Connect what authorizes the work to what the agent does.
FieldHash is the authority and evidence layer for enterprise AI agents. At the decision points you connect, it checks governing records, proposed effects, and applicable reviews outside the model. When a connected source changes, it returns a new decision for uses that recorded that dependency and leaves unrelated decisions unchanged.
Keep your agent runtime and source systems. Start in shadow mode: record what FieldHash would allow, withhold, or send to review. Production enforcement remains off.
First commercial application
Follow an agent deploy from approval to reuse.
A platform team approves a deploy against a change ticket. The agent retries, edits a manifest, or changes its target. FieldHash checks whether the supplied approval still covers the proposed action. Deploys make the broader authority layer concrete.
- Governed Memory
- Checks which connected records may shape an answer. For a deploy workflow, any context governance is scoped separately from the demonstrated action hook.
- Governed Actions
- Checks the supported deploy against the approved inputs and current change conditions at the connected hook.
- Governed Precedent
- Carries an eligible review forward while its conditions hold. A changed input or cancelled ticket returns affected work to a person.
- FieldHash Ledger
- Records the governing authority, decision and reason. A decision record alone does not prove that a deploy executed.
Change-bound approvals are a preview, off by default and not yet released. The recording uses the real agent runtime and FieldHash hook with stand-ins for the cluster command and change system. Before an evaluation starts: complete the deploy release, connect the agreed change source and validate the covered paths on the customer's host. Production enforcement stays off.
The evaluation asks whether this means more authorized work with less repeated review, waiting and evidence preparation. Customer savings remain unmeasured. The sample below shows the same authority lifecycle in a broader policy workflow.
SAMPLE / Illustrative approval lifecycle
See what changes when an approval stops applying.
Follow one vendor exception from approval to reuse. Then the policy owner publishes a new revision. Compare the request that reused the earlier review with work that never relied on it.
Illustration with invented records and scenario days. No live backend is connected. Production enforcement is off.
05 / Affected use needs review, day 10. The same matching request now needs a new decision. Vendor exception: Would send to review. Same vendor policy, no reused review: Current, would allow. Office-supplies policy answer: Current, would allow. The policy is still in force. It just isn’t the version the approval was reviewed against.
Stage 5 of 5
Scenario day
The policy is still in force. It just isn’t the version the approval was reviewed against.
05 / Affected use needs review · Day 10
The same matching request now needs a new decision.
- Governing source
- Vendor policy, revision 2, with the earlier review retained as history.
- Decision
- Would send to review
- Handoff
- The connected context check would withhold reuse of the exception and route this request to an authorized reviewer.
Same vendor policy, no reused review
Current · would allowIt never relied on the earlier review, so it keeps its allow under revision 2.
Office-supplies policy answer
Current · would allowThe permitted context would still pass its connected check. The vendor policy revision does not change this decision.
Drawing, lane by lane
Drawing of three lanes across scenario days 1, 2, 8, 9 and 10. The first two lanes share the vendor policy; the third has its own purchasing policy.
Vendor exception. Relies on the day 1 review. Governing source: Vendor policy, Revision 2, in force, Published day 9. Wire: Review bound to revision 1, broken.
- Day 1: Reviewed exception, Retained as history.
- Day 2: Would allow.
- Day 8: Would allow reuse.
- Day 9: Reuse suspended.
- Day 10: Would send to review.
Same vendor policy, no reused review. Relies on the policy alone. Governing source: Vendor policy, Revision 2, in force, Published day 9. Wire: Checked against revision 2 (current).
- Day 1: No request.
- Day 2: Would allow.
- Day 8: Would allow.
- Day 9: Rechecked under revision 2.
- Day 10: Would allow.
Unrelated workflow. Office-supplies policy answer. Governing source: Purchasing policy, Current, Unchanged.
- Day 1: Purchasing approval, Current.
- Day 2: Would allow.
- Day 8: Would allow.
- Day 9: Not affected.
- Day 10: Would allow.
An allow is an authority decision, not an execution receipt. This illustration generates no answer and records no completed action.
How this illustration works
An illustrative, locally scripted walkthrough with invented records and scenario days. Buttons change only this display: no live backend, generated answer, or customer workflow is connected. These stages are not an observed experiment, a customer result, or a combined API response. Production enforcement is off.
The view opens on day 10 with the whole sequence drawn. Nothing advances automatically: choose a day, or replay from day 1. Replaying returns to the beginning of the illustration and changes no authority.
Customer systems and authorized reviewers supply authority. This example assumes the update reaches the configured connection, dependencies are recorded, and the next use passes through a connected check. FieldHash does not discover changes or routes outside those connections; they require integration or review.
Read the complete sequence
01 / Bounded approval
An authorized reviewer grants a bounded exception.
On day 1, a procurement reviewer approves a vendor exception under Vendor policy revision 1: use this vendor’s approved support records for internal service summaries through day 30. Matching requests may reuse the review while the conditions it was reviewed against still hold.
Decision: Approval recorded. The review names the vendor, permitted records, purpose, expiry, governing policy revision, and permission to reuse it.
Handoff: No summary is requested at this stage. The bounded review is available for a matching request.
02 / First use
The first request fits the approval.
On day 2, an agent requests context for an internal summary of the vendor’s support history. The records, purpose, and policy revision match the approved conditions.
Decision: Would allow. The requested context fits the reviewed scope and time window.
Handoff: The approved records would pass the connected context check for this summary.
03 / Valid reuse
A matching request proceeds on the earlier review.
On day 8, another internal summary asks for the same approved records, for the same vendor and purpose. Without a reusable review, this request would need its own exception review.
Decision: Would allow reuse. Reuse was explicitly permitted, and the request matches the review: same policy revision, records, purpose, and time window.
Handoff: The matching context request would proceed on the earlier review instead of waiting for a new one.
04 / Authority change
The policy owner publishes a new revision.
On day 9, the policy owner publishes Vendor policy revision 2. It is current and in force, and it narrows which support records the exception may use. Nothing expired and nothing was revoked. The connected update reaches FieldHash.
Decision: Reuse suspended. The review was bound to revision 1. Revision 2 changes a condition the review relied on.
Handoff: The earlier review would not authorize another matching request. Earlier decisions remain recorded.
05 / Affected use needs review
The same matching request now needs a new decision.
On day 10, the same matching request arrives. It still matches the earlier cases, but the review it would reuse was checked against revision 1. Vendor requests that fit revision 2 without that review keep their allow.
Decision: Would send to review. The policy is still in force. It just isn’t the version the approval was reviewed against.
Handoff: The connected context check would withhold reuse of the exception and route this request to an authorized reviewer.
Unaffected work, the other two lanes
- Same vendor policy, no reused review
- A vendor request that fits the current policy revision on its own terms.
- After revision 2: Current · would allow. It never relied on the earlier review, so it keeps its allow under revision 2.
- Office-supplies policy answer
- A separate purchasing policy and approval. Both remain current throughout the scenario.
- After revision 2: Current · would allow. The permitted context would still pass its connected check. The vendor policy revision does not change this decision.
What runs, and what your team sees.
Connect selected authority sources and the context, action, or review decisions that depend on them. Your systems remain canonical. FieldHash evaluates the supplied authority and records the result.
- Authenticated gate
- Checks supplied records, proposed actions, or precedent reuse through their documented interfaces. In shadow, the host records the decision; a separately accepted inline integration makes it affect context or dispatch.
- Private operator console
- Shows source health, governing state, decisions, and active precedents. Operators can inspect which source and review a decision depends on.
- Durable review queue
- Keeps uncertain, conflicting, or changed authority visible to authorized reviewers. Their recorded judgment can be reused only within the approved conditions.
- Signed Ledger and recovery tooling
- Retains decision evidence for inspection and configured integrity checks. Backup and restore procedures support the deployment's agreed recovery requirements.
These are the single-tenant reference deployment components. The SOW identifies which are included in your proposed deployment, their access controls, and required recovery checks. A signed record supports integrity verification; it does not establish that the source or reviewer was correct.
Observe first. Enforce after acceptance.
During the shadow evaluation
Record what would be allowed, withheld, or reviewed alongside the existing workflow. Reviewers investigate differences and measure control quality, review burden, latency, and operating effort. Shadow decisions do not block production work.
When enforcement is accepted
Your team approves specific connected points, source-freshness rules, and failure behavior. The host then applies gate decisions before admitting context or dispatching an action. Test denied-action recovery and coverage of alternate paths before enabling it.
Current pilot scope includes configured context, action, and reviewed-decision paths. Cumulative and cross-agent budget enforcement are research-harness results; pilot coverage for them is agreed in the SOW. The multi-agent shared-budget runtime remains a research candidate and requires separate scoping. Coverage depends on trusted inputs, connected updates, and mediated paths.
Review the six-week scope and acceptance criteriaInspect an illustrative shadow packet
This illustrative shadow packet shows what would proceed, stop, or require review. It uses synthetic data and records proposed decisions, with production enforcement off.
Candidates in. Governed packet out.
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
Shadow decisions identify which context and actions would proceed. Items that would be withheld or reviewed retain 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. In shadow, FieldHash records that it would admit the current policy and withhold the other two, keeping all three in the evidence record.
Access control determines who can open these records. FieldHash records which would be permitted to influence this answer or proceed under the supplied authority.
Memory candidates
Reviewer-readable trace
POLICY-2026-041
Policy system
retrieval score 0.91
Would allow into model context
current_approved_record
POLICY-2025-118
Policy archive
retrieval score 0.89
Would withhold from model context
superseded_by POLICY-2026-041
EXCEPTION-2026-017
Review queue
retrieval score 0.84
Would retain as evidence only
rejected_exception
Action candidates
Tool-use trace
ACTION-REFUND-STANDARD
Would allow as an action candidate
approved_scope
ACTION-REFUND-OVERRIDE
Would hold for review before execution
approval_required
PACKAGE-REPORTING-2.4.0
Would remove before agent choice
revoked_action
SAMPLE / Initial handoff packet
The initial packet records the decision behind the answer.
This separate refund example shows proposed decisions and their authority sources at an initial handoff. It is independent of the vendor-exception walkthrough above; its labels are illustrative, not a combined API schema.
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
The packet records the decision outside the model.
This shadow packet records proposed decisions without enforcing them. In an accepted enforcement integration, the host applies those decisions before context reaches the model or an action executes.
FieldHash uses authority established by your systems and reviewers; free text alone does not grant it. 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 answer. 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 prior reviewed decision no longer holds, the gate decision withholds a clean allow and records the review route. In shadow, that decision is observed; it does not block production work. A reviewed outcome may guide later cases only while its authorizing conditions remain valid.
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, or expiry stops reuse and returns the case to review.
A review may update Authority State (the connected view of which records and reviews currently govern), 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 shadow evaluation to test the decision 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 a six-week shadow evaluation