THE PROOF FOUNDRY™

What we're building next.

A public view of the Foundry's current product lanes, proof gates, and what comes next. We separate shipped work, release candidates, active proof work, and research so roadmap ideas are never presented as finished features.

Build it. Prove it. Ship it. Roadmap status is evidence-scoped and may change as gates close.

ACTIVE PROOF LANES

What is moving now

Active proof work

Reality Gate

Reality Gate is being dogfooded against its own source. The validator path has requalified; the current remaining blocker is a deterministic test-oracle issue in the candidate baseline before the final self-CI proof can run.

  • Local-first project truth and CI governance
  • Signed failure receipts independently verified
  • Self-hosting proof still open
  • Agent/MCP gateway design underway in parallel

Not claimed: self-modification or autonomous release authority.

View Reality Gate →
Technical candidate / hold

Lights Out

The v11.1.3 technical candidate is proven, but publication is intentionally held until the live website/public-state story and exact release artifact identity are reconciled.

  • Technical candidate proven
  • Exact artifact identity required before publication
  • Public-state reconciliation still open
View Lights Out →

SHIPPED / STABLE BASELINES

Current public truth

Public release

GhostLayer

v0.2.1 is the current branded public release, distributed through the Proof Foundry download domain with SHA-256 verification. GitHub publication remains deferred.

View GhostLayer →
Public release

Cache Vault

v0.2.2 is publicly released. The next Cache Vault lane will be post-release hardening and product refinement, not a replay of old release-candidate gates.

View Cache Vault →
Public release · frozen

ForgeCast

v0.3.3 remains the safe public baseline until a fresh source, signing, release, and device-state audit opens the next engineering tranche.

View ForgeCast →
Authority re-proof next

Cleanroom

Cleanroom's next lane starts with a fresh canonical/release-state audit before any new release or feature claim is made.

View Cleanroom →

NEXT PLATFORM LAYER

Reality Gate Agent Gateway

The next major platform direction is a standard agent bridge so local coding agents can query and use Reality Gate without bypassing its proof and authority model.

The design draws selectively from earlier Proof Foundry / NeuralShell architecture: operator sessions, bounded execution, capability requests, and intent gating—while Reality Gate remains the authoritative control and receipt layer. 

Agent
  ↓
MCP Gateway
  ↓
Capability / Claim / Mutation Budget
  ↓
Reality Gate
  ↓
Governed Project
  ↓
Signed Receipt
Design now. Implement after self-hosting proof.

MCP v1 is intentionally narrow: project status, pipeline inspection, governed runs, logs, source state, and receipt verification. Arbitrary shell, unrestricted Git, release, and deployment operations are outside the first bridge.

ARCHITECTURAL RESEARCH

NeuralShell / ProofForge lineage

Historical NeuralShell and ProofForge work is being treated as architectural research, not as a product resurrection. Proven ideas around operator workspaces, persistent sessions, command surfaces, bounded execution, capability brokering, and provider routing are being studied for selective use in future Reality Gate layers.

NeuralShell / ProofForgeOperator shell and session UX
ExecutionBrokerBounded process execution
OMEGACapability / intent concepts
RouterCorePotential later provider routing

Historical systems remain separate lineages. Their architecture may inform new work; historical claims are not silently promoted into current Reality Gate guarantees.

THE ROADMAP RULE

Green is not permission.

1. Build Create a bounded candidate.
2. Prove Run explicit tests, receipts, field checks, and negative proof.
3. Decide Release, merge, or publication remains a separate owner decision.