Home/Trust

The line that never moves.

Models propose; deterministic code or humans commit.

Every Enkidu system draws the same line: machines propose, correlate, and explain; humans decide what matters. Each sector states it in its own terms.

In their own terms

One line, every sector

“Fuse intelligence. Never authorise combat.”

Defence · Enlil
Read the full passage →

“It raises the alert. It never takes the action.”

Urban / Public Safety · Lamassu
Read the full passage →

“Not a number someone typed. A number a named, verifiable process produced.”

Legal · Dinanu
Read the full passage →

“The AI produces the input. The clinician makes the call.”

Medical · Ninkarrak
Read the full passage →

“It assembles the intelligence. It never renders the judgment.”

Intelligence · Massartu
Read the full passage →

“It builds the case. It never lays the charge.”

Law Enforcement · Misharu
Read the full passage →
The mechanisms

How the line is enforced

01

Models propose; humans commit

“Baru never authorises action. It proposes, correlates, and explains; a cleared human operator decides. That line never moves.” Its counterpart on the discovery side reads the same way: AI does the reading; people make the findings.

02

Delegated authority is bounded

Agents work inside trust zones Z0–Z3 under a deny-by-default policy engine, and scoring formulas, rubrics, and taxonomies live in code as authoritative ground truth — the language model interprets, extracts, and drafts; it never assigns the score. Every effect that reaches the outside world is gated behind an earned trust zone and an accountable human decision.

03

The record proves it

Every finding carries a source citation resolvable to a specific document and passage; outputs lacking citations are rejected, and coverage gates verify mechanically that nothing was silently dropped. The finished work product carries a certification of that entire chain — every claim cited to source or rejected, every release signed off by a human. Verification never requires trusting the machine; it requires checking the record.

Not policy — property

Built into the stack

Kittu asserts trust claim by claim at release and verifies them step by step at run time: every claim is an assurance case — claim, argument, evidence — bound to exactly one policy with an explicit threshold and owner, satisfied only when the measured outcome meets the threshold and the evidence chain validates. Shedu supplies the identities, signatures, and sealed links that make every one of those claims verifiable end to end. Both are capabilities of the Ekur stack — every implementation inherits them.

None of this is policy that could change with a product cycle.

The line is enforced by architecture — mandates, bounded authority, and a verifiable record — and it holds in every sector we serve, in every configuration we ship. That is what trusted means here: not a promise to believe, but a record to check.

Enkidu

Check the record

Ask for the assurance dossier behind any claim on this page — the policies, the evidence chain, and the trace.

Request a briefingTalk to the team