One Execution Boundary.
10–14 Days.
We select one high-impact action, define its boundary, test ALLOW / HOLD / DENY scenarios, and review the resulting proof records.
One boundary. One partner. One pilot. One proof path.
What we test
Whether ExecutionProof can evaluate one high-impact action before execution and return ALLOW, HOLD, or DENY with a signed Execution Verification Record.
What the partner provides
Your team defines the boundary. We configure the verification.
- One execution boundary to test
- Authority rules — who can request the action
- Policy rules — what limits and thresholds apply
- Required evidence — what proof must be present
- State requirements — what must be true at execution time
- Constraints — what forces HOLD or DENY
- Sample actions — test scenarios for ALLOW / HOLD / DENY
- Desired outcomes — expected decision for each scenario
What Remnant Fieldworks provides
We build the verification config and run the tests.
- Structured boundary intake via Profile Builder
- Execution Boundary Profile (JSON/YAML)
- Verification-ready configuration
- ALLOW / HOLD / DENY simulation tests
- EVR / ProofRecord output for each scenario
- Decision trace and reason codes
- Pilot report with findings and recommendations
- Demo API pathway for v2.1 integration
What gets produced
Execution Boundary Profile (JSON/YAML)
Machine-readable boundary definition
Readiness score and validation warnings
Completeness assessment of the boundary
ALLOW / HOLD / DENY test results
Decision outcomes for each scenario
EVR / ProofRecord samples
Signed verification records with proof hashes
Technical Review Pack
Full summary for engineering review
Pilot Handoff Summary
Scoping document for next steps
Backend compatibility map
How the profile maps to v2.1 endpoints
Pilot report
Findings, recommendations, integration path
What success looks like
The partner's team can define one execution boundary using the Profile Builder
The boundary produces correct ALLOW / HOLD / DENY decisions for test scenarios
Each decision generates a verifiable, tamper-evident EVR / ProofRecord
The team understands what ExecutionProof verifies and what they control
A clear integration path to ExecutionProof v2.1 is documented
The partner can decide whether to proceed to a controlled production pilot
The pilot proves whether one real boundary can be verified before execution with a signed proof record.
First Pilot Lanes
Three focused lanes for external validation. One boundary. One partner. One proof path.
Enterprise AI Workflow
AI agent tool call gate
Verify AI agent actions before execution. Gate tool calls, model access, and autonomous decisions with authority and evidence checks.
• Tool allowlisting
• Model lineage verification
• Risk-threshold gating
• Human review triggers
Crypto Execution Boundary
Crypto withdrawal / multisig gate
Best market wedge — irreversible execution makes pre-verification obvious. Gate withdrawals, multisig spends, and chain operations.
• Destination allowlisting
• Multi-signature approval
• Amount thresholds
• Safe mode / chain health checks
Payment / Approval Workflow
Payment approval gate
Most understandable enterprise use case. Gate payment execution with invoice verification, dual approval, and vendor validation.
• Invoice / approval evidence
• Dual approval thresholds
• Vendor verification
• Amount-based escalation
What is out of scope
Pilot timeline
Boundary selection and intake
Select one high-impact action, define authority and policy requirements
Profile configuration
Build the Execution Boundary Profile with evidence, state, and constraint rules
Scenario testing
Test ALLOW / HOLD / DENY scenarios against the defined boundary
EVR review
Review proof records, decision traces, and reason codes
Report and next steps
Deliver pilot report with findings, integration map, and production path
The discipline is simple:
One boundary. One partner. One pilot. One proof path.
ExecutionProof does not provide legal, compliance, financial, medical, custody, cybersecurity, or investment advice. All pilot boundaries are customer-defined and intended for technical validation only.