Documentation
How This Connects to v2.1 Later
This Profile Builder currently exports integration-ready profiles. API connection is intentionally deferred until UX, profile structure, and pilot scope are validated.
Endpoint Mapping
The exported profile maps to ExecutionProof v2.1 endpoints:
authority rules/v2/policies/authority
constraints/v2/policies/constraints
evidence requirements/v2/policies/evidence-verifiers and /v2/evidence-schemas
rail/domain policy/v2/policies/rails
verification request/v2/verify
proof lookup/v2/proof/{proof_id}
proof summary/v2/proof/{proof_id}/summary
proof integrity/v2/proof/{proof_id}/verify-integrity
decision explanation/v2/pilot/explain/{proofId}
pilot dashboard/v2/pilot/dashboard
hold resolution/v2/hold-escalations or /v2/pilot/status/{proofId}
EVR registry/v2/evr/register and /v2/evr/lookup/{evrId}
Future Integration Flow
1Define boundary in Profile Builder
2Export JSON/YAML
3Review internally
4Load into ExecutionProof v2.1 configuration
5Test with sample ALLOW/HOLD/DENY actions
6Review EVR / ProofRecord outputs
7Iterate and refine
8Move to pilot
9Validate in controlled environment
10Move toward production readiness
The Profile Builder defines the boundary. ExecutionProof v2.1 enforces the boundary.