Evidence
SuperDomestique asks people to trust unattended software delivery. The evidence for that trust belongs in public records, close to the claims it supports.
Current position
| Area | Status | Record |
|---|---|---|
| L3 parking and run completion | Enforced at the documented ledger boundary | Public trust-claim audit |
| External L3 delivery | Demonstrated on a subject repository. The published Fly.io case study delivered its issue, but two governance controls failed, so it does not support a clean governed delivery | July L4 capabilities audit; Fly.io L3 case study |
| Harness support | Claude Code is the primary supported harness. Codex has completed an interactive run with limitations, and pi.dev is planned | Harness support; Harness coupling inventory |
| L4 completion | Unsupported as a complete public claim | Public trust-claim audit |
| Independent governance verification | The external-verification protocol is published. Its first real case did not support a clean governed delivery, and reproducible external proof is still pending | External-verification protocol v0.1 |
Read the records
- The public trust-claim audit is the current claim-by-claim status record.
- The L4 capabilities audit compares shipped mechanisms, documentation claims, and external runs.
- The MCP call census is a dated first-party measurement of Linear connector traffic during development.
- The evidence format guide describes the records emitted by governed runs.
- The external-verification index lists the published protocol and each real case.
These records are dated. A later implementation change does not silently update their findings.