Know what authorized each decision.

FieldHash Ledger records the context, actions, and precedents allowed or withheld at each governed handoff, together with the authority source, reason code, and verification references reviewers need later.

The review problem

A governance gate is only useful if reviewers can inspect what happened later. If an answer or agent action is challenged, legal, security, compliance, and model-risk teams need more than the final response. They need the governed path.

FieldHash Ledger records which context, action, or reviewed decision was allowed or withheld, which authority applied, and why. An execution receipt, when available, records the executor's reported result separately.

Retrieval explains what looked relevant. Tool registries explain what exists. FieldHash Ledger helps reviewers verify what was allowed to influence the answer or action.

What the Ledger records

Approved context passed to the model

Blocked stale, rejected, superseded, or out-of-scope records

Governance reasons, scope metadata, and policy references

Rollback and supersession links where available

Packet hashes, checkpoint references, and signed evidence records where configured

Exports for reviewer, SIEM, GRC, or internal audit workflows where configured

Inspect the decision without rerunning the model.

FieldHash captures the authority decision, hashes its evidence, and exports a packet reviewers can inspect. Stronger tamper evidence depends on the deployment profile: checkpoint signing, customer-owned logs, key custody, or signed checkpoints the customer keeps off-host.

Evidence packet

A compact record of allowed context or actions, blocked alternatives, review routes, authority sources, and handoff metadata.

Customer-owned logs

Deployments can export events to customer review systems, SIEM/GRC workflows, or internal audit stores where configured.

Configured checkpoints

Governance events can be hash-chained, checkpointed, and signed, and the customer can keep signed checkpoints off-host. Operator resistance is strongest when checkpoints or keys sit outside the operator boundary.

Local review

Evidence packets are designed for reviewer inspection without requiring raw protected content to be sent to a third-party validator.

Assurance is configured, not assumed.

A local packet can make the answer path reviewable. It does not, by itself, make the operator unable to rewrite history. Buyers who need stronger operator resistance should configure customer-owned exports, signing custody, or off-host checkpoint retention in the deployment agreement.

Tier 1

Reviewable packet

Records allowed and blocked items, reason codes, authority-source references, a packet hash, and the prior hash for reviewer inspection.

Tier 2

Signed packet

Binds the exact packet payload to an expected signer so a reviewer can verify both the content and signing identity.

Tier 3

Customer-held evidence

Uses a signed Ledger checkpoint the customer keeps off-host, customer-owned logs, or customer key custody where stronger resistance to operator-side rewriting is required.

Boundaries

Base packets are reviewer-verifiable records, not an out-of-the-box guarantee against operator-side rewriting.

Not a legal-compliance guarantee.

Not proof that every private memory, transient model output, or internal trace is public or permanently signed.

Tamper evidence is conditional: operator resistance depends on deployment configuration, key custody, checkpoint retention outside the operator boundary, infrastructure controls, and customer procedures.

Advanced assurance profiles

Deeper evidence options are available where the use case requires them.

For long-retention or disputed-evidence workflows, qualified deployments can add hash-chained checkpoints, stronger signing profiles including post-quantum signature options where configured, customer key custody, or signed checkpoints retained outside the operator boundary. Those options are an advanced assurance layer, not the starting point for a governed handoff.

Open advanced assurance brief

Start with one governed handoff.

Bring one agent workflow. FieldHash will show which records or actions would have proceeded, what would have stopped or gone to review, and what evidence your reviewers can inspect.

Request a six-week shadow evaluation