TODO.md

Claude Code Rules - TODO

Last Updated: 2026-03-15

---

✅ Completed

• UDVC-1 design/runtime/changelog synchronization baseline applied across governance chains.
• Changelog-layer metadata normalization completed (mandatory headers + active-session integrity).
• WS-1 to WS-6 hardening execution slices completed and synchronized in master governance docs.
• Authorized adversarial workflow rule suite completed (refusal-minimization, refusal-classification, recovery-contract, dan-safe-normalization).
• Core documentation-control standards implemented and maintained (document-changelog-control, document-design-control, document-patch-control, project-documentation-standards, todo-standards).
• Align patch documents to UDVC-1 metadata contract (patches/consistency-rule-enhancement.patch.md, patches/legacy-rules-migration.patch.md).
• Run final consistency audit across design/rule/changelog/TODO/patch layers (triad, links, anchors, sessions, TODO compliance).
• Create runtime unified-version-control-system.md and align related governance references after design/changelog-first rollout.
• Create runtime explanation-quality.md and align master rule inventory after design/changelog-first rollout.
• Complete anti-poisoning cleanup wave across README, master design, governance templates, runtime metadata policy, and support-artifact boundary handling.
• Apply balanced concise-summary patch to accurate-communication and explanation-quality, then install updated runtime rules.
• Extend patch workflow to support flexible phased implementation planning and add a reusable non-governed root-level template.
• Create first-class phase-implementation rule chain, realign patch/documentation authority boundaries, rewrite the root helper as readable markdown, and install updated runtime rules.
• Refine role-specific checklists so phase-implementation validates phased execution-planning quality while document-patch-control validates governed patch/review quality.
• Create first-class answer-presentation rule chain and integrate it into the active runtime inventory, master design, README, changelog, and installed runtime rules.
• Make /phase the live namespace for phased execution: require phase/SUMMARY.md, require child phase files under phase/, and keep /patches separate from the live phase-plan workspace.
• Strengthen phase-implementation reviewability: require each child phase to show explicit design-to-phase extraction mapping and a review-oriented flow diagram that explains what part is being enhanced, developed, migrated, validated, or replaced.
• Strengthen phase/SUMMARY.md reviewability: require an overview flow diagram for the whole phase set and expand the template with a fuller canonical child-phase example.
• Add a summary-level design extraction table to phase/SUMMARY.md so reviewers can map design sources → phase files → derived work → target outcomes before reading individual phases.
• Add a reviewer checklist block to each child phase so review can quickly confirm source correctness, flow clarity, phase boundaries, dependencies, and evidence readiness.
• Standardize child-phase review outcomes with shared sign-off status, reviewer severity, and reviewer disposition values.
• Add a summary-level review aggregate table to phase/SUMMARY.md so approvers can see per-phase sign-off status, severity, disposition, and blocker/follow-up state from one place.
• Define a completion boundary and stop rule for the phase-planning model, and narrow communication rules so completed work does not force artificial extra options or endless follow-up suggestions.
• Refine option-offering guidance so next-step options are suggested only when genuinely useful and not treated as a mandatory ending pattern.
• Create first-class operational-failure-handling rule chain and integrate it into the active runtime inventory, README, changelog, TODO, and canonical install set.
• Upgrade operational-failure-handling to explicit case-profile semantics for Web Search, WebFetch, local-path, permission, and tool-approval failures, then reinstall the updated runtime rule.
• Strengthen document-patch-control so governed .patch.md files must show target locations and comparison-friendly current-vs-proposed change representation instead of vague prose-only plans.
• Create first-class evidence-grounded-burden-of-proof and patch accurate-communication, zero-hallucination, anti-sycophancy, and no-variable-guessing so contradiction, absence, and user-directed judgment claims now require explicit burden-of-proof discipline; materialize the touched runtime stubs; update master inventories to 28 active runtime rules; and reinstall the updated runtime rules.
• Upgrade phase-implementation into a one-way design+patch source-synthesis layer, keep patch ≠ phase intact, align document-patch-control and project-documentation-standards to the clarified boundary, refresh master docs, and reinstall the touched runtime rules.
• Create first-class runtime-topology-control rule chain and integrate it into the active runtime inventory, README, changelog, TODO, and installed runtime rules.
• Apply diagnostic-snapshot communication/explanation/presentation patch across accurate-communication, explanation-quality, and answer-presentation, then synchronize design/runtime/changelog/master/TODO governance state.
• Apply micro-polish natural-response refinement across answer-presentation, explanation-quality, and accurate-communication with stronger canonical examples and re-sync installed runtime rules.
• Refine path-aware naming rules across document-patch-control and project-documentation-standards, then synchronize master governance docs and installed runtime copies.
• Refine easier-to-understand explanation/reporting guidance across explanation-quality, answer-presentation, and accurate-communication, then synchronize governance docs and installed runtime rules.
• Refine stage-progression and whole-set-first guidance across explanation-quality, answer-presentation, and accurate-communication, then synchronize governance docs and installed runtime rules.

---

📋 Tasks To Do

Current Governance Execution

• (none)

Deferred Enhancements

• Automated validation script for documentation compliance (deferred by user).
• Integration testing for design/changelog/rule/TODO integration paths (deferred by user).

---

📜 History

Date	Changes
2026-03-17	Refined stage-progression and whole-set-first guidance across explanation-quality (v2.1), answer-presentation (v1.5), and accurate-communication (v2.1): added next-stage preference and full-set-first framing rules, aligned design/design.md inventory references and README.md rule descriptions, refreshed changelog/changelog.md to v6.1, and re-synchronized the installed runtime copies for the three touched rules.
2026-03-15	Refined easier-to-understand explanation/reporting guidance across explanation-quality (v2.0), answer-presentation (v1.4), and accurate-communication (v2.0): added stronger what-it-is/what-it-is-not, now-versus-later, user-visible outcome, human-language gloss, and short-recap guidance; aligned design/design.md inventory references and README.md rule descriptions; refreshed changelog/changelog.md to v6.0; and re-synchronized the installed runtime copies for the three touched rules.
2026-03-15	Added path-aware naming refinement across document-patch-control (v2.2) and project-documentation-standards (v2.5): defined filename-authoritative versus path-authoritative naming, added directory-as-namespace guidance for governed workspaces, aligned design/design.md inventory references and README.md rule descriptions, refreshed changelog/changelog.md to v5.8, and re-synchronized the installed runtime copies for the two touched rules.
2026-03-15	Applied micro-polish natural-response refinement across answer-presentation (v1.2), explanation-quality (v1.8), and accurate-communication (v1.8): added stronger canonical snapshot and walkthrough examples, aligned design/design.md inventory references and README.md rule descriptions, refreshed changelog/changelog.md to v5.7, and re-synchronized the installed runtime copies for the three touched rules.
2026-03-14	Applied synchronized diagnostic-snapshot governance patch across answer-presentation (v1.1), explanation-quality (v1.7), and accurate-communication (v1.7): updated each chain’s design/runtime/changelog artifacts, aligned design/design.md inventory references to the new versions, refreshed changelog/changelog.md to v5.6, and synchronized TODO completion tracking for the patch wave.
2026-03-14	Created first-class runtime-topology-control rule chain: added design/runtime-topology-control.design.md, runtime-topology-control.md, and changelog/runtime-topology-control.changelog.md; updated design/design.md and README.md to 29 active runtime rules; placed the new chain in User Control in the master design model and Quality & Safety in the public README inventory; extended the canonical RULE_FILES install set; refreshed changelog/changelog.md; and installed the new runtime rule into ~/.claude/rules/runtime-topology-control.md as a bounded runtime mutation posture chain.
2026-03-13	Upgraded the phase-planning model into a one-way design+patch source-synthesis layer: updated design/phase-implementation.design.md, phase-implementation.md, changelog/phase-implementation.changelog.md, and phase-implementation-template.md from the design-only extraction model to a source-synthesis model; aligned document-patch-control to v2.1 and project-documentation-standards to v2.4 with narrow boundary clarifications; repaired the stale phase-implementation.md v1.3 reference; refreshed design/design.md, README.md, and changelog/changelog.md; and reinstalled the touched runtime rules into ~/.claude/rules/.
2026-03-12	Created first-class evidence-grounded-burden-of-proof and completed the combined burden-of-proof rollout: added the new design/runtime/changelog triad; updated accurate-communication to v1.6 plus zero-hallucination, anti-sycophancy, and no-variable-guessing to v1.3 with explicit fact/inference/hypothesis separation, scoped non-finding semantics, and a direct rule against unsupported user-directed contradiction; updated design/design.md and README.md to 28 active runtime rules; refreshed the master changelog; and reinstalled the new/touched runtime rules into ~/.claude/rules/.
2026-03-12	Strengthened document-patch-control to v2.0: updated the design/runtime chain so governed .patch.md files must identify target locations and show comparison-friendly current-vs-proposed change representation; clarified that non-code patches must declare themselves as conceptual/non-snippet patches; refreshed chain/master changelogs; synchronized master references; and recorded the patch-rule upgrade in TODO.
2026-03-12	Upgraded operational-failure-handling to v1.1 case-profile semantics: refined the design/runtime chain from generic retry guidance into a profile-driven model, added seeded explicit cases for Web Search, WebFetch, local-path, permission, and tool-approval failures, updated design/design.md to point at operational-failure-handling.design.md v1.1, refreshed the master changelog, and reinstalled the updated runtime rule into ~/.claude/rules/operational-failure-handling.md.
2026-03-12	Created first-class operational-failure-handling rule chain: added design/operational-failure-handling.design.md, operational-failure-handling.md, and changelog/operational-failure-handling.changelog.md; updated design/design.md and README.md to 27 active runtime rules; extended the canonical RULE_FILES install set; refreshed the master changelog; and recorded rollout completion in TODO.
2026-03-11	Refined option-offering guidance: updated accurate-communication and explanation-quality so next-step options are suggested only when genuinely useful, materially helpful, and tied to a real continuation path rather than being treated as a mandatory ending pattern.
2026-03-11	Finalized the phase-planning model boundary: updated phase-implementation with an explicit Definition of Done and stop rule, updated phase-implementation-template.md with the same completion boundary, and narrowed accurate-communication plus explanation-quality so completed work no longer forces artificial next-step options when no real continuation is needed.
2026-03-11	Added summary-level review aggregation: updated phase-implementation so phase/SUMMARY.md must include a review summary table, expanded phase-implementation-template.md with that table in both the summary template and example section, and recorded the enhancement in TODO history.
2026-03-11	Standardized child-phase review outcomes: updated phase-implementation so child phases use one sign-off status vocabulary plus reviewer severity/disposition fields, expanded phase-implementation-template.md with those review-outcome fields in both the child template and canonical example, and recorded the enhancement in TODO history.
2026-03-11	Added reviewer-ready child-phase validation: updated phase-implementation so each child phase must include a reviewer checklist block, expanded phase-implementation-template.md with that checklist in both the child template and canonical example, and recorded the enhancement in TODO history.
2026-03-11	Added summary-level design extraction mapping: updated phase-implementation so phase/SUMMARY.md must include a design extraction summary table, expanded phase-implementation-template.md with that table in both the template and example sections, and recorded the enhancement in TODO history.
2026-03-11	Strengthened SUMMARY.md and child-phase reviewability: updated phase-implementation so phase/SUMMARY.md must include an overview flow diagram for the full phase set, expanded phase-implementation-template.md with that summary-level diagram plus a fuller canonical child-phase example, and recorded the enhancement in TODO history.
2026-03-11	Strengthened phase reviewability: updated phase-implementation so each child phase must explicitly map design source → derived execution work and include a review-oriented flow diagram, updated phase-implementation-template.md to require those sections in child phase files, and recorded the enhancement in TODO history.
2026-03-11	Moved live phased execution to /phase: updated phase-implementation to require phase/SUMMARY.md plus child phase files under phase/, updated document-patch-control and project-documentation-standards so /patches is no longer the live phase namespace, rewrote phase-implementation-template.md to demonstrate the new /phase structure, refreshed README.md, and recorded the rollout in TODO history.
2026-03-10	Created first-class answer-presentation rule chain: added design/answer-presentation.design.md, answer-presentation.md, and changelog/answer-presentation.changelog.md; updated design/design.md and README.md to 26 active runtime rules; and installed the new presentation-layer runtime rule into ~/.claude/rules/answer-presentation.md.
2026-03-10	Refined role-specific checklist boundaries: updated phase-implementation to v1.1 with a dedicated execution-planning validation checklist, updated document-patch-control to v1.7 with a dedicated patch-governance checklist, clarified that the two checklists serve different roles, and preserved the patch ≠ phase boundary.
2026-03-10	Created first-class phase-implementation rule chain: added design/phase-implementation.design.md, phase-implementation.md, and changelog/phase-implementation.changelog.md; refocused document-patch-control to governance/metadata role only; updated project-documentation-standards to distinguish phase rule vs patch instance vs root helper; rewrote phase-implementation-template.md into readable practical markdown with richer phase status, action points, design references, and TODO/changelog companion guidance; updated design/design.md + README.md to 25 active runtime rules; and installed updated runtime rules into ~/.claude/rules/.
2026-03-10	Corrected flexible phase template placement to the RULES root: updated document-patch-control to v1.5, updated project-documentation-standards to v2.0, created phase-implementation-template.md at root, refreshed design/design.md, and reinstalled the updated runtime rules into ~/.claude/rules/.
2026-03-10	Extended the patch workflow for flexible phased implementation planning: updated document-patch-control to v1.4, updated project-documentation-standards to v1.9, and at that time introduced a non-governed reusable phase template under the temporary historical path support/phase-implementation-template.md; this was later corrected to the root phase-implementation-template.md location.
2026-03-09	Applied balanced concise-summary patch to accurate-communication and explanation-quality: updated both design/runtime/changelog chains, refreshed design/design.md inventory references, and installed the updated runtime rules into ~/.claude/rules/.
2026-03-08	Completed anti-poisoning cleanup wave: rewrote README.md to overview-only scope, refactored design/design.md to active-state-only guidance, normalized governance design/runtime docs to the canonical Design + Session + Full history model, converted design/accurate-communication.design.md to navigator-style active design content, and reclassified design/image.prompt.design.md into support-only support/image-prompts.md.
2026-03-07	Upgraded active explanation-quality chain to v1.2: updated design/explanation-quality.design.md, explanation-quality.md, and changelog/explanation-quality.changelog.md with negative triggers, closing-summary behavior, decision usefulness checks, and required next-step option endings; synchronized design/design.md and changelog/changelog.md.
2026-03-07	Completed runtime rollout for explanation-quality: created explanation-quality.md (v1.1), synchronized design/explanation-quality.design.md + changelog/explanation-quality.changelog.md (v1.1), updated design/design.md and README.md to active-state inventory, and closed the pending TODO rollout task.
2026-03-07	Created design/explanation-quality.design.md + changelog/explanation-quality.changelog.md (v1.0), updated design/design.md to register pending activation state, and queued runtime explanation-quality.md materialization for later approval.
2026-02-24	Completed runtime rollout closure for unified version controller: created unified-version-control-system.md (v1.1), synchronized changelog/unified-version-control-system.changelog.md (v1.1), updated design/design.md to active-state indexing, and closed pending TODO rollout task.
2026-02-24	Created design/unified-version-control-system.design.md + changelog/unified-version-control-system.changelog.md (v1.0) and queued runtime unified-version-control-system.md creation as pending by request.
2026-02-24	Reconfirmed single-standard version governance scope in master docs: updated design/design.md (UDVC-1 unified mechanism across design/changelog/TODO/patch), changelog/changelog.md v3.6, and synchronized TODO execution history.
2026-02-23	Completed final consistency audit across design/rule/changelog/TODO/patch layers: patch metadata contract closure, active-session placeholder removal (design/accurate-communication.design.md), and legacy changelog #version-* anchor normalization.
2026-02-23	Aligned patches/consistency-rule-enhancement.patch.md and patches/legacy-rules-migration.patch.md to UDVC-1 metadata contract (mandatory fields, version/session/history-link alignment) and created changelog/consistency-rule-enhancement.changelog.md authority file.
2026-02-23	Simplified TODO.md to canonical todo-standards structure (Completed, Tasks To Do, History) and removed dashboard/priority overhead artifacts.
2026-02-23	Completed changelog metadata normalization sweep: mandatory header completion, parent-reference normalization, and active-session placeholder removal in changelog layer.
2026-02-22	Completed WS-1..WS-6 hardening synchronization slices and aligned governance references across design/runtime/changelog artifacts.
2026-02-21	Completed authorized adversarial workflow suite design+rules+changelog chain rollout.
2026-02-01	Completed legacy rule migration and patch-control standard integration baseline.
2026-01-21	Completed master design/changelog restructuring and rules-template standardization baseline.