jac-serve declares plane = content and is therefore forbidden from reaching jac-seed; the boundary check says so in those words if you try. So the thing that actually seeds has to be a separate process that pushes to the surface, and the surface only ever learns a set of snapshot ids that must not promote. The ordering — seal the key, publish the id, then push — is what keeps that set from being a blocklist that fails open. Nothing implements it yet.
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 7e206966d6ae… -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.