<iXi>

The whole map.

The whole picture of what inixiative is building, and how the parts connect. The building blocks are a decade of lessons from building software, packaged as reusable pieces. The agentic tools get coding agents to use them. The governance designs are where it is all headed: tools for people, and their agents, to cooperate.

Colour: part
  • Building blocks
  • Developer experience
  • Agentic
  • Governance
  • Closed source
Fill: status
  • Done
  • Under construction
  • Planned
Lines: relation
  • Builds on
  • Reads its map
  • Goes through a Signet
  • Under construction
  • To a planned piece
The whole pictureThree tiers. At the base, the template layer: the whole SaaS app, made of the building blocks prisma-map, json-rules, permissions, transitions and rules-builder; beside it, developer experience: atlas, gloss and config, with the worktrees, init and CI rules that come with template. Above them, the agentic tools: Foundry, agent-session, Archive, KCP, Signet, Kingdom (the permission hub), Oracle, bench, and Artifactory (planned). At the top, governance: the Inixiative project (planned), a time-series governance platform with tokenization and the goal, which the whitepaper explains and feeds into; Livestock (planned, closed source) sits just above it, a product that uses the platform.Building blocksThe libraries template is made ofjson-rules reads the field map prisma-map producespermission rules are json-rulesrules-builder builds json-rules conditionstransition guards are json-rulesa transition is checked by permissionsrules-builderRule screensprisma-mapData shapetransitionsLifecyclesjson-rulesRulespermissionsWho can do whattemplate uses prisma-maptemplate uses json-rulestemplate uses permissionstemplate uses rules-buildertemplateThe whole SaaS appa Signet's lens is json-rulesKingdom decides access with permissionsFoundry uses json-rulesDeveloper experienceTools that help you workworktrees, init and CI rulescome with templateatlasMap of the codeglossNotes beside the codeconfigShared setupatlas checks its annotations with json-rulesAgenticAgents that work like you doFoundry 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)Artifactory will sign in with Kingdom (planned)Foundry runs each agent session on your machineOracle measures and tunes Foundry's docs and WardensoracleDid a fix stick?agent-sessionRuns sessionsbenchAgent challengesfoundryAgent workspacekcpCLIs through KingdomarchiveKeeps sessionsartifactoryShare agent worksignetRevocable passkingdomThe permission hubGovernanceCooperation at scalethe whitepaper explains why; the Inixiative project is the goalwhitepaperWhyInixiative projectchange.org meets Kickstarter on blockchainLivestock is a product that runs on the Inixiative platformLivestockTokenized cattle trusts

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

GovernanceThe project is the goal, and Livestock, closed source, is a product that uses it; the whitepaper explains why
Agentic
  • foundryAgent workspaceBuilt on agent-session, Archive, Signet, json-rules, gloss
  • kingdomThe permission hubBuilt on Signet, Archive, agent-session, permissions, json-rules, prisma-map, rules-builder
  • signetRevocable passBuilt on json-rules
  • archiveKeeps sessionsBuilt on agent-session, Signet
  • agent-sessionRuns sessionsBuilt on json-rules
  • kcpCLIs through KingdomBuilt on Signet
  • oracleDid a fix stick?Built on agent-session, Archive, Foundry
  • benchAgent challengesBuilt on agent-session
  • artifactoryShare agent work
Developer experienceBeside the stack: tools that help you work
  • atlasMap of the codeBuilt on json-rules
  • glossNotes beside the code
  • configShared setup
  • worktreesA copy per taskComes with template
  • initProject setupComes with template
  • CI rulesConvention checksComes with template
TemplateThe whole SaaS app, resting on the building blocks
  • templateThe whole SaaS appBuilt on prisma-map, json-rules, permissions, rules-builder, atlas, transitions, gloss
Building blocksprisma-map at the base
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.
  • transitions: Declarative lifecycles. Built on json-rules, permissions, config.
  • rules-builder: A headless rule builder. Built on json-rules, config.
  • atlas: A map of your code. Built on json-rules, config.
  • gloss: Explanations kept out of the source. Built on config.
  • config: The shared toolchain and theme.
  • worktrees: A worktree per task, with its own database and ports.
  • init: Sets up hosting, database and secrets for a new project.
  • CI rules: Checks that hold the codebase to its own conventions.
  • template: The whole SaaS app, built from the libraries. Under construction. Built on prisma-map, json-rules, permissions, rules-builder, atlas, config, worktrees, init, CI rules, transitions (to adopt), gloss (to adopt).
  • 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). Artifactory will sign in with Kingdom (planned).
  • Signet: A revocable pass on the owner's terms. Built on json-rules.
  • 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.
  • The whitepaper: How groups set rules and hold each other to them. The whitepaper explains why; the Inixiative project is the goal.
  • The Inixiative project: change.org meets Kickstarter on blockchain: a time-series governance platform, with tokenization. Planned. The whitepaper explains why; the Inixiative project is the goal. Livestock is a product that runs on the Inixiative platform.
  • Livestock: Tokenized cattle trusts in Uruguay and Argentina, a product on the Inixiative platform. Closed source. Planned. Livestock is a product that runs on the Inixiative platform.