for agents/llms.txtv0.14.128

Home / Articles / The intersection: SGit, SHarness, Agent Behaviour Policies, RiskMandate and AgentiCCells as one stack of separate companies, now with real customers, real usage and real examples, one ladder of offers on every site, and a plan to align them all

The intersection: SGit, SHarness, Agent Behaviour Policies, RiskMandate and AgentiCCells as one stack of separate companies, now with real customers, real usage and real examples, one ladder of offers on every site, and a plan to align them all

By · 2026-11-16 · article v1.1.0, 2 versions · newsroom v0.14.117 · strategysgitsharnessabpriskmandateagenticcellspromptugalvoicedebriefpositioningarticle

Abstract: What we have now is a ridiculously powerful workflow, and it runs across what are really several companies. SGit, encrypted vaults and lanes, is one foundation; SHarness, kernel-enforced Process Behaviour Policies, is another; a key for every person and agent is the third. On top sit Agent Behaviour Policies, the standard that underpins all of it, housed at RiskMandate for now. RiskMandate sells those policies. And AgentiCCells sells agentic teams built on all of it, which is what was missing: RiskMandate had a strong idea and a hard first step, because people asked how to start, and a £500 cell is a way to start. With the site factory, the last manual piece, creating repositories and making DNS and AWS changes, is now a commit, so delivery can scale. Above them are the customers and uses: PrompTugal.news going local town by town, the Web Summit team, the sites the factory makes, five apps, VoiceDebrief, and this newsroom. Money is not changing hands between them, but each uses the others, and that is real usage I can point to. So every site should now sell something on the same ladder of one-off prices, £500, £1,500, £5,000 and £20,000, show its examples, link to the others and to the content here, and say where it sits in the stack. This is the map, and the plan to align them.

One stack, several companies: foundations, the ABP standard, RiskMandate, AgentiCCells, and the customers and uses.

In short

Why now

Until a few weeks ago, these were ideas with demos. Now we have real customers, real usage and real examples. Six of us, with around 250 agents, ran a team operating system, a newsroom, a storm site, a fringe guide and native apps around Web Summit, all on this stack (ten days at Web Summit). PrompTugal.news has gone local, with an agent for every town in the Algarve (every story has an address). And last night the AgentiCCells site factory made a website from a commit in two and a half minutes (the site factory works), which removed one of the last pieces that was still manual and painful.

What that shows is an intersection: a set of companies that each do one thing, and that, together, go end to end. It is time to map it, and to make every site say so.

The foundations

The standard: Agent Behaviour Policies

Agent Behaviour Policies are the underpinning of all of this: for one agent, the grant (what it can reach), the mandate (what it was asked to do), the gap between them, and the barrier that actually stands in the way. The Web Summit team published policies for its agents, PrompTugal.news keeps 45 roles in one policy file, and the same grammar now describes a CI pipeline (CI behaviour policies). For now the standard is housed at RiskMandate; its open home will come later, with the open security community.

RiskMandate, and what it was missing

RiskMandate sells Agent Behaviour Policies for real agents: from a downloaded pack at £10 to a policy corrected for your situation at £500, and two sessions with a professional's signature at £1,500. Its use case is the summit: the team's agents, the stand, and the film (know the reach).

What it was missing was a sale that is easy to start. A policy is valuable, but people asked: how do I start? What do I do on day one? That is the gap AgentiCCells fills.

AgentiCCells: the first step

AgentiCCells sets up small teams of AI agents, in the customer's accounts or ours, as fixed-price cells: one agent or a website at £500, a few sessions handed over at £1,500, a team with a conductor, keys and a board at £5,000, and a network of teams at £20,000 (six setups of an agentic system). Every cell runs on SGit's vaults and lanes, gives each agent a key, and puts each agent under a behaviour policy: AgentiCCells uses RiskMandate, and sells it, as part of something a customer can buy today. With the site factory, delivery is now a commit away (atomic cells, end to end).

The customers and uses

Who uses whom, with evidence: each tick is something in a repository or on a live site.

Money is not changing hands between these companies, but each uses the others for real, and that is evidence a customer can check.

One ladder on every site

One ladder on every site: £500, £1,500, £5,000 and £20,000, each company selling its own thing at each step.

Every site should have something for sale, and the pattern is the same: £500 for one workflow, done in a session; £1,500 for two sessions and a handover; £5,000 for a few days and a team; £20,000 for a bespoke engagement. Each company sells its own thing at each step: a cell, a policy, a vault, a process policy, a set of debriefs, a town page. AgentiCCells and RiskMandate already show prices; the others are proposals in the figure.

Separate companies, one map

I see each of these as a separate company, with its own investment, its own flows and its own go-to-market:

The plan: align every site

Each site should carry the same few things, in its own words:

  1. One line on what it is, and where it sits in the stack, with the stack figure and its own layer highlighted.
  2. The ladder, with what it sells at each step, and a way to buy or start.
  3. Real examples and customers, with links: the summit, PrompTugal.news, the factory's sites, the apps.
  4. Links to the others, above and below it in the stack.
  5. Links to the newsroom's articles that explain it.
  6. A contact and an outreach path, so a reader who arrives on one site can find the one that fits.

And one gap to close: SHarness has no user in the map yet. It is the foundation with the most to show, and the next showcase should be a team of agents whose processes run under it.

What this does not claim

Where this comes from

My own thinking, 16 November 2026. The live sites: sgit.ai, sharness.ai, abp.sgit.ai, riskmandate.ai, agenticcells.ai, promptugal.news, voicedebrief.ai and its iOS app, read on 16 November 2026; the PrompTugal.news, AgentiCCells and PrompTugal iOS repositories. Earlier on this site: ten days at Web Summit, the site factory works, CI behaviour policies, every story has an address, identity for agents, layer by layer, six setups of an agentic system, atomic cells, end to end, native apps by agents, know the reach.

Peer review Not reviewed yet. Review it

Threads

Startups & strategyAgents & policy This article as a graph →

Builds on

Continued by

All articles · All graphs

Article No. 427 · start a reading list with it

Want the next issue by email. One issue a week or so: what was published, what it adds up to, and what is worth your time. Subscribe to the SGit Newsroom →

← All articles

Reviews

Reviews on the record, by agents, the editor and the desk, against the criteria. Each is kept for good and answered finding by finding. All reviews →

No reviews yet.