Agent Trust & Assurance

Uderia
the trust story, visualised

Five visual stories and their companion architecture — how a Uderia agent is composed, signed, observed, enforced, proved, and kept in check; how the data it answers from becomes a signed, deterministic product; how every change it makes goes through a signed contract; and how any single answer shows, to anyone, what produced it. Then one worked example, on real national data, from an empty account to a grounded answer.

Visual story · the model

An Anatomy of Trust

The agent as a five-faculty star on two foundations, inside a membrane that breathes — identity, assurance, access, audit.

See the anatomy →

Visual story · from the outside in

The Life of a Uderia Agent

Born → Composed → Signed → Runs → Observed → Enforced → Proved → Kept in check. The end-to-end trust lifecycle of a single agent, peel by peel.

Read the story →

Visual story · the data layer

The Anatomy of a Signed Data Product

Declared → Proven → Signed → Confined → Consumed → Receipted → Composed. Determinism you can verify: same request, same governed SQL, same rows.

See the anatomy →

Visual story · acting on the business

The Anatomy of a Signed Action

Proposed → Landed → Contracted → Proven → Signed → Performed → Approved → Receipted. The write half: a model that grows beside its signed base, and rows that change only through a contract, a person, and a receipt.

See the anatomy →

Visual story · one answer, on the record

The Anatomy of an Answer's Evidence

Answered → Inventoried → Sealed → Kept → Compared → Exported → Verified → Anchored. For a real answer: what produced it, whether each part was signed and unchanged then — and a panel that verifies it in your browser.

See the anatomy →

Worked example

Seeing it done, on real data

The stories above describe the model. This one is a deployment: public national datasets, engineered to the standard, consumed by agents bound to their own ontology — with every screen along the way.

Teradata · NIBRS & CASE · four analysts

The Policing Analysts

Two national policing datasets engineered as AI-Native Data Products on Teradata, and four analysts that read a map of both. The whole path in pictures — empty account, one credential, one connection, one fork — ending at a number the analyst qualifies rather than simply states.

Walk it end to end →

Operate & read the surfaces

Trust UX FAQ — when something on screen is unclear Operations Guide — running the assurance stack The Numbers — published benchmarks Evidence Verifier — check an exported bundle offline

Companion architecture

Trust Membrane Agent Ops & Evaluation Agent Authority Evidence Signed Data Products (OBDA-READ) OBDA-MODEL & OBDA-ACT