The Governance Gate for
Consequential AI Actions
If it cannot be verified, it cannot execute.
ExecutionProof is an independent pre-execution governance layer for consequential AI actions. Payment authorization is our first deployment boundary; the same architecture governs deployments, access changes, data release, infrastructure commands, and other irreversible actions.
We do not process payments. We sit before the payment rail — or any execution rail — and determine whether the action is currently authorized, evidenced, and within policy.
What Is an Execution Boundary?
An execution boundary is the complete set of conditions that must be true before a high-consequence action is allowed to proceed. It answers seven questions — and blocks execution until every one is satisfied.
What action is being requested?
Who or what is requesting it?
What authority is required?
What evidence must exist?
What constraints apply?
What state must be valid at execution time?
What outcome if proof is missing?
The Boundary Console is not a general policy builder. It is a pre-execution configuration environment for defining, testing, and exporting Execution Boundary Profiles.
Define the Boundary. See the Proof.
You define the rules. ExecutionProof returns the decision and the evidence.
# boundary: AI-Agent Vendor Payment
workflow: ai_agent_vendor_payment
proposed_action: AI agent initiates outbound vendor payment
required_authority:
roles: [payments_operator]
approvals: 1
source: Okta IAM → Finance approval system
required_evidence:
- vendor_bank_verification # updated within 1 hour
- purchase_order_match # updated within 24 hours
- finance_approval_record # current at execution
policy:
max_amount: 250,000 USD
allowlist: [ACME Supplies Inc — verified account]
prohibited: [crypto transfer, sanctioned region]
human_review:
required_when: amount ≥ 75% of ceiling, or risk high{
"schema_version": "ProofRecord™ v0.1",
"proofrecord_id": "PR-9F3C21A80B7E44D1",
"workflow_boundary_name": "Vendor Payment Approval",
"decision": "HOLD",
"reason_for_decision":
"Evidence stale: bank verification — updated 2h ago",
"evidence_freshness_summary": "2 current, 1 stale",
"policy_version": "2026.02",
"final_outcome":
"Blocked pending resolution — not denied, cannot execute yet.",
"integrity": {
"record_hash": "a1b2c3d4e5f60718",
"method": "Demo deterministic fingerprint (v0.1)"
}
}Demo ProofRecords use a lightweight deterministic fingerprint for local testing. Production ProofRecords are designed to use cryptographic signing and tamper-evident storage.
For Developers
The Integration Pattern
ExecutionProof is a verification gate you call inline, before an action executes. Intercept the request, verify it, honor the decision, and store the returned ProofRecord™.
Intercept
Pause the action at the execution boundary before it runs.
POST /v2/verify
Send the request context to the verification API.
Honor the decision
Proceed on ALLOW. Pause on HOLD. Stop on DENY.
Store the ProofRecord™
Persist the record returned with the decision.
POST /v2/verify HTTP/1.1
Host: api.executionproof.io
Authorization: Bearer <api_key>
Content-Type: application/json
{
"workflow": "vendor_payment",
"proposed_action": "initiate_outbound_payment",
"actor": { "id": "user_8213", "roles": ["payments_operator"] },
"context": {
"amount": 50000,
"currency": "USD",
"destination": "ACME Supplies Inc",
"evidence": {
"vendor_bank_verification": "2026-07-07T13:02:00Z",
"purchase_order_match": "2026-07-06T18:40:00Z"
}
}
}HTTP/1.1 200 OK
Content-Type: application/json
{
"decision": "HOLD",
"reason":
"Self-approval blocked; 2-of-2 independent approval required",
"proofrecord": {
"id": "PR-9F3C21A80B7E44D1",
"workflow_boundary_name": "Vendor Payment Approval",
"policy_version": "2026.02",
"evidence_freshness": "2 current, 0 stale",
"signature": {
"alg": "ML-DSA-65",
"key_custody": "AWS KMS HSM",
"value": "b7e4...44d1"
}
}
}Sample request and response shown for illustration; values are generated sample data, not live transactions. Production ExecutionProof signs ProofRecords with hardware-backed ML-DSA-65 (post-quantum) via AWS KMS HSM plus dual HMAC (HMAC-SHA-256 + HMAC-SHA3-512); proof chains are Merkle-rooted and tamper-evident. Formal RF-100 §8.4 conformance remains pending independent external review, and external anchoring remains on the roadmap.
The Execution Architecture
ExecutionProof sits at the execution boundary. It receives the intended action, constructs a Request Contract, evaluates authority and evidence, applies constraints, and releases execution only when the action is admissible. Fail-closed. No cached permissions. Non-bypassable.
Request Contract
Structured representation of the intended action — who, what, when, and under what conditions.
Authority Engine
Verifies identity, role, delegation chain, and approval requirements before any action proceeds.
Evidence Engine
Confirms required evidence exists, is fresh, and meets admissibility thresholds at execution time.
Constraint Engine
Enforces hard limits — rate caps, dollar ceilings, time windows, allowlists, and blocklists.
Control Engine
Orchestrates evaluation. Fail-closed by default. No cached permissions. Every request re-verified.
ProofRecord™
Tamper-evident evidence artifact generated for every ALLOW, HOLD, or DENY decision.
Execution Gateway
The non-bypassable boundary. Actions proceed only when verification is complete and admissible.
From Definition to Verification
Six steps from boundary definition to controlled pilot. The Boundary Console and Pilot Console are live today.
Choose a workflow
Identify one high-consequence action where pre-execution verification would prevent the most damage.
Map the boundary
Define the authority, evidence, policy, constraints, and state conditions that must be true before execution.
Configure rules
Set approval chains, evidence freshness requirements, dollar thresholds, time windows, and review triggers.
Test decisions
Run sample requests and observe ALLOW, HOLD, and DENY outcomes with full ProofRecord™ output.
Export the profile
Download your Execution Boundary Profile as JSON or YAML for review, handoff, or integration planning.
Prepare integration
Align the boundary with your systems for a controlled pilot or ExecutionProof v2.1 deployment.
Where Execution Boundaries Apply
Any system where actions have consequences that cannot be reversed.
AI-Agent Payments
Stop AI agents from moving money without proof — verify the agent, the invoice, the vendor, and the amount before any payment executes.
AI agent submits $50K vendor payment → HOLD → self-approval blocked → independent human approval required
AI Agent Tool Calls
Verify tool calls and autonomous actions before execution.
Agent requests file deletion → Gate evaluates → HOLD
Infrastructure
Verify deployments, configuration changes, and compute provisioning.
Deploy to prod → All checks pass → ALLOW
Healthcare
Verify care authorizations and clinical actions before proceeding.
Medication change → Evidence stale → HOLD for physician review
Identity & Access
Verify privilege escalations and permission changes.
Admin role grant → No MFA attestation → DENY
Data Release
Gate bulk exports, API data access, and sensitive record transfers.
Bulk PII export requested → classification check fails → DENY
Intellectual Property
Patent-Pending Architecture
Remnant Fieldworks has filed a U.S. patent-pending portfolio directed to proof-first, pre-execution governance. The architecture spans five commercial verticals: AI governance, physical infrastructure, financial execution, IP stewardship, and insurance / risk control.
A 56-application patent-pending stack: eight pending U.S. nonprovisional utility applications — one parent and seven continuations-in-part — together with forty-eight priority provisional applications filed in January 2026. The commercially significant subject matter of the provisional applications is consolidated into the nonprovisional stack. The eight nonprovisional filings are listed below.
Policy-Gated Execution
Proof-first authorization and tamper-evident evidence artifacts for AI, automated, and human-authorized systems.
February 4, 2026
AI Compute Infrastructure Governance
Inheritance-bound verification of physical-domain conditions before infrastructure actions execute.
July 4, 2026
AI-Generated Action Governance
Governance and verification controls for actions generated by AI models and autonomous agents.
July 5, 2026
Tamper-Evident Proof of Execution
Contemporaneous, tamper-evident records of execution events for audit and reconstruction.
July 5, 2026
Financial Execution Control
Proof-gated authorization and verification for financial execution events.
July 5, 2026
AI Safety, Consent & Data Governance
AI safety monitoring, consent-based access control, and privacy-preserving data governance for autonomous computing environments.
July 6, 2026
Ownership & Stewardship Control
Ownership-bound execution control, stewardship verification, and field-interlock access management for AI and autonomous computing environments.
July 7, 2026
Risk-Adaptive Governance & Claims
Risk-adaptive governance, coverage-bound execution control, and verifiable claims processing for insurance and risk domains.
July 7, 2026
Patent-pending means applications have been filed and are pending examination. No patent has issued unless expressly stated. Patent-pending status does not imply issued patents, USPTO endorsement, allowed claims, or final claim scope. Public demonstrations are architecture previews and do not represent production systems.
The Remnant Fieldworks Ecosystem
Three sites. One architecture. One doctrine.
The Platform
ExecutionProof.io
The verification layer for consequential AI actions — returning ALLOW / HOLD / DENY before any execution rail is called. Payment authorization is the first production boundary; the architecture is domain-independent.
Visit ExecutionProof.ioThe Company
RemnantFieldworks.com
Parent company. Doctrine. Standards. Patent-pending portfolio. Remnant Fieldworks builds the verification layer between intention and execution.
Visit RemnantFieldworks.comBook a 20-minute Execution Boundary Fit Call
Paid validation sprints available for qualified teams. Twenty minutes to confirm the one boundary worth testing first — and whether a sprint is the right next step for your team.
Prefer email? Reach us at [email protected].
Ready to define your first execution boundary?
Pick one consequential action — a payment, a deployment, an access change. Define the rules. Test the decisions. See the ProofRecord™.
ExecutionProof™ is a Remnant Fieldworks™ platform built on the Proof Before Power™ doctrine and the Verification Before Execution™ framework. ExecutionProof does not decide your business policy — your team defines the rules. ExecutionProof verifies them at the point of action and generates a tamper-evident ProofRecord™.