Reality Gate

On a fresh launch with no repositories, Reality Gate walks you through: add a repository, analyze dependencies, run a continuity check, get proof. Add the path you already use — GitHub, GitLab, or Forgejo remotes included — and the project appears on the board exactly as your git state describes it.

• Registration is read-only for the repository: Reality Gate validates the path, records the mapping, and reads local git state.
• No migration, no import step, no forced account. Your workflow stays where it is.
• A disposable demo repository ships with the pilot, so you can run the whole flow before pointing it at a real project.

What "passive" means here: the app does not push, fetch, rewrite remotes, or alter git configuration. It reads the repository and reports what it sees. The only writes it makes are its own data and receipt directories.

Once a project is registered, Forge Home renders a continuity card with five readings: Work, Proof, Recovery, Custody, and Provider Exposure. A reading is STRONG only when checks have run and passed; anything not yet exercised reads NOT TESTED or UNKNOWN — never an implied pass.

• Work: what local operations are known to keep working, and where they stand.
• Proof: whether proof has been generated and persisted for this project.
• Recovery: whether a recovery drill, bundle, or restore evidence exists.
• Provider Exposure: which capabilities still depend on a provider, in plain terms.

What this means for the demo below: the card reports provider exposure (push/fetch/clone) and marks proof and recovery as NOT TESTED — the honest state before any drill has run. The next two sections are what happen when you convert those readings into evidence.

When a CI run completes, Reality Gate snapshots the source state before and after the run, compares them by hash, and signs the run manifest with the machine's ECDSA P-256 key. The Runroom then shows the outcome badge and a VERIFIED RECEIPT badge — earned by a real signature, not assumed. A public key ships with each receipt, and a Compare action checks one run against another.

• The run manifest covers run ID, repository, branch, commit, pipeline hash, machine fingerprint, outcome, and source-state hashes.
• If the source changes while the run is in flight, the receipt records a mutation detection rather than hiding it.
• The signed receipt JSON (with its public key) is exported to the project's own workspace with the run record.

What a verified receipt is — and is not: it proves the record — which run, on which commit, on which machine, with which outcome — was signed and has not been modified. It is not a claim that the code is correct. The receipt verifies provenance, not quality.

The Recovery Vault creates a verified Git bundle for the project, checks it with SHA-256, and writes a signed receipt. "Prove I Can Recover This Project" then runs the recovery drill end to end. When a provider goes down, the procedure is already evidence-backed — you are not debugging recovery in the middle of an outage.

• Create verified Git bundle → bundle verified + SHA-256 + signed receipt.
• Recovery drill → runs the phases and persists the receipt regardless of outcome.
• Isolation inside the drill: credentials removed, no external remotes, no provider contact observed.

Preparedness, not magic: this is planned continuity and recovery capability, not autonomous failover. Reality Gate does not reroute your CI or keep a provider alive. It verifies that the local path — bundles, history, toolchain — is ready before it is needed.

The suite is verified at 269/269, and the number is composed of three checked suites: 269/269 static tests, a 24/24 live registration-registry suite, and a 20/20 installed-runtime hardening suite. The pre-pilot audit found no blockers and no overstated claims; it recorded two known non-blocking issues in standalone (non-packaged) execution.

• The published ZIP SHA-256 matches the build manifest and the R2 artifact (verified end to end).
• The packaged app runs with Electron sandboxing, context isolation, and node integration disabled.
• CI runs execute inside isolated git clones with whitelisted commands only.