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 the pieces run together, and what each is built on.
- Agentic
- Outside your machine
- Building blocks
- Developer experience
- Closed source
- Done
- Under construction
- Planned
- Runs with
- Goes through a Signet
- Builds on
- Under construction
- To a planned piece
Hover or focus a piece to light what it builds on and what builds on it.
- 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
- 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.
Foundry
A local daemon and viewer around Claude Code and Codex, also reachable from agent apps such as Paseo and T3 Code over the Agent Client Protocol (ACP).
- Runs as a launchd agent on macOS; the viewer is at http://localhost:4500. Install with bunx @inixiative/foundry-acp setup.
- Threads run on the Claude Code and Codex logins already on the machine, through @inixiative/agent-session. No API key is needed.
- foundry-acp is a stdio ACP adapter, so Paseo and T3 Code can drive the daemon.
- Wardens are built from the repo's docs, one per topic. Each turn, every Warden is asked whether the request touches its topic and, if so, names the existing thing and the doc section where it's written. They never block. They are off on a fresh install. Turn them on per project with "chorus": { "enabled": true } in the repo's .foundry/project.json, or with the project's Chorus switch in Foundry's settings.
- /feedback records a correction with its context; foundry repeats lists the corrections you keep giving.
- The app is BSL 1.1: any use except offering it to third parties as a commercial product or service, internal use at work included. It becomes MIT on 2030-04-06.
Kingdom
The hosted hub for identity, owners, integrations and Signets.
- Owners are a person, an organization, or a space inside an organization, with memberships and roles.
- An integration (GitHub, Slack, Linear, a paired Foundry or Archive) holds its credentials in Kingdom; they are never handed out.
- A Signet is the only grant to use an integration. An API token only reaches Kingdom's own API.
Archive
A session store you run yourself, one per machine, that syncs onward.
- Transcript extraction for Claude Code, Codex and Foundry sessions, immutable revisions in Postgres (pgvector and pg_trgm), lexical search and lossless text chunks.
- An authenticated HTTP server and published image; archive up runs it with Docker Compose on loopback 4700. Railway and Render configurations ship in the repo.
- Multiple explicit destinations with publication receipts, conflict detection and retry after interruption. One deployment is one ownership boundary with one access token.
Signet
The one implementation of the Signet protocol, shared by Kingdom and every client.
- contracts: the wire schemas for keys, grants (operation picks, lens layers, terms), proposals, pairing requests, describe and execute.
- proof: DPoP proofs, ES256, nonce-bound and access-token-bound. files: private 0600 JSON files for keys and credentials.
- client: registerInstallation, pairInstallation, InstallationSocket for live revocation, requestSignet, and SignetClient for describe and execute.
KCP, the Kingdom CLI Proxy
Runs your command-line tools through Kingdom so no token sits on your machine. A thin client on @inixiative/signet: a CLI command becomes a Signet execute call that Kingdom runs.
- Built: kcp login (browser, --token, --signet), logout, status and map. Credentials live under ~/.kcp, 0700 directory and 0600 files, one directory per Kingdom host.
- In progress: running commands through Kingdom. No operations are declared and Kingdom's runner is not built, so kcp railway, gh, vercel and infisical do not run commands yet.
agent-session
Long-lived Claude Code and Codex processes behind one interface.
- ClaudeCodeSession keeps one agent process per session, sends each turn over stdin and classifies each event that comes back: text, thinking, tool calls, tool results and usage.
- Claude Code runs over its CLI or the Agent SDK; Codex over its app-server.
- Also holds primed decision sessions, subscription pools with deterministic routing, limit polling and session continuity. Foundry and Archive run their sessions on it.
Oracle
Measures whether a correction stuck, and tunes the docs and Wardens.