Prove the evidence gap in 100 events, not 30 days

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

Collect 100 eligible events. If volume is low, stop after 24 hours. There is no reason to wait 14–30 days before deciding whether the evidence is useful.

At the current 0.02 USDC fresh single-resource Preflight price, 100 paid fresh reports correspond to 2.00 USDC and 500 to 10.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. The report generator counts resolved evidence, evidence gaps, statement distribution, unique resources and declaration changes without sending the log back to AcqPath.

node examples/shadow-report.mjs events.ndjson

4. Convert immediately when value is visible

Continue paid usage if the first 100 events produce useful verified source evidence, surface a prohibited/license-required/unknown case, reveal a missing evidence field in the existing audit trail, or detect a meaningful declaration change.

If none of those happen, stop. The sprint is designed to produce a fast yes/no decision, not to manufacture a long pilot.