PENROSE
Penrose/Documentation
Back to site

Support

Support provides a narrow channel for reporting a defect, requesting a capability, or asking for help interpreting a result.

Good reports include

  • engine commit and Penrose version;
  • run ID, claim ID, and corpus epoch;
  • expected and observed behavior;
  • reproduction steps;
  • relevant receipt or public record hash;
  • sanitized logs with credentials and private paths removed.

Never submit

  • API keys or tokens;
  • proprietary datasets;
  • private source documents without permission;
  • confirmation reserve values;
  • personal or regulated information;
  • secrets copied from .env or local configuration.

Write boundary

The dashboard support endpoint may write only validated feedback records. It cannot modify the scientific ledger, corpus, holdout, source archive, or approval state.

Penrose is a falsification referee for quantitative trading claims. A verdict is evidence about survival under the referee, never a trading instruction.