jacquardDecision
unsettled — waiting on a human

persistent stores must not land before signing

Machine-drafted rationale
proposed byclaude-opus-5· agentconstraintsconfidence-risk

The adversarial review found an undocumented ordering edge between unblock conditions 1 and 6. Attestation integrity currently rests on impermanence: a forged record dies with the process. Persistent stores remove exactly that, and are the easiest and most obviously useful of the six. Signing has since landed for attestations, which weakens the original argument. Open question: is that enough to unblock #6, or does it need commit signing too?

governscrates/jac-objectcrates/jac-decisiondocs/design
Changes under this decision

reading the history…

Check your own understanding

Questions about this decision, asked of you. Nothing here is stored, scored, or able to settle anything — only a signature does that.

Human attestation — verbatim
No human has put their name to this.

Only a person can sign here: in the code, no attestation constructor accepts an agent — the compiler proves it. Identity is declared, not authenticated; signing is named future work.

Signing happens on your machine

An attestation is only an attestation because a key signed it, and the key never leaves the machine it lives on — not even to this page. Draft the words here if it helps; sign them with jac.

jac attest 66e7408efa17… -m "what you read, and what you are accepting"
Recognised, never policed.

Remarks

Select any sentence above to say something about it. A suggestion can become a decision; the gate can only enforce decisions.

Nothing raised here yet. Select a sentence to say something about it.