Week 17 · reflection
Week 17 Capstone Plan Log
This log captures the moment your capstone changes from a concept into a controlled plan.
Do not summarize every page. Record the decisions that now make the mission traceable.
Product-to-route trace
Choose the three most important product requirements and show where the mission produces them.
| Product requirement | Route state / action | Evidence artifact | Completion test |
|---|---|---|---|
If a product requirement cannot be traced to an action and artifact, carry it forward as an unresolved design problem.
Evidence status snapshot
Classify five important planning claims.
| Claim | Verified | Assumption | Re-check required | Source / evidence |
|---|---|---|---|---|
The goal is not to make every row “verified.” The goal is to stop uncertainty from hiding.
Review revision record
Document two changes made because of the Week 17 mission-plan review.
Revision 1
- Finding:
- Artifact changed:
- What changed:
- Why the new version is stronger:
Revision 2
- Finding:
- Artifact changed:
- What changed:
- Why the new version is stronger:
One failure path you can now explain
Choose one failure such as rejected imagery, deteriorating weather, unexpected people, route delay, weak positioning evidence, or a changed regulatory/source condition.
Write the sequence:
trigger -> detection evidence -> decision owner -> fallback/abort action -> artifact updatedIf any arrow is missing, that is a Week 18 risk-review target.
Phase-2 reflection
Answer three questions:
- Which part of the mission plan is now most defensible because the evidence chain is clear?
- Which assumption still carries the most risk?
- Which reviewer question would be hardest for your team to answer today?
Week 18 starts with that hardest question.