- Purpose
- Define a bounded pilot with explicit hypotheses, data, acceptance gates, review cadence, costs, and exit conditions.
- Intended user
- Program sponsors, procurement teams, technical evaluators, and prospective delivery partners.
- Version
- 2026.07
- Reviewed
- 2026-07-12
- Owner
- AuraOne Open maintainers
- Next review
- 2027-01-12
- Source commit
- f14253719a9c3bfe2b282b816bab24929529fb3e
- Update policy
- Review at least every 180 days and after a material product, workflow, legal, security, or procurement-boundary change.
Planning and legal boundary: Planning aid only. This resource is not legal, security, medical, compliance, contractual, service-level, employment, investment, or procurement advice. 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
Define measurable quality, throughput, evidence, privacy, security, and operating gates before work begins.
Exit and handoff
Specify artifact return, deletion, knowledge transfer, production-readiness review, and no-go handling.
Related resources
Continue with the adjacent planning record rather than treating one template as a complete procurement or approval process.