Security and deployment
Know what FieldHash enforces, and what your deployment must own.
The supported pilot profile is single-tenant and shadow-first. Authentication, persistence, recovery, evidence assurance, and the move to inline enforcement are reviewed before the gate can affect production.
Supported lifecycle
Install, verify, recover, and remove through one documented path.
01
Initialize
Create a deployment identity, configuration, and separate operator and workload credentials.
02
Preflight
Check origins, signing identity, persistence, and required configuration before launch.
03
Launch
Start the authenticated control plane, private console, review database, and evidence ledger.
04
Verify
Exercise allow, block, and review routes; then verify queue and ledger chains, signer identity, and readiness state.
05
Recover
Create or restore a checksummed backup only after deployment and signer checks pass.
06
Export or stop
Produce a reviewer-safe evidence bundle or remove the deployment with the documented command path.
FieldHash provides
Authenticated control-plane and operator roles
Deterministic authority checks over supplied state
Versioned MCP enforcement over stdio or stateless HTTP for discovery, influence, lifecycle lineage, and exact calls
Structured Playwright-compatible action checks with exact approval and pre-dispatch page-boundary verification
Reason-coded allow, block, and review routes
Signer-pinned packet verification and durable append in the controlled inline profile
Documented preflight, smoke, verification, backup, export, and shutdown paths
Your deployment owns
Identity provider, SSO, TLS, private ingress, and network policy
MCP host and server authentication, transport authorization, and upstream permissions
Browser authentication, session custody, target allowlists, and computer-use runtime permissions
Retrieval, registry, document, and review-system credentials
Retention, residency, backup, monitoring, and incident-response requirements
Key custody, external anchoring, and customer-owned audit exports where required
Executor idempotency, request deadlines, rate limits, and multi-host topology
Failure behavior
Authority failure and infrastructure failure remain separate.
Authority uncertainty
Missing, stale, conflicting, or unbindable authority stays out or routes to review under the configured policy.
Shadow mode
FieldHash records what it would allow or block without changing production answers or actions.
Controlled inline mode
A clean allow is not returned when required governance, signing, durable append, or ledger verification cannot complete.
Evidence assurance
Assurance is configured, not assumed.
A reviewable packet does not automatically make the operator unable to rewrite history. Signing, external storage, key custody, and anchoring increase assurance only when the deployment actually configures and preserves them.
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
Externally anchored evidence
Uses customer-owned logs, external anchoring, or customer key custody where stronger resistance to operator-side rewriting is required.
Procurement path
Set the operating boundary before enforcement.
Deployment topology, support commitments, service levels, subprocessors, retention, residency, incident contacts, evidence ownership, key custody, and external anchoring are scoped in the applicable SOW. The public site does not claim universal production readiness, high availability, or compliance by default.
The MCP adapter preserves a legacy stdio profile and supports the MCP 2026-07-28 core over modern-only stdio or stateless HTTP. Remote deployments require trusted identity at the gateway; upstream OAuth and server permissions remain upstream. The bounded Tasks profile must be explicitly negotiated, subscriptions must be re-established after disconnect, and MCP Apps support covers the governed host/server path rather than the iframe sandbox or app bridge. Managed MCP hosting remains outside the supported boundary.
The computer-use profile is a structured Playwright-compatible reference. The default path creates a fresh context with downloads disabled and service workers blocked. Reusing an existing CDP context is an explicit, weaker containment profile. The host supplies the intended action packet; FieldHash does not read pixels, control unrelated tabs, or replace browser identity and session controls.