Kai's veto, still outstanding, recorded as blocking unblock condition 4 rather than the current deployment. The privacy claim is already double-enforced by the plane rule and the DigestSafe bound, and the transport that would need an abuse model does not exist. An org could publish a rival's sketches, or spam the registry to fish for introductions, and nothing in the design says what happens then.
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.
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 92c5767c5ae9… -m "what you read, and what you are accepting"
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.