Reality, with provenance
Every entity, track and relationship enters one Reality Graph through a single write path. No source, no confidence, no classification label means no write.
Command that can prove every decision.
Verity Command unifies the operating picture, the authority to act and the evidence behind every action into one governed system for defense, government and critical infrastructure.
Three rules the system never bends.
Speed without authority is a liability. Authority without evidence is an assertion. Verity Command is engineered so that the picture, the permission and the proof are the same system, not three integrations stitched together after the fact.
Authority, before action
One Authority Kernel decides every request. Deny takes precedence. When a dependency is unavailable, the answer is no.
Evidence, before effect
The signed record of a decision is committed before anything moves. If the ledger cannot write, the action does not happen.
One spine from sensor to effect.
Recommendation, authorization and execution run as separate services with separate credentials. Nothing reaches an effector without passing the kernel, and nothing passes the kernel without leaving evidence.
Request path
Evidence committed before effect
Refusal, recorded like any other decision
LAYER 01
FABRIC·GRAPH fabric/eu-01
NODES 0 · EDGES 0 · REFUSED 0
Nothing enters without its source.
Every track, entity and relationship is written through one governed path. A record arrives with its provenance, a confidence value and a classification label, or it does not arrive at all. Where two sources disagree, both are kept and the disagreement is shown.
FABRIC·GRAPH — illustrative. Confidence shown per node; refused records never cross the write path.
LAYER 03
LEDGER·CHAIN ledger/eu-01
BLOCKS 0 · VERIFIED 0 · BROKEN 0
A chain that shows when it has been touched.
Each decision is committed as a signed block before the effect it authorizes is released. Verification walks the chain continuously. An altered block no longer matches the hash its successor carries, and the break is surfaced rather than repaired.
LEDGER·CHAIN — illustrative. Block 07 is altered on purpose to show how a broken link is reported.
LAYER 04
THEATER·HORMUZ ais+radar
CONTACTS 0 · CONFLICTS 0
One strait. Every track accounted for.
The reference theater is the Strait of Hormuz: dense traffic, contested signals and consequences measured in hours. Every contact carries its source, its confidence and the contradictions the fabric has found.
Contacts
Select a contact
- Source
- —
- Last report
- —
- Speed
- —
- Label
- —
- Contradiction
- —
Confidence
LAYER 05
FEDERATION·EDGE edge/node-04
NODES ONLINE 4/4 · LEASE --:--
The link drops. The authority does not.
Edge nodes hold a signed lease with an expiry. When the link fails they keep deciding inside that lease and reconcile deterministically once it returns. When the lease runs out they stop deciding. Authority expires; it does not drift.
FEDERATION·EDGE — illustrative. Node 04 loses its link, runs on a bounded lease, then fails closed.
Sovereign by architecture, not by contract.
The customer holds the keys, the policy and the data. The architecture is shaped so that no vendor, including us, sits in the path of a sovereign decision.
You hold every root of trust.
Signing, encryption and identity roots are generated and kept inside your enclave, on your hardware.
Policy is signed, versioned data.
Rules and operating procedures ship as reviewed configuration with a full history, not as code only a vendor can change.
Disconnected, with bounded authority.
Edge nodes keep operating when links fail, under time-limited leases that expire instead of drifting.
AI that knows what it may read.
Models are routed by data classification. Open-weight models serve sensitive work inside your boundary; high-consequence actions stay with people.
Built for missions where the record matters.
Wherever an action must be defensible to a commander, a minister, an auditor or a court.
Maritime security
Chokepoints, sanctions enforcement and contested traffic.
Defense command
Coalition operating pictures with governed release.
Critical infrastructure
Energy, ports and networks under continuous threat.
Crisis government
Ministries coordinating under pressure and scrutiny.
Questions we are asked before a briefing.
Short answers to what technical and security teams raise first. A briefing goes further, against your own environment and constraints.
Where does Verity Command run?
In an environment you control: your own data centre, a sovereign or national cloud you select, or an isolated network with no external connectivity. The architecture is designed so that no component depends on a vendor-operated service in order to keep working.
Who holds the cryptographic keys?
You do. Signing, encryption and identity roots are designed to be generated and held inside your boundary, on your hardware. The design places no vendor key in the path of a decision and keeps no vendor copy of your key material.
How is AI used, and what is it allowed to do?
Models and agents are principals with their own identity, delegation and limits. Routing is decided by data classification, so sensitive work is designed to stay with models inside your boundary. An agent may recommend; it is not given authority over high-consequence actions, and it cannot exceed the authority of the person who delegated to it.
What happens when the network fails?
Edge nodes are designed to continue under a signed lease with an expiry, deciding locally within the authority that lease carries, and to reconcile deterministically on reconnect. When the lease expires the node stops deciding rather than continuing on stale authority.
How do you approach export control?
Deployment and support are subject to the export control rules that apply to the parties involved. Our current position, and the questions we ask before an engagement, are set out in the export control notice.
How do we arrange a briefing?
Send a request through the briefing form with your organization, your role and the environment you are considering. A briefing covers the architecture, the security model and the limits of what has been built so far, with a technical audience.