What this demonstrator does not prove
Read this before quoting any figure from this tool. A demonstrator that hides its limits is worse than no demonstrator.
What it does demonstrate
- ✓refusal logic is coherent, against durable state
- ✓the ledger is append-only and its chain verifies
- ✓separation of duties is refused at the transaction boundary
What it does not establish
MVP.md section 11, program/28-production-technology-controls.md
| Claim | Status | Why not |
|---|---|---|
| acts are non-repudiable | Not true here | signatures are SHA-256 digests; no hardware-backed keys |
| identity is assured | Not true here | seeded accounts; no sovereign identity provider, no MFA |
| data is protected | Not true here | no classification, access logging or retention schedule |
| it is available and recoverable | Not true here | no disaster recovery, no manual fallback |
| it scales | Unproven | state is rebuilt by full log replay on each request |
| it is sovereign-hosted | Not true here | not hosted in Iraqi facilities |
| the economics work | Out of scope | the assumption register is largely synthetic |
| a mechanism is legally and fiscally classified | Out of scope | a Phase 0 gate condition; software cannot answer it |
Refusal codes
Every refusal this system can produce, rendered from the message catalogue rather than from server prose.
ACTOR_INACTIVEALREADY_ISSUEDBAD_CREDENTIALSBLOCKED_BEFORE_SELECTION_GATECAP_BINDINGCEILING_EXHAUSTEDCERTIFICATE_STALECLOSURE_NOT_CURRENTCONFLICT_OF_INTERESTCOVERAGE_INSUFFICIENTD0_DIGEST_MISMATCHELIGIBILITY_BLOCKEDFRESH_CAPITAL_SHORTLEDGER_INTEGRITY_FAULTNOT_ACCREDITEDNOT_AUTHENTICATEDNOT_FOUNDNOT_OWN_RECORDREVIEWER_OUTSIDE_FIRMROLE_NOT_PERMITTEDSELF_REVIEWSESSION_EXPIREDSTEP_NOT_IN_MECHANISMUTILISATION_CAP_EXCEEDEDVALIDATION_FAILED