CAF: a signed projection, not a truth oracle
Casa can produce a Capx Attestation Format bundle: a signed projection of operating state with commitments, published only when the founder explicitly chooses to.
Inside a bundle
manifest.jsonwhat is included, schema version
statements.jsoncompany-authored values (claimed)
commitments.jsondigests of unseen artifacts (committed)
signaturebinds the bundle to the company key
Local commands
Casa renders, the sidecar signs. All four steps run on your machine, with no network.
node caf/keygen.mjs company-brainnode scripts/brain.mjs attest company-brainnode caf/sign.mjs company-brainnode caf/check.mjs company-brainThe last command is an offline check. It does not talk to the network.
A self-check, not a verdict
caf check is a self-check, not a verdict. Passing means the record is internally coherent and structurally legal. It does not mean the record is true.
What it proves
| Property | Guaranteed by CAF? |
|---|---|
| The company stated exactly this | Yes: signature over the bundle |
| The statement has not changed since | Yes: integrity by construction |
| A committed artifact existed at publication | Yes: digest bound to the root |
| The statement is true | No: truth requires reproduction |
Lifecycle
CAF 01OBSERVATION CHAIN STUDYINTEGRITY / NOT A TRUTH ORACLE
EARLIER RECORDCASA OBSERVATION
Envelopestructure passes
Continuityprevious hash matches
Arithmeticclaims reconcile
Commitmentartifact digests bound
ON-CHAINREPRODUCEDCOMMITTEDCLAIMED
Passing means the record is internally coherent and structurally legal. It does not mean the record is true.
- Publication is an explicit founder action, never a side effect
- Terminal reads bundles and labels contents claimed or committed
- Reproduced status is earned only when Capx re-runs the underlying check
- The open-source core stays neutral: CAF is the optional bridge, not a requirement