[Evidence Sprint follow-up] Define live-pilot entry criteria for external claims

[ootakazuhiko]

Summary

Define live-pilot entry criteria before converting fixture-backed Evidence Sprint pilot materials into external or live-behavior claims.

Background

Issues #3572 and #3573 produced fixture-backed/report-only Web API and event-driven pilot evidence. The release assets in #3575 intentionally avoid live API/event behavior, productivity, safety, quality, adoption-impact, and vendor-comparison claims. Before any public external pilot claim, the project should define what evidence, consent, baselines, and operational boundaries are required.

Proposed scope

• Define minimum entry criteria for live/external pilots, including repository consent, data handling, artifact retention, and claim boundaries.
• Specify which Evidence Sprint metrics must be collected before a live-pilot claim can be made.
• Separate pilot readiness criteria from enforcement or benchmark claims.
• Link the criteria from the measurement protocol or pilot evidence docs as appropriate.

Acceptance criteria

• Live-pilot entry criteria are documented with explicit supported/unsupported claim boundaries.
• Required evidence artifacts and measurement fields are listed.
• External repository, data-retention, and consent assumptions are explicit.
• Fixture-backed pilots remain clearly marked report-only until the criteria are satisfied.

Evidence references

• Parent Evidence Sprint Epic: [Epic] Evidence Sprint: dogfood, measure, and publish ae-framework effectiveness #3567
• Web API pilot: [EVIDENCE-011] Run Web API pilot using domain preset #3572 / PR [EVIDENCE-011] Run fixture-backed Web API pilot #3580
• Event-driven/conformance pilot: [EVIDENCE-012] Run event-driven/conformance pilot using domain preset #3573 / PR [EVIDENCE-012] Run fixture-backed event-driven pilot #3581
• Release assets follow-up list: [EVIDENCE-030] Prepare release note, article outline, and public announcement assets #3575 / PR [EVIDENCE-030] Prepare Evidence Sprint release assets #3583

[ootakazuhiko]

Completed via PR #3589.

Evidence:

• Added docs/product/LIVE-PILOT-ENTRY-CRITERIA.md as the SSOT for live/external pilot entry criteria, including entry states, consent/data-handling/retention assumptions, required artifacts, measurement fields, and supported/unsupported claim boundaries.
• Linked the criteria from README/docs navigation, the Evidence Sprint measurement protocol, Web API/event-driven pilot reports, external pilot onboarding/runbook/report, release assets, and the launch kit.
• Preserved fixture-backed/report-only boundaries for [EVIDENCE-011] Run Web API pilot using domain preset #3572/[EVIDENCE-012] Run event-driven/conformance pilot using domain preset #3573 and ACP-097 dry-run status until the criteria reach claim_ready through a future reviewed PR.
• Addressed all Copilot/Codex review feedback on PR docs(product): define live pilot entry criteria #3589; final review completeness was status=ok with 4/4 threads resolved.
• Final PR head f20cfe46581d306c7460a9c32359099162411607 had required checks gate, policy-gate, and verify-lite passing, full check rollup success/skipped only, and mergeStateStatus=CLEAN before merge.

Local verification:

• pnpm -s run check:doc-consistency
• pnpm -s run docs:lint
• node scripts/ci/validate-json.mjs
• pnpm -s run check:schemas
• pnpm -s run types:check
• pnpm -s run verify:lite
• git diff --check && git diff --cached --check