Backend Compatibility Map
How Profile Builder fields map to ExecutionProof v2.1 endpoints.
Integration Status
This builder currently exports integration-ready profiles. API connection is intentionally deferred until UX, profile structure, and pilot scope are validated.
Profile Field
v2.1 Endpoint
Notes
Authority rules
/v2/policies/authority
Role, approval, signer requirements
Constraints
/v2/policies/constraints
HOLD and DENY trigger definitions
Evidence requirements
/v2/policies/evidence-verifiers and /v2/evidence-schemas
Evidence types, freshness, validation
Rail/domain policy
/v2/policies/rails
Domain-specific rules and limits
Verification request
/v2/verify
Submit an action for verification
Proof lookup
/v2/proof/{proof_id}
Retrieve a proof record
Proof summary
/v2/proof/{proof_id}/summary
Condensed proof overview
Proof integrity
/v2/proof/{proof_id}/verify-integrity
Tamper-evidence check
Decision explanation
/v2/pilot/explain/{proofId}
Human-readable reason trace
Pilot dashboard
/v2/pilot/dashboard
Real-time pilot monitoring
Hold resolution
/v2/hold-escalations or /v2/pilot/status/{proofId}
Manage HOLD escalations
EVR registry
/v2/evr/register and /v2/evr/lookup/{evrId}
Execution Verification Records
Integration Flow
01
Define boundary in Profile Builder
02
Export JSON/YAML
03
Review internally
04
Load into ExecutionProof v2.1 configuration
05
Test with sample ALLOW / HOLD / DENY actions
06
Review EVR / ProofRecord outputs
07
Iterate and refine
08
Move to pilot
09
Validate in controlled environment
10
Move toward production readiness
The Profile Builder defines the boundary. ExecutionProof v2.1 enforces the boundary.