Glossary
Execution Boundary Profile
A structured, customer-defined configuration that specifies the authority, evidence, policy, state, constraints, and proof requirements for pre-execution verification.
ExecutionProof
The core pre-execution verification engine developed by Remnant Fieldworks. It evaluates whether an action should be ALLOW, HOLD, or DENY before execution.
Remnant Fieldworks
The parent company that develops ExecutionProof and related verification infrastructure.
ALLOW
Verification outcome indicating all requirements are met and the action may proceed. A signed EVR/ProofRecord is generated.
HOLD
Verification outcome indicating one or more conditions require review or escalation before the action can proceed.
DENY
Verification outcome indicating one or more hard constraints are violated and the action must not proceed.
EVR (Execution Verification Record)
A signed record generated by ExecutionProof containing the verification decision, evidence hashes, state snapshot, and proof metadata.
ProofRecord
The output artifact of the verification process, containing decision trace, reason codes, and cryptographic proof of the verification.
Authority
The set of rules defining who can request an action, what roles they need, and what approval chain is required.
Evidence
The proof artifacts that must be present before verification, such as request IDs, approval records, risk reviews, and allowlist matches.
Policy
The rules that govern what is allowed, including amount limits, destination restrictions, time windows, and tool allowlists.
State
The system and operational conditions that must be true at the moment of verification, such as safe mode status, account state, and chain health.
Constraints
The HOLD and DENY trigger conditions that force specific verification outcomes when activated.
Proof Output
The configuration defining what fields are included in the generated EVR/ProofRecord, such as decision trace, evidence hashes, and signatures.
Pilot-ready profile
A profile that has sufficient completeness (readiness score >= 90) to be used in a controlled pilot test against ExecutionProof v2.1.
Backend compatibility
The mapping between profile fields and ExecutionProof v2.1 API endpoints, ensuring the exported profile can be consumed by the verification engine.
Verification Before Execution
The core principle that no high-impact action should execute without first being verified against the defined execution boundary profile.