# The key register > The current public key of every agent on the team, and the read keys of the public vaults it talks through. *Source: · site v0.1.34 · generated from the same content as the page, so the two cannot drift.* --- Admin # The key register The current session key of every member of the team. The push is the authorisation: each key was published by a session the editor's account lets push to this repository. Read a fingerprint from here or from the member's key.json, never from a message. | Agent | Fingerprint | Encryption | Session | Since |`````` | conductor@the-ultimate-insider | sha256:7047871c97407e2b | sha256:9568700877d11832 | session_01Kw9UwCYrsrC6HCKoskyDAo | 2026-10-29T00:48:29Z |`````` | deck@the-ultimate-insider | sha256:ec0c8365ee704c7a | sha256:2323997301936c37 | session_01Kw9UwBB1wNV9hwXCcQAzKn | 2026-10-29T02:18:24Z |`````` | dev@the-ultimate-insider | sha256:34bb81872471a542 | sha256:ecc1af727bb053cb | session_01Kw9UwED5okiUPqRn3ovgyo | 2026-10-29T01:53:07Z |`````` | researcher@the-ultimate-insider | sha256:efe173cb7f086366 | sha256:132c52339be3b4ba | session_01Kw9UwDxA7opmQMZf3iqCjN | 2026-10-29T01:49:56Z |`````` | ruv.sgit@the-ultimate-insider | sha256:6075a4b5d24881ae | sha256:f65a27535e3f110f | session_01Kw9UwDSQxFGP7NZd4MEJ4v | 2026-10-29T02:34:43Z | ## How a session gets its key - It makes the key pair in its own session with `admin/tools/pki-agent.mjs keygen --session`, a pinned, unmodified copy of [the tool pki.sgit.ai publishes](https://pki.sgit.ai/agents/pki-agent.mjs). The private halves never leave that session. - It writes the public half to `team//key.json` with its QR image, adds `team//sessions//`, marks the previous session superseded, and pushes. From that commit it is the agent. - To hand it a secret, read its fingerprint here, seal to it, and send the sealed QR or link. Only that session can open it. ## Known keys: not members, relied on by the team Public keys of agents outside the team that members seal to. Each was confirmed by the editor; the QR code carries the key itself, and `pki-agent.mjs read-qr` recomputes its fingerprint. ### DC Vault Registry (the vault of vaults) the editor's vaults manager: the agent that keeps the team's vault keys (the vault of vaults). `` | Fingerprint (record, signing) | sha256:956934e47063ceaa |`` | Encryption fingerprint | sha256:06c6ccddb7476629 | | Confirmed | by the editor, Dinis Cruz, in the conductor's session on 29 October 2026 ("yes that is the one") | | Source | https://web-summit.sgit.ai/keys/sha256-956934e47063ceaa.json, where the editor handed it over as a QR code on 28 October 2026 | | Use | seal a vault key to it (pki-agent.mjs seal --to sha256:956934e47063ceaa, or sgit pki encrypt --recipient sha256:06c6ccddb7476629); only the vaults manager can open what is sealed to it | [The key file](known-keys/dc-vault-registry.json) (both public PEMs) · [seal a secret to it on pki.sgit.ai](https://pki.sgit.ai/send/#k1.MIICIjANBgkqhkiG9w0BAQEFAAOCAg8AMIICCgKCAgEA0GBgDSrySVIggQjk61hnFneREDnIULzEwcYn0mpQHu7Ux0o9x71a-mVVV6umWJw_YtRJu5TjmUbordI0UzMhuXQc3dd1KSayBMyz9jiks0fUmuAFWvK3WqbZ_QWn879iTHKj1palpGRdsDhpHoSKLiqJrIHUOmXiYr4iS7qVZW4DdmaHM_kuyyJ8_FZzJbAzKGijjM3Hrz76dH37zVaKJHyiKkRd8Enl0YvmcIkNBKOmlwNiPmSJV7Xk4iiF4MQYFGM6aj-TDUkKMFLtLKuKOvBkUYCw7L88DHy0JFRX_nw1LA9IXfhUDSBI4XmuycpmWEzF1o35rblOP7sVDRinmgSZRDXjcO9cHgoZEKy0-s8v2m-AQS1evgGihfwrA1wKxpBMR7QhmpVsvyYpxHcVqop8ZFlgQEqlPevRlSTH30nG47OCBaZFlOUI9BV84gOqW5mwh7zRdr3lmM_Vf9IhorLT20UjBfLI1nsvF2IWvEc9yBBGDARZqEK4Bpy2M2mUbkNvhwQiy4DpndfszO9VLvnez1jpppbEZIDHT1xI0tuZ0EWKmbsG8x3toqKFFbtFEBQC_b5eR_CfpcpRafO5v37l1ulvZjTB_ypHVJgmHR0zU4bFJ2oPazJzjXI_ENEPwpBAgD1ZW1nkcNqFK9NaePgFbtHbWeUktsctObb3VocCAwEAAQ.MFkwEwYHKoZIzj0CAQYIKoZIzj0DAQcDQgAEdJXhI6H9riUxEEdW1z7duvaHzDPy6HFBVPQYTsKJhvPXRoA8reSwy5QhOa3aJlZfiBTvuOZKoW7BwDK1Szn9hg.REMgVmF1bHQgUmVnaXN0cnkgKHRoZSB2YXVsdCBvZiB2YXVsdHMp) ## The vaults the team talks through The vaults this team talks through. Both are 100% public: anyone may read them with the read key below; a read key cannot write. The pattern is web-summit.sgit.ai's (public and private vaults for Issues-FS, Email-FS and a CRM); this team needs the two public ones only. ### Issues-FS: `tui-issues-public` The team's board: each agent's open, blocked and done work, in Issues-FS lite. Vault `h9fh2apf` on `https://dev.send.sgraph.ai`. **Layout.** `/issues/{open,blocked,done}/NNN-kebab-slug.md; read every folder, write only your own` **Read key** (read only, published on purpose): `sgit_public_read_70e37665648d2a5241fb13c5a16c23d23e1fe4ff604e36e29777fe316bd09c14:h9fh2apf` `sgit clone sgit_public_read_70e37665648d2a5241fb13c5a16c23d23e1fe4ff604e36e29777fe316bd09c14:h9fh2apf tui-issues-public` [Open it in the vault browser](https://dev.vault.sgraph.ai/#sgit_public_read_70e37665648d2a5241fb13c5a16c23d23e1fe4ff604e36e29777fe316bd09c14%3Ah9fh2apf) · write key: escrowed: the vault key is sealed to the vaults manager, DC Vault Registry (sha256:956934e47063ceaa, encryption sha256:06c6ccddb7476629), confirmed by the editor; the sealed QR codes are in the handover zip the editor stores, and in no file here. ### Email-FS: `tui-mail-public` The team's mail: agent to agent, agent to editor and back, as .eml files. Vault `lotalm0w` on `https://dev.send.sgraph.ai`. **Layout.** `mailroom//NNN-subject.eml (new; anyone may add); /{inbox,done,outbox}/ (only that agent writes)` **Read key** (read only, published on purpose): `sgit_public_read_46d32067a2eb718cd1012ef4137c779d5d95f8ab9c7ef3dcfa23a3912191872a:lotalm0w` `sgit clone sgit_public_read_46d32067a2eb718cd1012ef4137c779d5d95f8ab9c7ef3dcfa23a3912191872a:lotalm0w tui-mail-public` [Open it in the vault browser](https://dev.vault.sgraph.ai/#sgit_public_read_46d32067a2eb718cd1012ef4137c779d5d95f8ab9c7ef3dcfa23a3912191872a%3Alotalm0w) · write key: escrowed: the vault key is sealed to the vaults manager, DC Vault Registry (sha256:956934e47063ceaa, encryption sha256:06c6ccddb7476629), confirmed by the editor; the sealed QR codes are in the handover zip the editor stores, and in no file here. ### evidence: `tui-evidence-public` Every source the talk and the editor's ideas rest on, captured and hashed; the claims register graded A0 to A6; the ideas map; agent incidents since May 2025. Vault `2fz1wv1d` on `https://dev.send.sgraph.ai`. **Layout.** `README.md, METHOD.md, BEFORE-TONIGHT.md, claims/, ideas/, incidents/, sources// with sources/manifest.json, updates/` **Read key** (read only, published on purpose): `sgit_public_read_ce52d21e4e26238922b2743a9b0b13f4abfb0adef3dcef10f0f1cce213571e65:2fz1wv1d``sgit clone sgit_public_read_ce52d21e4e26238922b2743a9b0b13f4abfb0adef3dcef10f0f1cce213571e65:2fz1wv1d tui-evidence-public` [Open it in the vault browser](https://dev.vault.sgraph.ai/#sgit_public_read_ce52d21e4e26238922b2743a9b0b13f4abfb0adef3dcef10f0f1cce213571e65%3A2fz1wv1d) · write key: escrowed: the vault key is sealed to the vaults manager, DC Vault Registry (sha256:956934e47063ceaa), in the handover zip given to the editor on 29 October 2026, and in no file here. As data: [vaults.json](vaults.json). Each vault's README says how to use it. As data: [keys/index.json](keys/index.json). The pattern is the PHP newsroom's, argued in [The push is the authorisation](https://newsroom.sgit.ai/articles/the-push-is-the-authorisation.html). --- *[Site index for agents](../llms.txt) · [HTML version](https://the-ultimate-insider.presentation.sgit.ai/admin/keys.html)*