The Claims Register
Every claim we make in public has a row here: what it says, where the evidence lives, what its status is today, and the specific gate it must pass before we may describe it as current.
Rows are not marked current because we believe them. They are marked current when they pass their gate.
- Implemented is described as current.
- Not yet implemented is described explicitly as specified, in development, or roadmap.
- We never imply an application runs on WAR unless that is technically true today.
- Enterprise Context Intelligence is described as the first enterprise application of the WAR architecture and its commercial validation pathway — that wording only.
| # | Claim | Evidence source | Status today | Gate to “current” |
|---|---|---|---|---|
| 1 | Intent Graph: typed, event-sourced, hash-verifiable, language-free | WAR-SPEC-001 (RFC-2119, implementable without founders) |
SPECIFIED
Specified; pre-prototype |
Prototype passes ir-lint invariants 1–8 |
| 2 | Intent Understanding Layer: 7-stage pipeline; the only component seeing language | WAR-SPEC-002 |
SPECIFIED
Specified; pre-prototype |
S1–S7 running on real utterances |
| 3 | Deterministic planner (pure function, byte-identical replay) | WAR-SPEC-003, Rule PL-1 |
SPECIFIED
Specified; flagged as the spec's riskiest promise |
CI replay test green |
| 4 | Provider compilers; cross-model replay; mid-execution fallback | WAR-SPEC-003 §5, WAR-TRACE-001 T12 |
SPECIFIED
Specified; worked on paper |
Two compilers passing identical artifact contracts |
| 5 | Clarification Engine (taxonomy, budget, why-carrying questions) | WAR-SPEC-004 Part A |
SPECIFIED
Specified; pre-prototype |
Live clarification round-trip |
| 6 | Build Along™: blast radius, interruption, rendered narration, replay | WAR-SPEC-004 Part B, WAR-TRACE-001 T10–T12 |
SPECIFIED
Specified; worked on paper |
Live interrupted session |
| 7 | Hinglish kirana end-to-end trace | WAR-TRACE-001 |
SPECIFIED
Complete worked trace on paper — not an execution log |
Prototype reproduces the trace |
| 8 | Pivot-language verification harness | WAR-SPEC-002 §5 |
SPECIFIED
Designed; not in CI |
Harness running on native-authored corpus |
| 9 | Research discipline: doctrine governance, self-critiquing specifications | North Star; DOS-user doctrine; WAR-TRACE-001 Coda F1–F5 (the trace found 5 defects in its own specs) |
LIVE
Current — demonstrable today |
— |
| 10 | Enterprise Context Intelligence runs on WAR | — |
NOT CLAIMABLE
NOT claimable. ECI is the first enterprise application of the WAR architecture and its commercial validation pathway. |
ECI executing via the WAR pipeline |
| 11 | WAR live platform | Founder target |
IN DEVELOPMENT
In development; launch target 15 August 2026 |
Launch |
| 12 | Live cross-provider demonstration | — |
PLANNED
Committed milestone for Finals (27–29 October 2026) |
Demo rehearsed on a real build |
| 13 |
CP-001 Business Website executes on the WAR runtime Added 3 Aug 2026
|
CP-001 freeze declaration, 3 August 2026 |
LIVE
Live |
— |
| 14 |
CP-002 Company Research Brief executes on the WAR runtime Added 3 Aug 2026
|
Provider Runtime v1, 3 August 2026 |
LIVE
Live |
— |
| 15 |
Claude ↔ Gemini provider swap by configuration, with no capability-specific code Added 3 Aug 2026
|
Provider Runtime v1, 3 August 2026 |
LIVE
Live |
— |
Three rows are worth reading twice, because they are the rows a diligence reader would otherwise have to discover for themselves.
The pivot-language harness is not running
The verification harness that would prove intent authored natively in different languages produces semantically identical graphs is designed and is not in CI. There is no multilingual determinism demonstration on this site, because there is nothing yet to demonstrate.
Enterprise Context Intelligence does not run on WAR
ECI is the first enterprise application of the architecture and its commercial validation pathway. It is specified, not shipped. This is why there is no Enterprise section in the navigation: a nav item with only promises behind it is worse than no nav item.
The trace found five defects in its own specifications
WAR-TRACE-001 is a complete end-to-end worked trace on paper — not an execution log. Running it against the specifications surfaced five defects in those specifications. This is the one row already marked current — demonstrable today.
A system with the property does not ask to be believed. It offers to be checked.
Every status chip elsewhere on this site links back to a row on this page. If you find a sentence on wesimplifai.com that you cannot trace to a row here, that is a defect and we would like to know about it.