11 lines
661 B
Markdown
11 lines
661 B
Markdown
# Steps 10–12 — Manifest-Bound Implementation and Acceptance
|
||
|
||
1. Implement approved tasks only inside manifest `source_roots`.
|
||
2. Confirm every changed behavior and test maps to a requirement ID.
|
||
3. Review architecture boundaries, validation, authorization, data integrity, safe logging/errors,
|
||
dependency policy, test depth, and golden drift.
|
||
4. Run all matching manifest verification rules.
|
||
5. Run manifest build commands, then test commands, as argv without shell interpolation.
|
||
6. On failure, roll back the approved patch and return to plan/implementation with evidence.
|
||
7. Write implementation acceptance only after every deterministic gate passes.
|