PENROSE
Penrose/Documentation
Back to site

How to read these docs

The documentation is organized by intent.

If you are evaluating a claim

Read:

  1. Submit claims
  2. Verdicts and routing states
  3. Interpret a result
  4. Analysis Reports

If you are operating Penrose

Read:

  1. System model
  2. Safety invariants
  3. Dashboard operations
  4. Corpus operations

If you are building a public corpus

Read:

  1. Public corpus model
  2. Security and privacy
  3. Cost model
  4. Launch checklist

Source of truth

These pages explain the product and operator contract. The executable source and invariant tests remain authoritative when prose and behavior disagree. Thresholds and exact gate logic belong in the versioned engine and should be linked by engine commit rather than copied into a permanently stale web page.

The deeper research and engineering material remains in the repository's original docs/ directory.

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