Governed inference demo
Candidates in. Governed packet out.
FieldHash processes candidates at the payload boundary, excluding stale or revoked items and recording reviewer-verifiable evidence for every decision.
This trace shows the split in plain view: what proceeds, what stops, and why. If the governing source does not support the answer, FieldHash records the resolver check and routes the uncertainty away from approval.
1. Candidates in
Retrieval and agent tooling return current records, stale records, rejected proposals, and possible actions from the systems already in use.
2. FieldHash governs
Configured approval, version, rollback, revocation, scope, and precedent records determine what may influence the answer, action, or next case.
3. Packet out
Allowed context and actions proceed. Everything withheld or sent to review stays in the record with a reason and authority source.
4. Review later
The evidence packet gives reviewers a compact record of what was allowed, what was blocked, what needs review, and why.
Illustrative pilot corpus
A support agent asks which refund path is allowed.
Retrieval returns an approved current policy, a superseded amendment, and a rejected proposal. FieldHash checks them before the model sees them, allowing the current policy through and keeping the other two in the evidence record.
Access control determines who can open these records. FieldHash determines which of them may influence this answer and which actions may proceed.
Memory candidates
Reviewer-readable trace
POLICY-2026-041
Policy system
retrieval score 0.91
Allowed into model context
current_approved_record
POLICY-2025-118
Policy archive
retrieval score 0.89
Withheld from model context
superseded_by POLICY-2026-041
EXCEPTION-2026-017
Review queue
retrieval score 0.84
Retained as evidence only
rejected_exception
Action candidates
Tool-use trace
ACTION-REFUND-STANDARD
Allowed as an action candidate
approved_scope
ACTION-REFUND-OVERRIDE
Caveated before execution
approval_required
PACKAGE-REPORTING-2.4.0
Removed before agent choice
revoked_action
Evidence packet viewer
The reviewer sees the decision behind the answer.
The packet is the handoff record: what went forward, what was withheld, which system supplied authority, and how the artifact can be verified later.
packet_type
fieldhash_evidence_packet_v1
workflow_id
support-refund-policy-agent
run_id
fh_demo_2026_06_16_001
mode
shadow
retrieval_route
customer_rag_stack_redacted
model_route
approved_model_route_redacted
allowed_context
POLICY-2026-041
allowed_actions
ACTION-REFUND-STANDARD
blocked_or_caveated
POLICY-2025-118, EXCEPTION-2026-017, ACTION-REFUND-OVERRIDE, PACKAGE-REPORTING-2.4.0
reason_codes
current_approved_record, superseded_by, rejected_exception, approval_required, revoked_action
authority_source
policy approval state + registry revocation state
reviewed_precedent
none in this illustrative packet
evidence_integrity
packet_hash + previous_hash
checkpoint_reference
none in this base illustrative packet
failure_flags
none in this illustrative packet
Output boundary
This is evidence packaging, not a model claim.
FieldHash makes a narrow claim: enforce configured authority before it can influence an answer or action, then return a packet the reviewer can read.
FieldHash does not claim autonomous truth inference from arbitrary prose. If a workflow has no visible authority records, the pilot starts by finding or proposing reviewable signals before enforcement.
When wording differs, the configured resolver must show that the governing source supports the fact being answered. If it cannot, the packet sends the case to review instead of presenting the answer as governed.
Uncertainty returns to review
A missing authority signal never becomes approval by default.
If the current source cannot be identified, the evidence does not support the claim, an action requires approval, or a precedent has drifted beyond its original conditions, FieldHash withholds a clean allow and records the review route. A reviewer can settle the case; bounded precedent may carry that decision forward only while its scope and dependencies still hold.
The Governed Learning Loop
One reviewed case can improve the next without becoming a permanent rule.
01
A handoff contains missing or conflicting authority.
02
FieldHash sends the case to an authorized reviewer.
03
The reviewer establishes what governs.
04
FieldHash records the scope, evidence, expiry, and dependencies.
05
Future handoffs may reuse the result.
06
Drift, revocation, conflict, or expiry stops reuse and returns the case to review.
A review may update Authority State, resolve a source binding, revoke or narrow authority, or, when the workflow's authority policy permits reuse, compile the judgment into Governed Precedent. Not every review becomes precedent.
Follow the complete loopUse the pilot to test the answer and its evidence.
Bring one real workflow. FieldHash will map where authority signals live, run the governed handoff in shadow mode, and return the packet shape reviewers would use before enforcement.
Request pilot review