Proof Layer / Buildability
This route exposes the Wave 0 and Wave 1 receipt scaffolds used to connect paper proof, Signal Canvas, Evidence, and Build Loop verdict primitives. It is intentionally explicit about what is currently computed versus what remains an external gate.
Wave-scoped truth status for buildability public surfaces.
Machine-readable feed route consumed by downstream ranking and watch workflows.
Execution surface where receipt-aligned verdicts route into decision actions.
Evidence workstation now linked to receipt scaffolds for proof continuity.
Receipt cohort roadmap
This build includes 3 deterministic seed receipts and 200 verified public receipts. The 75 and 200 receipt milestones stay blocked until real external receipt packages are supplied and verified.
public cohort 75
200/75
ready real public receipt volume
public cohort 200
200/200
ready real public receipt volume
Deterministic fixtures
These receipts are deterministic pipeline fixtures. They are useful for verifying render paths, blocker copy, hashes, and external gate wording, not for claiming real founder signatures or pilot telemetry.
Insufficient-data contract
Missing compute requirements, demo timing, external signatures, registry approvals, pilot telemetry, adoption receipts, and Brier outcomes render as blockers. The page does not infer them from proof run duration, fixture scores, or route availability.
Truth Boundary
Buildability surfaces only report computed viability and proof receipts. They do not claim live production usage, pilot outcomes, founder sign-off, public Brier calibration, judge divergence, or external adoption unless explicitly sourced.
A signed, evidence-backed receipt that records whether a paper is actually buildable — code public, dependencies pinned, holdout coverage measured, scaffold contract present. Status is one of `buildable`, `conditionally_buildable`, `not_buildable`, or `unknown`. Verifiable via the `/api/buildability/verify-receipt` endpoint.
A Model Context Protocol server exposing read-only tools to agents over streamable HTTP. Tools include `search_signal_canvas`, `search_buildable_papers`, `get_buildability_receipt`, `get_repro_requirements`, and `submit_build_attempt`. Connect from Claude Desktop, Cursor, or any MCP-aware client.
POST the receipt JSON to /api/buildability/verify-receipt. The endpoint runs an ed25519 verifier and returns counts_as_wave7_completion=false for unsigned or placeholder receipts.
Buildability Waves stage the proof a paper is reproducible. Wave 0 is metadata only; Wave 7 requires founder signatures, live telemetry, external adoption, real-judge divergence, and the public Brier receipt. Each step up tightens the contract a Buildability Receipt has to satisfy before the platform calls a paper buildable. Waves let us ship the surface long before every check is perfect.
Every Buildability Receipt carries an ed25519 signature with a key id. The signature proves the platform actually issued the receipt and nobody downstream forged or edited it. POST a receipt to /api/buildability/verify-receipt and the verifier returns whether the signature is valid and whether the receipt counts as Wave 7 completion. Unsigned receipts fail closed.