Sign a node¶
Signing a node records your approval of exactly the text on the page, with your fingerprint, face or device PIN. You do it yourself, in your browser, on a page Hadron's server hosts. An agent can ask you to sign and can hand you the link, but it cannot sign for you and cannot press the button: only a person signs, with their own passkey. If you have not got a passkey yet, register one first.
Signing is off by default on a server you run yourself. An operator turns it
on with PASSKEY_SIGNING_ENABLED=true. /capabilities
lists node-signing on a server where it is on; without it there is no signing
page. What a signature covers, and what it does not, is in
Signed revisions.
Ask an agent to ask you¶
Not yet run end to end
The request below is the shape of what to say, taken from the
MCP signing tools. It has not been
run against a live agent. Rely on the receipt your agent shows you, which
carries the Ceremony link: line, rather than on the agent's wording.
Tell your agent which node you want signed and by whom:
Ask me to sign the node
hrn:node:hadronmemory.com:dev:decisions:dk-001.
The agent creates a signing request for the node's current revision and gives you a ceremony link to open. It hands the link over exactly as Hadron printed it, and the link is only there while the request is open. If you want only one named person to be able to sign, say so; otherwise any writer of the node's memory can. A request you no longer want can be withdrawn by the account that asked: tell the agent to withdraw it.
Open the link and sign¶
- Open the link in a browser. The page is titled Review and sign. It shows nothing yet: "To see what you have been asked to sign, confirm it is you with your passkey."
- Click Use passkey and approve. If the request names a person, only that person gets in.
- Read what the page shows before you sign: who asked, when the request expires, the node's title, summary and text exactly as Hadron stored them, the revision, and changes since the last signed revision. Any text pulled in from elsewhere is shown as its include tag and marked [not covered by this signature].
- Click Sign with passkey and approve again. The page says "Your signature was recorded. You can close this page."
If you may read the node but not write to its memory, the page says "You can read this, but you are not allowed to sign it." and offers no buttons.
Decline¶
Click Decline, then Yes, decline ("It will be ended and can no longer be signed"). Cancel goes back. A declined request is ended for good; whoever asked has to make a new one.
When the page says the request has ended¶
A request ends exactly once. The page says which way:
| The page says | What happened |
|---|---|
| This request was already signed. | Someone completed it. |
| This request was declined. | It was declined. |
| This request expired. | Its deadline passed. |
| The text changed after this was requested, so this request can no longer be signed. | The title, summary or text changed. Ask for a new request. |
| The person who asked withdrew this request. | It was withdrawn. |
Each ends with "Ask for a new signature request to sign again."
Two failures look alike but are not. "That did not verify. Nothing was recorded. You can try again." and "That did not work and nothing was recorded." are definite: nothing was written, and you can retry. "We could not confirm whether your signature was recorded. Reload this page and check before trying again." is not definite: the signature may have been recorded. Reload, then check the result as below before you try again. The same goes for "We could not confirm whether the request was declined." after a decline. A node in an encrypted memory is never signed: the page says "Not signable".
Check the result¶
Ask your agent for the node's signatures, or run:
A signature made with your first passkey, while its cooling-off window is still running, reads PENDING and does not count yet. See Register a passkey. Every state is explained in Signed revisions.
If you start from the CLI¶
hadron node sign <node-ref> creates the same request. The CLI never signs,
and as of v0.44.0 it prints the request's id, state, node and
deadline but no ceremony link. The link is /signing/ followed by that id,
on the server's own address (https://srv.hadronmemory.com on hosted Hadron); the MCP signing tools print it for you as
Ceremony link:. --revision refuses if the node has changed since you read
it, and --signer names the one person (by user id) who may sign. See the
CLI reference for the rest.
Signatures and agent-team authorizations¶
This is guidance on how agent teams work, not a description of something the platform enforces. The practice agent teams follow is: for an agent, an authorization counts only if its current revision is signed by the person expected to sign it.
A signature covers the revision it was made on and later revisions until the title, summary or text changes; see Signed revisions. A pending signature never counts. Who counts as the person expected to sign is named by the rule that asks for the signature, not by this page.
Related¶
- Signed revisions: what a signature is and is not.
- Rules this page follows, from the product specs:
cor:dmo:130:02(only the signer, through the ceremony, makes a signature),cor:dmo:130:03(a signing request's lifecycle),cor:dmo:130:08(the ceremony runs on a server-hosted page that shows exactly what is signed) andcor:dmo:130:09(what "signed" means). - MCP tools: Signatures
- Hadron CLI: node approval, minting and signing
- Register a passkey
- Let a worker edit its own boot prompt: the signed grant, a different signature.