Standalone architecture preview · No backend connection required · Exports JSON/YAML for ExecutionProof v2.1 pilot testing.
This tool does not execute actions. It helps teams define the conditions that must be verified before execution.
Verify high-risk actions before they execute.
ExecutionProof decides whether an action should be ALLOW, HOLD, or DENY before execution — and generates a verifiable proof record of the decision.
This builder helps your team define the authority, evidence, policy, and constraints that ExecutionProof will verify.
Define One Boundary
Choose one high-impact action to govern before execution.
Export the Profile
Generate JSON/YAML that can be reviewed and tested against ExecutionProof v2.1.
Prepare for Pilot
Use the profile to scope a 10–14 day technical validation.
Sample Execution Verification Record
What ExecutionProof generates after every decision.
Sample only. Not a live verification record.
Why This Matters
Without ExecutionProof
Unauthorized approvals go through unchecked
AI agents execute tool calls without verification
Payment errors reach production systems
Missing evidence is discovered after the fact
Compliance failures surface during audits, not before
Actions cannot be verified or replayed
With ExecutionProof
Every action verified before execution
HOLD triggered before damage occurs
Verifiable, tamper-evident proof of every decision
Replayable audit trail with signed records
Policy violations caught at the gate, not after
Clear ALLOW / HOLD / DENY at the point of action
How This Fits ExecutionProof
The Profile Builder defines the boundary. ExecutionProof v2.1 enforces the boundary.
What the Company Defines
Seven dimensions of an execution boundary profile.
Authority
Who can request this action
Evidence
What proof must be present
Policy
What rules apply
State
What must be true at execution time
Constraints
What forces HOLD or DENY
Decision behavior
ALLOW / HOLD / DENY logic
Proof output
What proof record to generate
What ExecutionProof Later Verifies
Pre-execution verification questions.
Is the actor authorized?
Does policy allow the action?
Is required evidence present and current?
Is system state valid now?
Do constraints trigger HOLD or DENY?
Should the action be ALLOW, HOLD, or DENY?
What proof record should be generated?
Do not start by modeling your whole organization.
Start with one execution boundary.
Responsibility Boundary
ExecutionProof does not decide your business policy. Your team defines the authority model, evidence requirements, policy rules, state conditions, constraints, and proof outputs. ExecutionProof turns those definitions into pre-execution verification and signed proof.
Remnant Fieldworks does not provide legal, compliance, financial, medical, custody, cybersecurity, or investment advice through this tool.