Agentic · technical details

What each piece does, and where to check it.

Each line names the command, function or file that backs it. The plain version is on Agentic.

How they fit

How the pieces run together, and what each is built on.

Colour: part
  • Agentic
  • Outside your machine
  • Building blocks
  • Developer experience
  • Closed source
Fill: status
  • Done
  • Under construction
  • Planned
Lines: relation
  • Runs with
  • Goes through a Signet
  • Builds on
  • Under construction
  • To a planned piece
How the agentic tools work togetherFoundry runs on your machine with agent-session and Archive. Kingdom is the permission hub: your integrations connect to it, and anything that uses an integration goes through a Signet. Foundry and a local Archive pair with Kingdom through a Signet; Your command-line tools will run through Kingdom so no token sits on your machine, with KCP, the Kingdom CLI Proxy (signing in works; running commands is in progress). Oracle measures and tunes Foundry. Artifactory is planned.On your machineMeasuring the workHostedOutside your machineWhat they're built onFoundry pairs with Kingdom; the pairing is a Signeta local Archive pairs with Kingdom through a SignetKCP will run your provider CLIs through Kingdom (in progress: it signs in today)your integrations connect to Kingdom, which holds their credentialsteammates and their agents use your integrations through a SignetArtifactory will sign in with Kingdom (planned)Foundry runs each agent session on your machineFoundry sends every session to ArchiveOracle measures and tunes Foundry's docs and WardensFoundry runs sessions with agent-sessionFoundry captures sessions into ArchiveArchive reads sessions through agent-sessionFoundry holds its Kingdom access as a SignetArchive shares are SignetsKCP presents a Signet for each commandKingdom issues and checks SignetsKingdom sets up and reaches ArchivesKingdom uses agent-sessionOracle builds on FoundryOracle replays work with agent-sessionOracle reads sessions from Archivebench runs agents with agent-sessiona Signet's lens is json-rulesagent-session uses json-rulesFoundry uses json-rulesKingdom uses json-rulesFoundry uses glossFoundry uses configKingdom uses prisma-mapKingdom decides access with permissionsKingdom uses rules-builderoracleDid a fix stick?closedbenchAgent challengesfoundryAgent workspaceunder constructionagent-sessionRuns sessionsarchiveKeeps sessionskcpCLIs through Kingdomunder constructionkingdomThe permission hubunder constructionsignetRevocable passintegrationsGitHub, Slack, LinearteammatesThem and their agentsartifactoryShare agent workplannedprisma-mapData shapejson-rulesRulespermissionsWho can do whatrules-builderRule screensglossNotes beside the codeconfigShared setup

Hover or focus a piece to light what it builds on and what builds on it.

Measuring
  • oracleDid a fix stick?Built on agent-session, Archive, Foundry
  • benchAgent challengesBuilt on agent-session
On your machine
  • foundryAgent workspaceBuilt on agent-session, Archive, Signet, json-rules, gloss
  • agent-sessionRuns sessionsBuilt on json-rules
  • archiveKeeps sessionsBuilt on agent-session, Signet
  • kcpCLIs through KingdomBuilt on Signet
HostedEverything outside your machine reaches you through a Signet
  • kingdomThe permission hubBuilt on Signet, Archive, agent-session, permissions, json-rules, prisma-map, rules-builder
  • signetRevocable passBuilt on json-rules
Outside your machine
  • integrationsGitHub, Slack, Linear
  • teammatesThem and their agents
  • artifactoryShare agent work
Read the map as text

How to read the map: colour shows which part a piece belongs to (amber building blocks, teal developer experience, lime agentic, blue outside your machine, violet governance; charcoal marks closed source and pink marks a connection that goes through a Signet). Fill shows status: a solid block is done, a block in scaffolding is under construction, a dashed outline is planned. Lines show the relation: solid builds on or runs with, dotted reads prisma-map's map, pink goes through a Signet, a scaffold-dashed line is under construction (on the technical graph: what template will adopt), a long-dashed grey line reaches a planned piece.

  • prisma-map: Your Prisma schema, readable at runtime. Built on config.
  • json-rules: One rule that runs in memory, in Prisma and in SQL. Built on prisma-map (reads its map), config.
  • permissions: RBAC, ABAC and ReBAC on your own records. Built on prisma-map (reads its map), json-rules, config.
  • rules-builder: A headless rule builder. Built on json-rules, config.
  • gloss: Explanations kept out of the source. Built on config.
  • config: The shared toolchain and theme.
  • Foundry: The workspace around your agent. Under construction. Built on agent-session, Archive, Signet, json-rules, gloss, config. Foundry pairs with Kingdom; the pairing is a Signet. Foundry runs each agent session on your machine. Foundry sends every session to Archive. Oracle measures and tunes Foundry's docs and Wardens.
  • agent-session: Runs each Claude Code and Codex session. Built on json-rules. Foundry runs each agent session on your machine.
  • Archive: Keeps every agent session. Built on agent-session, Signet. A local Archive pairs with Kingdom through a Signet. Foundry sends every session to Archive. Oracle reads the sessions Archive keeps.
  • KCP: Runs your CLIs through Kingdom. Under construction. Built on Signet. KCP will run your provider CLIs through Kingdom (in progress: it signs in today).
  • Kingdom: The permission hub. Closed source. Under construction. Built on Signet, Archive, agent-session, permissions, json-rules, prisma-map, rules-builder. Foundry pairs with Kingdom; the pairing is a Signet. A local Archive pairs with Kingdom through a Signet. KCP will run your provider CLIs through Kingdom (in progress: it signs in today). Teammates and their agents use your integrations through a Signet. Your integrations connect to Kingdom, which holds their credentials. Artifactory will sign in with Kingdom (planned).
  • Signet: A revocable pass on the owner's terms. Built on json-rules.
  • Your integrations: GitHub, Slack, Linear, Google. Your integrations connect to Kingdom, which holds their credentials.
  • Teammates and their agents: Anyone the owner gives a Signet. Teammates and their agents use your integrations through a Signet.
  • Artifactory: Sharing what agents make, signed in with Kingdom. Planned. Artifactory will sign in with Kingdom (planned).
  • Oracle: Measures whether a correction stuck. Closed source. Built on agent-session, Archive, Foundry. Oracle measures and tunes Foundry's docs and Wardens. Oracle reads the sessions Archive keeps.
  • bench: Our challenge set for coding agents. Built on agent-session.