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 platform developed by Remnant Fieldworks™. It evaluates whether an action should be ALLOW, HOLD, or DENY before execution.
Remnant Fieldworks™
The company that develops the ExecutionProof™ platform and related verification infrastructure. Legal entity: Remnant Fieldworks Inc.
Proof Before Power™
The governing doctrine behind ExecutionProof™: consequential actions must be verified before they are allowed to execute.
ALLOW
Verification outcome indicating all requirements are met and the action may proceed. A tamper-evident 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 tamper-evident record generated by ExecutionProof containing the verification decision, evidence references, state snapshot, and proof metadata.
ProofRecord™
The named output artifact of the verification process (internally an EVR), containing decision trace, reason codes, and tamper-evident integrity references for the verification (deterministic fingerprints in demo; designed for cryptographic signing in production).
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.
RF-100
Remnant Fieldworks' emerging field standard for verification-first execution control. The draft is archived and citable on Zenodo (DOI 10.5281/zenodo.21366342) with open review on GitHub (github.com/derekhone/rf-100). RF-100 is not a certification — references to it on this site distinguish pilot-readiness scores from formal RF-100 assessment.
Verification Before Execution™
The framework / method layer behind ExecutionProof™: no high-impact action should execute without first being verified against the defined execution boundary profile.