Remnant Fieldworks Inc.
Pre-Execution
Governance Infrastructure
“If it cannot be verified, it cannot execute.”
Remnant Fieldworks builds ExecutionProof — the verification layer that gates vendor and treasury payments before they execute.
We start with one boundary: stopping AI agents from moving money without proof.
Proof Before Power™ · Verification Before Execution™
Where would you like to start?
Three paths, one boundary.
The Boundary, Concretely
A $500K Wire, Held Before It Moves
This is the one use case we are validating today. An AI agent submits a vendor payment — follow it through the ExecutionProof boundary, from request to signed proof.
HOLD — Awaiting Independent Approval
Self-approval blocked. 2 independent approvers required.
ProofRecord will be written on final disposition · Boundary re-verification at release
A $500,000 wire is initiated
An AI agent — or an automated treasury workflow — submits a $500,000 outbound vendor payment. In most systems, this is the moment money moves.
ExecutionProof places it on HOLD
The action does not execute. It is intercepted at the boundary and held until authority and conditions are independently verified.
The initiator cannot approve their own wire
The person or system that requested the transfer is structurally barred from clearing it. Separation of duties is enforced, not requested.
Two independent approvers verify
Two distinct, authorized approvers must each confirm authority and conditions. Neither approval alone releases the transfer.
Conditions are re-checked at release
Before release, the boundary re-verifies that nothing material changed — amount, destination, authority, and constraints — since approval.
Only now does it ALLOW
With authority proven, self-approval blocked, two independent approvals captured, and conditions re-verified — the transfer is permitted to execute.
A signed ProofRecord is written
Every decision — the HOLD, the blocked self-approval, both approvals, the re-verification, the ALLOW — is captured in a tamper-evident, signed ProofRecord.
The same boundary logic — ALLOW / HOLD / DENY with independent verification and a signed record — generalizes far beyond wires. But we are proving it on this one boundary first.
Start with One BoundaryThe Flagship Platform
ExecutionProof™
A general-purpose pre-execution control layer. Every high-impact action passes through one gate before it is allowed to act.
Verification Gate
ExecutionProof™ receives a proposed action, verifies authority, evidence, policy, state, and risk, returns ALLOW / HOLD / DENY, and generates a signed, tamper-evident ProofRecord™ — a verifiable receipt of the execution decision — before the action proceeds.
The flagship verification engine is operational today — a live /v2/verify endpoint returning real ALLOW / HOLD / DENY decisions with HMAC-signed ProofRecords™ and working HOLD resolution. Live pilot integrations are open now.
ExecutionProof™ is a Remnant Fieldworks™ platform built on the Proof Before Power™ doctrine and the Verification Before Execution™ framework. Each decision produces a ProofRecord™ for auditability, reconstruction, and accountability.
Explore ExecutionProof.ioThe Core Shift
Why Verification Before Execution™?
Most systems act first and check later. We move the checkpoint to the moment that actually matters — before the action fires.
Without ExecutionProof
Executes first
The action fires before anyone confirms it should.
Audits later
Review happens after the fact — if at all.
Discovers failure afterward
Damage is found once it is already done.
With ExecutionProof™
Verifies first
Authority, policy, evidence, state, and risk are checked up front.
Executes second
Only verified actions are allowed to proceed.
Generates proof automatically
Every decision leaves a signed, tamper-evident record.
The Story in Five Words
Doctrine → Framework → Standard → Platform → Proof
Doctrine
The governing belief
Framework
How verification works
Standard
RF-100 conformance
Platform
ExecutionProof
Proof
The signed record
Request a Pilot
The core verification API and Boundary Console are live and pilot-ready. We are recruiting a small group of design partners to govern one high-impact action end to end: intercept, verify, honor the decision, and issue a signed ProofRecord.
- Start with one workflow and one execution boundary.
- Live ALLOW / HOLD / DENY decisions with M-of-N HOLD resolution.
- Direct access to the founder and architecture team.
Built for teams deploying AI agents, treasury workflows, infrastructure commands, healthcare access, or other high-impact systems where execution must be verified before action.
How to Start With One Boundary
One Boundary, Proven Before You Scale.
There is one path in: define a single execution boundary, then prove it in a supervised pilot. A free open-source reference tool lets you explore the ALLOW / HOLD / DENY logic first. Hosted plans, RF-100 assessments, and certification pathways come later as the standard and backend mature.
The Sprint and Pilot are not additive. Because 100% of the Sprint fee is credited toward the Supervised Pilot, your total engagement cost is the final Pilot price — a typical complete Sprint-to-Pilot engagement is approximately $25,000 total.
VaultProof Agent Guard
Open-source experimental reference tool for AI-agent wallet governance.
- ALLOW / HOLD / DENY logic
- Local policy checks
- Sample profiles
- Spend caps
- Allowlists
- Drain-vector blocking
- Telegram HOLD approval path
- Testnet / disposable-wallet use only
Experimental open-source reference implementation. Not audited. Not for production funds.
Request AccessRemote Execution Boundary Validation Sprint
Define one real execution boundary before a pilot.
- One remote kickoff
- One workflow / boundary review
- One governed-action definition
- Authority / evidence / constraints / state mapping
- ALLOW / HOLD / DENY recommendation
- Execution Boundary Profile draft
- RF-100 alignment memo
- Pilot recommendation
- 100% of the Sprint fee credited toward a subsequent Supervised Pilot
Timeline: approximately 10 business days
InquireSupervised Pilot
Test ExecutionProof against one real workflow.
- One defined execution boundary
- Remote setup
- ALLOW / HOLD / DENY test cases
- ProofRecord / VDR output
- HOLD and DENY no-execution testing
- Replay / expiry / parameter-change testing where applicable
- Pilot findings report
- Production-hardening roadmap
- You pay only the remaining balance after the Sprint credit is applied
Weeks 1–2
Boundary setup, remote integration, and policy configuration
Weeks 3–4
ALLOW / HOLD / DENY test execution and ProofRecord capture
Weeks 5–6
Findings report and production-hardening roadmap
4–6 week engagement
InquireDesign-Partner Pricing
Design-partner pricing (Supervised Pilot from $15,000) is available only in exchange for written case-study / testimonial rights, a recognizable reference, or a defined expansion path.
Coming Soon · Waitlist Only
These paths open as the platform, hosted product, crosswalk, and certification pathway mature. Contact us to join the waitlist.
For Diligence Reviewers
The Full Evidence Record
Everything a board member, technical advisor, or compliance reviewer needs is on a dedicated page — doctrine, IP portfolio, standards, research corpus, and open-source ecosystem.
The ExecutionProof™ Series
A governance library of 9 published books and 75+ articles documenting the doctrine, framework, standard, and platform — the written backbone behind the company.
9
Books Published
75+
Articles
#1
Amazon Kindle · Free
The Company
Remnant Fieldworks™
A patent-pending governance infrastructure company building the verification layer between intention and execution.
Derek Hone
Founder & Named Inventor
Sole named inventor on all 56 U.S. patent filings (USPTO Customer No. 236398), filed pro se. Author of 9 published books and 75+ articles. Creator of the Proof Before Power™ doctrine, the Verification Before Execution™ framework, and the RF-100 governance standard.
Remnant Fieldworks began with a single thesis: high-consequence systems should not be allowed to execute merely because an agent, user, or workflow requested action. Every system in the portfolio — from AI governance to data-center operations to financial execution — enforces that thesis at the execution boundary.
Derek Hone
Founder
Adith Kadam Ramesh
Systems Engineer
56 Filed / Pending
Patent Applications Filed
9 Books · 75+ Articles
Published Works
RF-100
Governance Standard