AttexaTrust Fabric · Evidence
The Attexa Witness layer

Independent, tamper-evident evidence for every AI action.

Witness signs and hash-chains what your AI did into receipts anyone can verify against a key you hold. Verified Actions adds governance on top: a policy gate, a capability check, and optional human attestation before a consequential action runs. Evidence first. Governance on top.

Evidence layer · L1 Verifiable by anyone Open protocol since 2025
01 · The fabric

One witness fabric. Two primitives.

Witness is the evidence layer beneath everything. Verified Actions is governance built on top of it. The same fabric hardens from evidence, to witnessed conformance, to policy-gated action — witnessing where Attexa is beside the path and enforcing where Attexa owns the boundary — so coverage grows without a rebuild.

Witness · the evidence layer

Signs and hash-chains tool calls, results, approvals, generated artifacts, and memory writes into independent, portable receipts. Answers: what happened?

Verified Actions · governance on top

Policy and capability checks before a consequential action runs, with optional human or domain attestation. Answers: was it allowed, and who stood behind it?

Verified Actions
SDE Workbench
Agent Anything
Verified Actions
Policy & capability checks · governance
Witness
Signs & hash-chains every AI action · evidence
Verification runs beneath, against a key you hold

02 · Why a Witness receipt is trustworthy

Four properties that make the evidence hold.

Independent

Evidence that does not depend on the party being governed, or on a vendor dashboard.

Tamper-evident

Hash-chained, so any change to the record is detectable by anyone who checks it.

Portable

Travels outside any system. Verify it in any language, on any machine, with no Attexa service in the loop.

Customer-owned

The evidence is yours and outlives every participant: the AI vendor, the operator, and Attexa.


03 · Depth on demand

Three layers of assurance, mapped to plain questions.

The default is observed. Enforcement and accountability are named tiers you reach as the stakes rise, on the same fabric. At L2, the same policy layer can prevent (enforce) or prove (sentinel) — whichever the situation allows.

L1
Witness
Observed
Records and signs the action path. Independent evidence it occurred as recorded. The evidence floor.
What happened?
L2
Policy Witness
Policy-witnessed
Evaluates behavior against policy in two postures. As an enforcer, it allows, denies, or escalates a consequential action before it runs. As a sentinel, it watches an enrolled channel outside Attexa’s control and signs when a governed state is held, breached, or restored.
Was it allowed — and did it stay that way?
L3
Domain Attestor
Domain-attested
A credentialed person signs approval over the specific action: identity, claim type, request digest, decision. Verifiable forever. Something a vendor log cannot produce.
Who stood behind it?
Enforcer
Sits in the action path. Allows, denies, or escalates before execution. Used where Attexa owns the action boundary. Prevents.
Sentinel
Sits beside the path. Verifies a signed self-governance claim against an enrolled evidence channel and signs each state transition — in policy → out of policy → back in policy (held → breached → restored) — pushed to every party with standing. Used where Attexa can’t or shouldn’t block: model-routing floors, provider decisions, settlement rails, substrates you don’t own. Makes conformance or breach undeniable.

The same L2 policy layer, two stances. Sentinel claims cover explicitly enrolled channels with source-bound evidence — not global coverage.


04 · How it attaches

A wrapper at the action boundary, not a rebuild.

Witness attaches where your AI already executes its actions. The model does nothing differently: no retraining, no prompt changes.

Before the action
Check policy, record intent
The requested action is evaluated and its intent is signed.
Attexa
Policy gate
Capability check
Witness result
After the action
Record and sign the result
The outcome is hash-chained into a portable receipt.
Signed receipt chain Portable evidence bundle Verifier-compatible certificate

05 · A small, explicit trust base

Standard cryptography. A key you hold.

Witness uses standard primitives only, so the trust path is intentionally small: an open protocol, standard cryptography, and a key the customer holds. No vendor dashboard is required to verify a receipt.

Ed25519 signatures
SHA-256 hash chaining
Canonical JSON payloads
Held-key verification, offline
Open, independently implementable protocol
receipt.json
{
  "action": "tool.write_file",
  "prev":   "sha256:3f9a…c041",
  "payload":"sha256:b71e…02ad",
  "ts":     1781049600,
  "sig": {
    "alg": "ed25519",
    "by":  "witness:eng-01",
    "val": "a7d2…99fe"
  }
}
// verify against a key you hold

06 · The components

Three ways to adopt the fabric.

Verified Actions drops onto any surface. The deployment products each run agents on a specific footing, with Witness beneath every one.

Production-proven

Verified Actions

The governed-action layer for any AI surface. Policy gates, capability checks, and human attestation for consequential actions, with independently verifiable evidence. Drops onto what you already run.

SDE Workbench

A governed cloud development environment. Developers get a familiar AI coding workstation; security gets receipt-backed evidence of every model call, tool use, and developer action.

Agent Anything

A governed environment where an orchestrator builds and runs a team of agents for your organization, with the Witness layer beneath every agent so each one’s actions are signed automatically.


07 · Exact about the technology

What it proves, and what it doesn't.

Proves what an AI did, in what order, under what policy, with what approval, independently, and lasting beyond every participant.

A small, explicit trust base: an open protocol, standard cryptography, and a key you hold. Not a blind one.

Does not expose hidden model reasoning, and does not claim enforcement unless a Verified Action policy gate is present.

Does not make you compliant; it produces the evidence your compliance program needs.


Verifiable by anyone

A regulator, an auditor, a customer, or a counterparty can verify a receipt against a key you hold, in any language, long after the original system or vendor is gone.

Witness turns AI action logs into independent, tamper-evident, portable evidence. Verified Actions governs which consequential actions are allowed. Together they produce the evidence your compliance program needs, owned by you.

Contain the agent. Govern the action. Verify the outcome.