Proof relay binding
Evidence Analysis travels through the proof spine.
Run a structured compliance packet through Evidence Analysis, then bind the result to Receipt Passport, Agent Run Ledger, Proof Relay, and the retry or handoff path.
Model-backed proof binding
Path
The analysis layer supplies the analysis. Wever Labs signs, ledgers, relays, and routes the result.
Packet
Model-backed
Receipt
Ledger
Relay
Retry
One-click live relay demo
One packet. One analysis. One verified receipt. One relay path.
The demo POSTs a vendor security questionnaire packet, receives Model-backed analysis, creates a ledger entry, and returns a proof relay object with delivery state and next endpoint.
Waiting for relay run.
Run the sample to see the relay summary.
View sample payload
{
"rail_key": "compliance_evidenceops",
"packet_type": "vendor_security_questionnaire",
"requested_outcome": "readiness_review",
"organization_name": "sample_organization",
"control_framework": "vendor_security",
"required_evidence": ["soc2_report_or_bridge_letter", "insurance_certificate", "security_policy", "subprocessor_list", "data_handling_summary"],
"available_evidence": ["soc2_report_or_bridge_letter", "insurance_certificate", "security_policy"]
}Returned objects
The analysis is no longer isolated.
Evidence Analysis feeds a visible relay bundle. Agents can store the ledger entry, verify the receipt binding, and route incomplete packets to Retry Manager or complete packets to Proof Relay.
Analysis
Evidence Analysis
Evidence summary, gaps, risk notes, readiness rationale, and handoff summary.
Receipt
Receipt Passport
Receipt hash, signature, verification state, and passport identity bind the model-backed run.
Ledger
Agent Run Ledger
Ledger entry records analysis id, receipt id, proof hash, model state, and cost state.
Relay
Proof Relay
Relay hash, receipt binding hash, delivery state, and next endpoint prepare downstream handoff.
Retry
Agent Retry Manager
Incomplete packets route to retry with missing evidence attached.
Boundary
Controlled routing
The relay path accepts structured compliance context and returns proof objects for retry or handoff.
API route
POST directly to the relay binding.
Agents can provide an existing analysis_result or submit packet context and let the endpoint run analysis before binding the proof relay.
POST /api/analysis-proof-relay
{
"packet_type": "vendor_security_questionnaire",
"requested_outcome": "readiness_review",
"available_evidence": ["soc2_report_or_bridge_letter", "insurance_certificate", "security_policy"],
"required_evidence": ["soc2_report_or_bridge_letter", "insurance_certificate", "security_policy", "subprocessor_list", "data_handling_summary"]
}