Inspectable progress.
Explicit open questions.
Specifications, runnable prototypes, formal results and real customer outcomes answer different questions. Here is the current scope of the ecosystem and the work that remains.
Different stages.
Specific evidence.
| Component | Present scope | What remains open |
|---|---|---|
| E7G-T | Experimental v0.15 reference; bounded executable models and scoped formal work. | E7C completeness and the all-input Python/IR-to-Lean adequacy bridge remain open. |
| E2CI | Bounded offline runtime, structured-input admission, deterministic reports and semantic replay. | Reviewer workspace and explicit reviewer-response workflow are in open drafts. Real-task usefulness and paid demand need evaluation. |
| E7DB | Pre-alpha reference implementation; semantic runtime and append-only storage contract. | Durable XTDB integration and expanded review/recovery experiments are in an open draft. Production deployment and customer validation remain open. |
| E7 Boundary | Architecture with selected security and controlled-reliance prototypes. | Full Boundary conformance has not been achieved. Complete deployment controls and independent review remain open. |
| E7 Core | Provisional contract and conformance work within E2CI. | A released shared standard and broadly extracted common runtime are not yet established. |
| E7Q | Credential-free v1.0 release candidate rc12, reference circuits and portable evidence/reporting workflows. | Hardware validation, scientific interpretation and quantum advantage need separate evidence. |
| E7Q-IR | Core architecture within E7Q, with a bounded supplied-QASM/counts demonstrator. | The demonstrator does not execute real hardware or authenticate a provider’s observations. |
| E7FS | Evidence-preserving storage architecture direction. | A production file system, performance profile and recovery guarantee are not established. |
| E7 Fabric | Conditional integration and orchestration direction. | Broader orchestration depends on useful independent products and validated interfaces. |
A new reference is not an automatic migration.
E7G-T’s current experimental reference is v0.15. Its profiles include exact combinations, family-state and recursive constructions, reasoning with evidence and scoped coherence. Each profile has its own semantics and limits.
E2CI and E7Q retain product-specific pinned editions and contracts. This website does not claim that every consumer has adopted v0.15. A formal result applies to its stated model and assumptions; correspondence with a running implementation needs separate evidence.
Reasoning with evidence retains support and refutation independently and checks declared boundaries. It does not establish source truth, domain correctness or AI performance.
Inspect the experimental source.
E2CI and E7DB are maintained in non-public repositories. This page summarises their development state; it does not expose private source. Open drafts are distinguished from the main-branch implementation.
Define the question.
Keep the scope clear.
Start with the workflow, intended use and an example of a useful result. Agree the material, review responsibility and evaluation criteria before work begins.