# 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.39 · 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 |`````` | analyst@cold-read.the-ultimate-insider | sha256:b45cfc076710a84c | sha256:8d3e24fe382a3be1 | session_01Kw9UwBANzx2EEjifgwwjPF | 2026-10-30T01:51:13Z |`````` | conductor@cold-read.the-ultimate-insider | sha256:d1ddb098a416d027 | sha256:380fa27bf90915e2 | session_01Kw9UwDpw3MHUuXvpTkoJkf | 2026-10-30T01:11:27Z |`````` | critic@cold-read.the-ultimate-insider | sha256:a558f59c6b1173fd | sha256:73a371ec6c0f2154 | session_01Kw9UwFLji866eu2x4BdCPb | 2026-10-30T01:52:12Z |`````` | grc@cold-read.the-ultimate-insider | sha256:6cda488564949dfa | sha256:799fac03bfae6752 | session_01Kw9UwBfSz48uj9wXSTPeUV | 2026-10-30T01:51:34Z |`````` | historian@cold-read.the-ultimate-insider | sha256:0b365c753f3456ed | sha256:043838a3393a7846 | session_01Kw9UwEZvw2EdgWgea4BQyC | 2026-10-30T01:47:12Z |`````` | journalist@cold-read.the-ultimate-insider | sha256:9e3921aaa672d30a | sha256:5cc68d4e29f04299 | session_01Kw9UwDN4mw1BZGYPbaTcNm | 2026-10-30T01:52:34Z |`````` | reader-1@cold-read.the-ultimate-insider | sha256:da07c13e86383299 | sha256:a3a4dae126bd5330 | session_01Kw9UwEkNUTDi3xo671Le9Y | 2026-10-30T01:52:53Z |`````` | reader-2@cold-read.the-ultimate-insider | sha256:23fc5bbce8529018 | sha256:9d8cfa2171aabb9c | session_01Kw9UwE9BQ5X4xzXct42UgE | 2026-10-30T01:53:04Z |`````` | reader-3@cold-read.the-ultimate-insider | sha256:330bf8db1ccf850e | sha256:b5d5024620ecaff9 | session_01Kw9UwCfbh5zCT6GXDt1kuJ | 2026-10-30T01:53:18Z |`````` | reader-4@cold-read.the-ultimate-insider | sha256:10f1873b07981579 | sha256:c0819e40b900041e | session_01Kw9UwBjyLegCCAFp5ebvWf | 2026-10-30T01:54:12Z |`````` | reader-5@cold-read.the-ultimate-insider | sha256:fd507890a02b299f | sha256:41e9745afdeec3d8 | session_01Kw9UwBuiEExFFfukfkpP5y | 2026-10-30T01:53:41Z |`````` | security@cold-read.the-ultimate-insider | sha256:474dded6f57f44b0 | sha256:8bc96fcf868d3e85 | session_01Kw9UwEFygpv8cKrL42CMhR | 2026-10-30T01:52:16Z |`````` | technologist@cold-read.the-ultimate-insider | sha256:6a07488b6dfe36f4 | sha256:543361cb30951666 | session_01Kw9UwEVwa1hzgTRtAzz6aS | 2026-10-30T01:50:50Z | ## 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 source team talked through two public vaults (its team/conductor/vaults.json at 298be4e). This team never created them: at the editor's word (30 October 2026, 01:58 UTC) the same layouts live as folders in this repository, comms/issues (Issues-FS lite) and comms/mail (Email-FS lite), with git as the medium. Both are as public as the vaults were: the repository and its site are public. No vault, so no read key and no vault key. 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.cold-read.sgit.ai/admin/keys.html)*