Abstract
FieldHash is an independent authority and evidence layer for enterprise AI. It records the governing sources, approvals, scope, and dependencies supplied by customer systems and authorized reviewers. At connected handoffs, it checks which records may influence an answer, which effects may proceed, and which reviewed decisions may govern a later case, then records the decision in an evidence packet. It works with the customer's existing model, memory store, database, review system, and tool registry.
Governed Memory controls memory influence: approved/current records can shape the model input; stale, rejected, superseded, out-of-scope, or rolled-back records remain reviewable but blocked from steering future answers without review.
Governed Actions applies the same authority pattern to proposed effects. It keeps current authority outside the model and checks it before an instrumented effect proceeds. Cumulative and cross-agent budget enforcement are research-harness results; pilot coverage for them is agreed in the SOW.
Governed Precedent lets review compound outside the model: a reviewed decision may guide later work only while the customer-defined conditions that authorized it remain valid.
The Governed Learning Loop is the controlled process around those surfaces: uncertainty returns to authorized review, approved outcomes update external Authority State, and reviewed judgments may become Governed Precedent when the workflow's authority policy permits reuse. Future use remains linked to the original evidence and stops when its authority changes.
FieldHash does not decide truth by itself. Customer systems of record, review signals, supersession events, and rollback operations define real-world authority for a workflow; FieldHash applies that customer-defined authority at the context, action, and reviewed-decision handoffs the workflow connects.
FieldHash Ledger records the decision surface: evidence packets, packet hashes, checkpoint references, customer-owned exports, and stronger signing or transparency anchoring where configured. Base packets make the governed path reviewable; operator resistance depends on where anchors, logs, and keys are held.
In plain English
Retrieval answers “what looks relevant?” FieldHash asks, “is this record, tool, or reviewed decision allowed to shape the answer or action, and can we prove what happened later?”
Product
Authority and evidence layer at context, action, and reviewed-decision handoffs.
Buyer
AI platform, security, legal, compliance, and model-risk teams.
Failure mode
A relevant record or individually permitted action can still carry the wrong authority into an answer or outcome.
Proof boundary
Separate self-administered studies test influence, action, and reuse controls. They do not establish an integrated customer lifecycle or third-party validation.
Product architecture
FieldHash applies customer-defined authority at context, action, and reviewed-decision handoffs. Existing source systems, agent runtimes, models, and review tools keep their roles. The integration connects the governing records and decisions each selected handoff depends on.
Simple workflows can use simple flags. FieldHash is designed for the workflows where authority spans stores, reviewers, supersession chains, rollback operations, scope boundaries, and evidence requirements.
Authority State maintains the customer-scoped status, scope, source bindings, and precedent dependencies needed between governed handoffs. When a connected source changes, recorded dependencies identify which workflows or reviewed decisions need re-evaluation. Required dependency mismatches suspend precedent reuse and return the case to review.
The documented integration paths use separate context, exact-action, and precedent interfaces. The retrieval example shows one surface. Governed Memory can also govern context cleanup, retaining approved records and recording what was kept or excluded where configured.
| Layer | Technology | Function |
|---|
| Candidate sources | Existing enterprise records, memory systems, tool catalogs, and review systems | Supplies candidates and authority signals without requiring a rip-and-replace of the customer stack. |
| Authority State | Customer-supplied authority and change signals | Carries current organizational authority to governed handoffs and identifies when prior use must be reconsidered. |
| Governed Learning Loop | Authorized review, bounded carry-forward, and evidence lineage | Lets review improve future handoffs without turning every outcome into a permanent hidden rule. |
| Governed Memory | Current, superseded, rejected, and out-of-scope record state | Determines which records may influence the next answer and keeps excluded alternatives reviewable. |
| Governed Actions | Current action authority and exact-action approval | Determines which proposed effects may proceed. Cumulative limits address individually allowed steps that add up past what was authorized. Cumulative and cross-agent budget enforcement are research-harness results; pilot coverage for them is agreed in the SOW. |
| Agent and action adapters | Governed discovery and structured action mediation | Places the authority decision at instrumented model and execution handoffs. |
| Governed Precedent | Reviewed decisions with customer-defined validity conditions | Allows bounded reuse while the authorizing conditions hold and returns changed cases to review. |
| Authority decision | Allow, withhold, caveat, and review routing | Applies configured authority decisions outside the model. |
| FieldHash Ledger | Evidence packets and customer-controlled verification | Records the governed path for later inspection. |
| Model route | Customer-approved hosted, cloud, VPC, or local model | Receives only the context allowed by the governed handoff. |
| Deployment substrate | One single-tenant stack you run in your VPC or on premises | Lets you keep the model and memory store you already use. |
Current implementation boundary
Governed Learning does not mean online model training. FieldHash records authorized changes outside the model. Model output, confidence, or observed success may propose a candidate update, but cannot grant that update authority by itself.
The current Authority State pilot path connects customer-approved authority and change signals to selected governed handoffs. Managed SaaS connectors remain design-partner scoped and customer systems remain canonical.
The supporting connector reliability diagnostic publishes aggregate restart, rejection, replay, and scoped-impact results with a public verification manifest.
FieldHash can mediate supported agent discovery, instructions, resources, prompts, interactive work, deferred work, and action dispatch at an instrumented boundary. Trusted identity, upstream permissions, and runtime isolation remain customer responsibilities; material changes or uncertain authority require a new decision or review.
The current computer-use path is a structured reference integration. The host supplies the proposed action and trusted workflow context; FieldHash checks current authority at the configured boundary and records the decision separately from the observed execution outcome. It does not infer authority from pixels or operate as a managed browser service.
Keep your systems
Customer systems and authorized reviewers establish authority; existing agents and stores remain in place.
Connect each use
Apply current authority before information influences, an effect proceeds, or a reviewed decision carries forward.
Verify the path
Evidence records the governing source, decision, and reason separately from any observed execution outcome.
Governed inference loop
At each connected handoff, the workflow supplies candidates and current authority evidence. FieldHash applies the relevant context, action, or reuse check and records the decision. An approved review may inform a later handoff within its recorded limits; it does not train the model or become permanent permission.
1Retrieve candidate records, memories, tools, or reviewed precedent candidates from approved systems.
2Apply governed-state metadata: current, superseded, rejected, revoked, rolled back, expired, or out of scope.
3Apply the relevant check: source support for context, authority for a proposed effect, or scope and dependencies for reviewed-decision reuse.
4Release allowed context or permit the governed action or reuse at its connected handoff. Withhold uncertain cases or return them to review.
5Re-evaluate affected uses when connected authority changes. Preserve the earlier decision and the reason for its new disposition.
6Record governance reasons, selected inputs, blocked alternatives, packet hashes, and ledger references.
The production context handoff returns an allow decision only after its evidence seal and durable ledger chain verify. Caveated records stay out of model context; uncertain cases can be configured to route to review. This gives the application a decision backed by a retained, verifiable record before it proceeds.
Related work and positioning
Stateful and memory-augmented LLM agents are an active area. Relevant reference points include Letta/MemGPT for agent-managed context, Mem0 for production memory across users and sessions, Zep for temporal knowledge-graph memory, Oracle-style enterprise memory substrates, and retrieval-centric systems such as HippoRAG.
FieldHash governs answer and action paths. Trusted workflows supply candidate memory, tools, reviewed precedents, and authority evidence. FieldHash enforces what may influence the answer or action, keeps blocked alternatives reviewable, and records the decision path. Existing stores remain canonical, and FieldHash does not infer truth from arbitrary prose.
Incorrect upstream authority can still be enforced. The value is that the decision path remains inspectable and correctable: reviewers can see which signal governed, which records were withheld, and where the authority decision must be changed if the source system is wrong.
For technical diligence
Public materials summarize FieldHash at a product and evidence level. The FieldHash governed-context methods report is available as a direct PDF; deeper architecture notes, benchmark methodology, ablation summaries, trace examples, evidence-export examples, and governance controls are available selectively for qualified technical reviewers.