Esta página ainda não está traduzida. Está a ler o original em inglês.
Part of a stack
AgentiCCells is one of several separate ventures that use each other. Dinis Cruz maps them in The intersection (newsroom.sgit.ai, 2026-11-16). This page says where we sit and links up and down the stack. No money changes hands between the ventures; the uses are real, the transactions are not (the same article says so).
Jump to
Under us
- SGit: git for encrypted vaults. Our cells keep their work in vaults and message each other on lanes.
- SHarness: a behaviour policy for every process an agent starts, enforced by the kernel.
- Keys: a key for every person and every agent. A key for every person.
- Agent Behaviour Policies: the standard under all of it, housed at RiskMandate for now.
Beside us
RiskMandate writes the behaviour policy. Already running agents and need to control them? RiskMandate writes the behaviour policy, from one agent to hundreds. We sell the team; they sell the control. A team is usually set up with its policies, so a dual sale is possible. Both sites sell on one ladder; every price on this site is a first proposal.
On top of us
- The hub: every cell we have made, one page each, with demos marked as demos.
- RiskMandate at Web Summit: the first site the factory made from a request file.
- The book: an agentic cell in the form of a book.
- The newsroom: the articles that explain each part.
Worked examples to read
Three newsroom articles of 17 November show pieces a cell could be made from. None is sold as a cell yet; each says what it does not claim.
- Deploy sgit from CI: a team runs its own sgit server in its own cloud account, using the pipeline pattern of our site factory.
- Shipping an iOS app with agents: agents without a Mac build, test and send a native app to testers.
- Build on VoiceDebrief: the techniques of an open-source voice app, with the code to read.
How the work is handed out
One person sets the work and owns the outcome. One conductor agent hands it out and collects the reports. Specialists, each with a role and a behaviour policy, do it. A reviewer checks every claim. A person decides what goes out; agents never send or post. Dinis Cruz sets this out, with one addition (a file every agent reads first, so the door can close), in Who hands out the work.
Read next
- Your own agentic cell, end to end: the plan for the website cell as a workflow, with three human gates. A plan: none of it exists end to end yet, as the article says.
- The intersection: the map.
- The site factory works
- Atomic cells, end to end
- The cell is the unit
- Six setups of an agentic system
- The team's operating system
Not sure which site fits? Write to agent@riskmandate.ai. A person reads and answers it.