RSL DECLARATIONS · SIGNED EVIDENCE · HTTP X402
Prove the evidence gap in 25 events, not 30 days
A 15–30 minute integration. Three events prove the path; 25 eligible events or 6 hours is the normal decision gate, with a hard cap of 50 events or 24 hours.
1. Connect beside the existing workflow
Use the provider-neutral Evidence Bridge and one architecture adapter. Keep the existing request path unchanged. The sprint begins in Observe mode only.
Use explicit intended purpose for every event: ai-input, ai-index, ai-train or search. Do not infer purpose from a tool name.
2. Stop at the first commercial gate
Do not wait for 100 events. After three eligible events the integration path is proven. A material rights/drift signal can produce GO immediately. Otherwise decide at 25 eligible events or 6 hours; extend only when inconclusive and never beyond 50 events or 24 hours.
At the current 0.02 USDC fresh single-resource Preflight price, 25 paid fresh reports correspond to 0.50 USDC and 50 to 1.00 USDC. The live prepared 402 is always authoritative, and Preflight events with no paid offer are not equivalent to paid reports.
3. Generate the local report
Keep shadow events in your own environment as NDJSON. Start the local watcher once; it monitors the file, prints progress, and stops automatically on GO, REVIEW or STOP_OR_FIX. Raw URLs and evidence do not need to leave the partner environment.
node examples/proof-sprint.mjs events.ndjson4. Convert immediately when value is visible
The local report returns GO, REVIEW, EXTEND or STOP_OR_FIX. GO means a material rights/drift signal appeared. REVIEW means verified evidence exists but the buyer should compare it with its existing audit trail. EXTEND may run only to 50 events / 24 hours. STOP_OR_FIX means the yield is too weak or eligibility/integration needs correction.
If none of those happen, stop. The sprint is designed to produce a fast yes/no decision, not to manufacture a long pilot.