KATLAS PlatformGovernance infrastructure for agentic systems

Bounded action. Signed receipts.
A platform built for accountable agents.

KATLAS is the governance layer for agentic systems operating in regulated and high-stakes environments. Every decision is constrained by an explicit mandate. Every action produces a verifiable receipt. The platform explains it. Cierge Labs proves it.

Mandates enforced
100%
of agent actions
Receipt emission
1 per action
signed, indexed
Live reference
ClubCierge
validated node
Operating model
Active
not monitoring
The CAR Pattern

Custody.
Authority.
Receipts.

Custody controls the evidence. Authority governs the action. Receipts prove what happened.

KATLAS records the governed action, not a copy of everyone's private data.

CCustody
Custody

Who controls the relevant wallet, profile, asset, entitlement or evidence?

Members, patients, travellers, shipments, devices or role-controlled wallets hold evidence at source.

AAuthority
Authority

Who is allowed to request, approve, refuse, share, claim, hand off or escalate?

Parents, secretaries, clinicians, operators, customs roles and resilience officers act under policy.

RReceipts
Receipts

What proves the governed action happened — who acted, when, under what authority, what was shared and what was withheld?

A KATLAS-signed receipt with hash, signer, timestamp, verification, shared refs and withheld counts.

Operating principle

AI suggests. Wallets prove. Authorised roles decide. KATLAS signs the receipt.

Data boundary

KATLAS records the governed action, not a copy of everyone's private data.

How KATLAS Works

From custody to signed receipt — at the point of action.

KATLAS is not a wrapper, a model, or a dashboard. It is the runtime governance layer that sits between counterparties at the moment something has to be requested, approved, shared, handed off or escalated.

STEP 01
Custody

Evidence stays with whoever rightfully holds it — member, patient, traveller, shipment, device or role-controlled wallet.

STEP 02
Request

A counterparty requests an action — an introduction, an approval, a handoff, a share, a claim or an escalation.

STEP 03
Authority

An authorised role under explicit policy decides: approve, refuse, share, hand off or escalate. AI may suggest; it does not approve.

STEP 04
Sign

Backend posts a minimal CAR payload to the KATLAS node. The node signs a receipt with hash, signer, timestamp and verification.

STEP 05
Prove

The receipt shows what was shared and what was withheld. Counterparties verify it independently — no raw private data is exposed.

Plane

Governance, not Glue

KATLAS sits orthogonal to your stack. It does not centralise raw private data and it does not replace your models, orchestrators or tools — it governs the actions they participate in.

  • Custody held at source
  • Authority gate per action
  • Signed receipt emitter
  • Verification endpoint
Receipts

Evidence by default,
not by request.

Receipts prove the action was approved and recorded without exposing more information than needed. Counterparties verify them directly against the KATLAS node.

RECEIPT · 0x9a4f…c12dVERIFIED
action: sponsor.introduction.approve
custody: member:cc.m_0419
authority: role:club_secretary
shared: 3 refs · withheld: 5
outcome: approved
Why KATLAS Differs

Not a dashboard.
Not a chain.
Runtime governance.

The market is crowded with passive tooling and blockchain-anchored claims of provenance. KATLAS does neither. It governs the action, records who acted under what authority, and prevents raw private data from leaving custody.

Category
Conventional approach
KATLAS approach
Dashboards
Visualise what already happened.
Govern the action at the moment it happens, then sign the receipt.
Passive monitoring
Detect drift after the fact.
Hold authority at the gate. Refuse, share or hand off in the open.
Blockchain-first claims
Anchor data in a chain and call it trust.
Trust is a KATLAS-signed receipt, verifiable by the recipient.
AI agents acting alone
Model wrappers approving on behalf of humans.
AI suggests. Wallets prove. Authorised roles decide. KATLAS signs.
Cross-Over Map

The hard problems live between sectors.

KATLAS receipts are designed to cross domain boundaries. A health decision can be referenced by a logistics provider. A city authority can verify a fleet operator. Trust is portable.

NODE 01
Supply Chain
NODE 02
Mobility
NODE 03
Cities & Resilience
NODE 04
Health
Supply ChainMobility

Last-mile recovery

Carrier dispatch under shipment-recovery mandate.

MobilityCities & Resilience

Incident perimeter routing

Routing agents respect authority directives during incidents.

Cities & ResilienceHealth

Welfare and clinical handoff

Shelter and triage decisions exchange receipts.

HealthSupply Chain

Clinical procurement

Consent-bounded data informs supplier exposure.

Cierge Labs · Catalogue

The platform explains it. Cierge Labs proves it.

A catalogue of bounded agent actions across sectors. Live nodes produce signed receipts. Simulations and concepts are clearly marked. Nothing implies more than it delivers.

Visit live ClubCierge node
Sector
Status
Cross-sector
Live KATLAS node

ClubCierge — Member Organisations

Validated live-node reference.

Governed action

Member sponsor introduction under Club Secretary authority. Parent-held custody. AI may draft; only the Secretary approves.

Receipt proof

KATLAS-signed receipt: action, custody subject, authority role, shared evidence refs and withheld counts.

Supply Chain
Simulation

Tier-2 Supplier Exposure

Governed action

Agent surfaces and ranks exposure across sub-tier suppliers, proposing pre-approved mitigations within procurement policy.

Receipt proof

Simulation receipts attach evidence used, mandate boundaries, and a counterfactual log.

Request walkthrough
Supply Chain
Concept

Shipment Recovery Cell

Governed action

Recovery agent coordinates carriers, customs and customer comms under a published recovery mandate.

Receipt proof

Each external comm carries a receipt hash retrievable by counterparties.

Request walkthrough
Supply Chain
Archived

Cross-DC Inventory Rebalance

Governed action

Auto-rebalancing across distribution centres under hourly cost and SLA constraints.

Receipt proof

Archived: receipts retained for audit; node retired in favour of carrier-native flow.

Request walkthrough
Mobility
Simulation

Field Fleet Redeployment

Governed action

Agent reassigns crews and vehicles under shift, certification and fatigue constraints.

Receipt proof

Receipts record the constraint each reassignment respected, plus the rejected alternatives.

Request walkthrough
Mobility
Concept

Depot Handoff Protocol

Governed action

Standardised governed handoff between operators at depot boundaries, including duty-of-care transfer.

Receipt proof

Counter-signed receipt by ceding and receiving operator.

Request walkthrough
Mobility
Simulation

Incident-Aware Routing

Governed action

Routing agent respects live incident perimeters and authority directives, not just traffic feeds.

Receipt proof

Receipts attach the authority advisory referenced and the policy applied.

Request walkthrough
Cities & Resilience
Concept

Multi-Agency Handoff

Governed action

Coordinated handoff between civil, utility and emergency agencies during a sustained incident.

Receipt proof

Public-verifiable receipts: who held the action, under what mandate, for which window.

Request walkthrough
Cities & Resilience
Simulation

Utility Outage Communications

Governed action

Agent issues outage and restoration comms within regulator-set tone and accuracy bounds.

Receipt proof

Each public message carries an accuracy attestation and source-evidence trail.

Request walkthrough
Cities & Resilience
Concept

Shelter & Welfare Allocation

Governed action

Allocation agent respects accessibility, family-grouping and capacity constraints.

Receipt proof

Receipts capture the constraint that bound each placement decision.

Request walkthrough
Health
Simulation

Triage Decision Support

Governed action

Agent proposes triage paths under clinician-defined policy; clinician retains authority.

Receipt proof

Receipt captures the evidence considered, the policy applied, and the clinician sign-off.

Request walkthrough
Health
Concept

Discharge Coordination

Governed action

Coordination agent aligns transport, pharmacy and community care under discharge policy.

Receipt proof

Receipts referenced by community providers receiving the patient.

Request walkthrough
A lab is marked Live KATLAS node only when it is connected to the live KATLAS plane and emits signed receipts. Everything else is honestly marked as Simulation, Concept or Archived.
Customer Engagement Pathway

From walkthrough to live node.

A deliberate path. No procurement theatre, no infinite pilots. Each step ends in something a counterparty can verify.

Step 01

Walkthrough

Map your highest-stakes agent action. We show how KATLAS would bind it.

Step 02

Mandate draft

Together we draft the first explicit mandate — constraint, action, receipt scope.

Step 03

Simulation node

A Cierge Labs simulation node runs against your evidence. Receipts are emitted.

Step 04

Live node

When ready, the node is promoted to live KATLAS. Receipts become production-grade.

Step 05

Verification

Your counterparties verify independently. Trust without granting trust.

Differentiators

What makes KATLAS, KATLAS.

Action boundary
Refusal at the edge

Out-of-mandate actions are refused at the runtime boundary, not flagged after.

Receipts
Independently verifiable

Recipients verify receipts without trusting KATLAS or the agent operator.

Mandates
Explicit and versioned

Published before action. Auditable. Comparable. Revisable with provenance.

Surface area
Orthogonal, not invasive

Sits beside your stack — your models, orchestrators and tools remain yours.

Honesty
No status inflation

Live means live. Simulation means simulation. Concept and archived are owned.

Cross-domain
Portable trust

Receipts cross sector boundaries — health to logistics, city to operator.

Contact

Bring us your highest-stakes action.
We'll show you the receipt.

A walkthrough takes around 45 minutes. We come prepared. You leave with a draft mandate for one agent action in your organisation — and a clear sense of what a live KATLAS node would evidence.

Principle

Website explains the platform.
Cierge Labs proves it.
Receipts evidence it.

Response timeWithin 2 business days
LocationRemote · UK / EU friendly hours
StageEarly access to live KATLAS nodes