refactor: implement governed Delivery program contracts
This commit is contained in:
1 parent
c306ea4794
commit
65e546c448
18 files changed
+575
-99
No files matched your search
@@ -10,8 +10,8 @@ When a build or CI failure is observed:
|
||||
2. reproduce locally when feasible;
|
||||
3. determine root cause before editing;
|
||||
4. compare the intended fix against approved FR/NFRs, ADRs, architecture documentation, and project conventions;
|
||||
5. implement the smallest safe fix;
|
||||
6. add/update tests where behavior changed;
|
||||
5. load `development-method-ttd` and [runtime-and-ci.md — Unit testing](runtime-and-ci.md#unit-testing); observe the product-reason unit failure before behavior changes;
|
||||
6. implement the smallest safe forward fix, preserving valid shared work and missing-RED honesty;
|
||||
7. run local validation;
|
||||
8. commit and push through the approved branch workflow;
|
||||
9. inspect CI for the exact new head SHA;
|
||||
@@ -53,14 +53,4 @@ Update these pages from verified project practice. Do not document a planned pro
|
||||
|
||||
## Synchronization Workflow
|
||||
|
||||
When planning documentation, Architecture structure, or Kanban state changes while implementation remains gated, follow [`planning-artifact-reconciliation.md`](planning-artifact-reconciliation.md). It defines fresh remote-head discovery, exact-merge-SHA validation, `READY_FOR_DELIVERY` handoff interpretation, evidence boundaries, and duplicate-status suppression.
|
||||
|
||||
1. Read new same-project activity and enough delivery history to avoid duplicates.
|
||||
2. Before claiming new task work, verify exact-item `Approved for Implementation` evidence, exact Task `READY_FOR_DELIVERY` state, task dependencies, approved UI/UX handoff when applicable, and target version.
|
||||
3. Identify executable tasks, CI failures, blockers, requirements/ADR implications, and documentation drift.
|
||||
4. Load all applicable project engineering skills.
|
||||
5. Complete at least one useful safe activity when an authorized path exists; otherwise document and route the exact blocker.
|
||||
6. Escalate uncertainty or contradiction rather than selecting direction.
|
||||
7. Verify local and remote results and update task/Feature progress in project documentation.
|
||||
8. Maintain Ways of Working and Engineering pages when durable practice changed.
|
||||
9. Post a concise update with work completed, evidence, blockers, and required decisions.
|
||||
Before reconciling planning/Architecture/Kanban changes, load [planning-artifact-reconciliation.md](planning-artifact-reconciliation.md) for Task-row semantics and its verification-owner loads. Use the entry skill's synchronization/iteration contract for useful safe work and current documentation. Reconcile only changed evidence; do not duplicate its workflow here.
|
||||
Reference in new issue
Block a user