Vision Readiness Summary¶
Template purpose¶
Use this template to summarize the ES-101 vision package.
This artifact does not repeat every detail. It records whether the problem, vision, stakeholders, scope, assumptions, and success criteria are clear enough for ES-102 — Requirements and Constraints to begin.
Project¶
<Project name>
Document control¶
| Field | Value |
|---|---|
| Artifact owner | <owner> |
| Primary reviewers | <reviewers> |
| Status | <draft / in review / accepted / revised> |
| Last updated | <YYYY-MM-DD> |
| Related Engineering Stage | ES-101 — Vision and Problem Definition |
| Project workspace target | docs/project-workspace/vision/vision_readiness_summary.md |
| Next stage | ES-102 — Requirements and Constraints |
ES-101 package summary¶
Briefly summarize the ES-101 vision package.
<One or two paragraphs.>
Artifact status¶
| Artifact | Project Workspace Reference | Status | Notes |
|---|---|---|---|
| Problem Statement | docs/project-workspace/vision/problem_statement.md |
<draft / reviewed / accepted / incomplete> |
<notes> |
| Vision Statement | docs/project-workspace/vision/vision_statement.md |
<draft / reviewed / accepted / incomplete> |
<notes> |
| Stakeholders | docs/project-workspace/vision/stakeholders.md |
<draft / reviewed / accepted / incomplete> |
<notes> |
| Scope | docs/project-workspace/vision/scope.md |
<draft / reviewed / accepted / incomplete> |
<notes> |
| Assumptions | docs/project-workspace/vision/assumptions.md |
<draft / reviewed / accepted / incomplete> |
<notes> |
| Success Metrics | docs/project-workspace/vision/success_metrics.md |
<draft / reviewed / accepted / incomplete> |
<notes> |
Problem¶
Summary:
<Problem summary.>
Readiness concern:
<Any concern that could affect requirements work.>
Vision¶
Summary:
<Vision summary.>
Trustworthiness expectation:
<Trustworthiness expectation.>
Stakeholders¶
Key stakeholder groups:
<stakeholder group>
Missing or unresolved stakeholder concerns:
<stakeholder concern>
Scope¶
Key boundary decisions:
<boundary decision>
Explicitly prohibited behavior:
<prohibited behavior>
Deferred scope:
<deferred item>
Key assumptions¶
Material assumptions:
| Assumption ID | Assumption | Validation Status | Impact on ES-102 |
|---|---|---|---|
<A-###> |
<assumption> |
<open / accepted / validated / retired> |
<impact> |
Success criteria¶
Most important success indicators:
| Indicator | Evidence Source | Later Stage Use |
|---|---|---|
<indicator> |
<source> |
<requirements / testing / release / monitoring / stewardship> |
AI, data, and governance considerations¶
| Area | Summary | Requires Follow-up in ES-102? |
|---|---|---|
| AI | <AI relevance or boundary> |
<yes / no / conditional> |
| Data | <data assumptions, risks, or boundaries> |
<yes / no / conditional> |
| Governance | <review, approval, oversight, policy, or accountability considerations> |
<yes / no / conditional> |
Open questions¶
| ID | Question | Owner | Must Resolve Before |
|---|---|---|---|
| OQ-001 | <question> |
<owner> |
<ES-102 / architecture / implementation / release> |
Readiness decision for ES-102¶
Can requirements and constraints work begin?
<Yes / No / Conditional, with rationale.>
Conditions for proceeding¶
If readiness is conditional, list required actions.
| Condition | Owner | Due |
|---|---|---|
<condition> |
<owner> |
<date or stage> |
Reviewer notes¶
<Optional reviewer comments.>
Readiness checklist¶
- [ ] Problem statement is clear and solution-neutral.
- [ ] Vision responds to the problem and includes trust expectations.
- [ ] Stakeholders include users, affected parties, operators, maintainers, and governance reviewers where relevant.
- [ ] Scope includes in-scope, out-of-scope, deferred, and prohibited items.
- [ ] Material assumptions are visible and assigned.
- [ ] Success criteria include outcome, operational, trustworthiness, and adoption indicators.
- [ ] AI, data, and governance implications are identified where relevant.
- [ ] Requirements work can begin without hiding major uncertainty.