How it works
A signal arrives. A team forms around it. Members reason with memory and skills, inside their authority. Decisions are recorded. The books get sharper. Then it happens again, without anyone asking.
The loop
Signal on the mesh
Team self-composes
Reason with memory
Decide or escalate
Record and learn
The layers
Each team member is an agent with a role, a goal, a backstory and a library of skills it loads on demand.
Teams are crews. Crews can call other crews, so a plan built by one team can be interrogated by another while it is still being written.
A Redis-backed event bus. Everything that happens in the business is a signal: a data feed, a system event, a human decision, another team's output.
Teams subscribe to signals and wake when something relevant happens. That is what ambient means mechanically — no schedule, no click.
A governance boundary around every team and every party. A membrane decides what enters a team's attention, what leaves it, and in what form: it distills, redacts and routes.
It is judgment, not a filter — the difference between what a good employee thinks and what they say.
This is how a supplier's agent sits in a retailer's planning session without the supplier's cost data crossing the boundary, and how medical and commercial stay separated in pharma.
Six layers: working, session, episodic, domain-operational, institutional, and federated — cross-organization and membrane-governed.
Before a team reasons or acts it retrieves a structured context pack: facts, constraints, feasible actions and open questions.
Mistakes are written back. The team never re-learns your business.
Each member carries a decision matrix: decide alone, decide with a peer, or propose to a human. Escalation rules are explicit.
The decision ledger records every decision, its inputs, its reasoning and its outcome.
The ledger is the performance review, the audit trail, and the source of the books that set prices.
Model routing
Every job is routed to the cheapest model that achieves the result we guaranteed. Outcomes are graded and fed back into routing. You never pick a model, and you never pay for a model you did not need.
Interoperability
Teams work across your existing systems — CRM, ERP, ChMS, planning tools, Microsoft 365 — through governed connectors. We do not require a single system of record, because the problems we take on never had one.
Data-readiness assessment
Role and authority definition
Resumes approved
Team goes live with recommendations only
Autonomy expands as the ledger earns it
The guarantee
Every competitor asks you to trust a demo. We ask you to read a contract.
Each member of each team carries a bond. The team is accountable for the work, not just for the effort.
Every job sits on a price list with a stated result. No seats. No token meters. If a job fails, we pay.
For every job we have ever run we hold what it cost, which model ran it, and whether it worked — pooled across thousands of organizations.