KATLAS · Cierge Labs · synthetic transit demonstrator
Govern what happens
after a transit risk alert.
A synthetic demonstrator showing how HMRC- or Border Force-style teams could move from anomaly signal to authorised action, attributable receipt and learning outcome — without centralising every source dataset and without replacing existing customs systems.
Others can score the risk · KATLAS governs the action
The case
A transit declaration or movement event arrives, a partner analytics service flags elevated risk — but the intervention still needs authority, attributable evidence and a receipt.
What this demonstrator shows
Authority at the point of action. Federated evidence and provenance. A receipt for each material intervention. And a structured learning loop back to the rules.
Why this exists
Coordinate, not centralise.
Customs and border operations span declaration, manifest, border event and trade-document services. Analytics and rules engines can score risk — yet interventions still require authority, attributable evidence and an audit trail that holds up later.
Transit Risk Decision Integrity shows how a lightweight, policy-governed evidence layer can sit alongside existing services — giving operations a shared, auditable stream of governed intervention without forcing raw customs, trader or cargo data into a new central platform.
Trusted, low-exposure coordination across services, people and systems. Faster, cheaper, with less risk — and without ripping anything out.
Architecture
A single view
without centralising the estate.
Source services keep custody of their own data. KATLAS coordinates governed alerts, evidence references, authorised actions and receipts across those boundaries — creating an operational view of what is happening without turning one platform into a single point of failure.
Data stays where it is
Declarations, manifests, border events and trade documents remain in their source services. KATLAS uses references, provenance markers and evidence hashes rather than copying customs or cargo data into a new central store.
Authority is checked at the point of action
Before a hold, inspection, clarification request, release or escalation, the system checks role, policy, evidence sufficiency and rule version.
Receipts create the shared view
KATLAS records the governed intervention — who acted, under what authority, on what evidence, with what outcome — and feeds confirmed outcomes back to the rules.
CAR
Custody. Authority. Receipts.
Custody controls the evidence. Authority governs the action. Receipts prove what happened.
Who controls the evidence
Source services and third parties retain custody of declarations, manifests, border events and trade documents. KATLAS surfaces references, provenance and evidence hashes — never raw cargo or trader data.
Declaration · manifest · GVMS · trade document · third-party
Who may decide
An authorised role — case officer, border officer, rule owner or supervisor — decides hold, inspect, clarify, release with monitoring, escalate or close. Authority is checked at the point of action, not after.
Triage · hold · inspect · clarify · release · escalate · close
What proves it
Receipts prove the governed intervention without exposing raw customs, trader or cargo data. The KATLAS receipt references actor, role, policy, rule version, evidence boundary and outcome.
Signed by the live KATLAS node
KATLAS
The decision-integrity layer between risk analytics and operational action.
KATLAS does not replace CDS, NCTS, GVMS or Border Force operational systems. It governs the actions around them: who raised an alert, who had authority, what evidence supported the decision, what intervention followed, and what receipt proves the outcome.
KATLAS does not create another central database. It creates governed connections between services, people, policies, rules and evidence — letting an operations lead see the operational picture while customs and trader data remain under local custody.
Risk alerts arrive from analytics services. KATLAS opens a governed Risk Decision Case.
The right authorised role gets the action request, with sufficiency notes and policy basis.
KATLAS records each intervention as an attributable receipt and posts confirmed outcomes back to the rules.