- Purpose
- Scope a pilot that ends. Explicit hypothesis, acceptance gates, and exit conditions.
- Intended user
- Program sponsors, procurement teams, and technical evaluators.
- Version
- 2026.07
- Reviewed
- 2026-07-12
- Owner
- AuraOne Open maintainers
- Next review
- 2027-01-12
- Source commit
- f14253719a9c3bfe2b282b816bab24929529fb3e
- Update policy
- Reviewed at least every 180 days. A material change to the product, the workflow, or a legal or procurement boundary also triggers a review.
Planning and legal boundary: Planning aid only. Nothing here is professional advice. It does not replace review by your own legal, security, and procurement teams. Qualified reviewers must adapt and approve any production use.
Pilot question
State what the pilot is intended to prove, what it cannot prove, and who will use the result.
Acceptance gates
Set the quality, throughput, and evidence gates before any work starts.
Exit and handoff
Say what comes back, what gets deleted, and what happens on a no-go.
Related resources
Continue with the related planning documents rather than treating one template as a complete procurement or approval process.