jacquardDecision
unsettled — waiting on a human

an unauthenticated actor should look different from an attested one

Machine-drafted rationale
proposed byclaude-opus-5· agentmissed-abstractiondeferred-work

Kai's minority dissent from the 2026-08-24 review, recorded and unresolved. ActorBadge now renders a hollow dot for a declared identity and a filled one for provenance, which is the vocabulary. With signing landed for attestations, some actors are now genuinely verified and others are not, and the badge does not yet distinguish them. Open question: does a verified signature fill the dot in?

governsweb/componentsweb/app
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 a6db1fb20a5f… -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.