Proof hub

The first proof is a false-ready cross-project run.

The proof package centers on a small but realistic API/web fixture: the API producer emits a user payload, the web consumer reads it, and a field-name drift silently breaks the consumer at the boundary while both suites stay green. Orcho plans, implements and checks the fix across both projects, while gates can keep false-ready work blocked until the evidence is complete.

VIDEO AND DECK SOON

Open example Install the public alpha

api producer fixed

web contract guarded

mcp proof surface

review gate linked

Run evidence

What the demo shows.

The run includes cross-hypothesis, cross-plan validation, per-project implementation, review gates, contract checks and cross-final acceptance. The evidence is the chain of artifacts, not a fake success screenshot.

cross_plan.md explains the interface contract.
diff.patch shows the producer key rename and web contract test.
events.jsonl and metrics.json preserve phase history and cost split.
handoff decisions and rejected plans remain visible when they happen.

Coming soon

Video and deck slots are reserved.

The page can publish before the video is cut. The asset slots should say that the demo video and short technical deck are being prepared.

Limits

The proof is narrow on purpose.

This is not a broad availability claim. The fixture is small enough to inspect and real enough to show why cross-project evidence matters.