weichen 1ac79c2a90 Define iterative delivery with explicit stage reviews ...

Why: make requirements, experiments and implementation revisions reviewable while retaining bounded continuous authorization.

Evidence: task-card SELF receipts include expected red regressions and 104 passing governance checks; full candidate verification follows.

Impact: add project delivery policy and generated task fields; make post-merge reminders read-only.

Refs: .task/feature-iterative-delivery.md; policy/delivery.md

2026-10-07 02:53:20 +00:00

..

adoption.md

Define iterative delivery with explicit stage reviews

2026-10-07 02:53:20 +00:00

architecture-baseline.json

Record the make test evidence

2026-10-06 15:03:02 +00:00

architecture.yaml

Add an architecture edge ratchet and waiting-state tokens

2026-10-03 16:02:57 +00:00

delivery.md

Define iterative delivery with explicit stage reviews

2026-10-07 02:53:20 +00:00

facts.md

Fix F2 verify command for the markdown-list token file format

2026-10-05 10:49:29 +00:00

governance.md

Define iterative delivery with explicit stage reviews

2026-10-07 02:53:20 +00:00

lib-deps-allowlist.txt

Pin the D1 heads and cover the adapter modules

2026-10-03 13:47:02 +00:00

platform-admission.md

Make development gates preserve work and verifiable evidence

2026-10-05 12:36:02 +00:00

tool-adaptation-matrix.md

Define iterative delivery with explicit stage reviews

2026-10-07 02:53:20 +00:00

tool-adaptation-zcode.md

Make development gates preserve work and verifiable evidence

2026-10-05 12:36:02 +00:00