Fix progressive disclosure violations and amend DoD/Self-Audit for document deliverables#31
Merged
Merged
Conversation
…cument deliverables Three canon documents from the Anti-Cache Lying work violated every tier of the Writing Canon progressive disclosure requirements (no blockquotes, no Summary sections, generic headers). This commit rewrites all three with proper progressive disclosure, documents the incident, and closes the structural gap that allowed it: - Replace odd/constraint/anti-cache-lying.md with blockquote, Summary, descriptive headers - Replace docs/incidents/oddkit-stale-cache-2026-02.md with full progressive disclosure - Replace docs/oddkit/IMPL-content-addressed-caching.md with full progressive disclosure - Create docs/incidents/progressive-disclosure-failure-2026-02.md (incident record) - Amend canon/constraints/definition-of-done.md: add Document Deliverables section, Operating Constraint for Writing Canon validation, "The document exists" failure mode - Amend canon/methods/self-audit.md: add 5b Document Structure Check, update Outline and Description to reflect ten areas - Create docs/oddkit/IMPL-writing-canon-gate.md (OddKit enforcement implementation plan) https://claude.ai/code/session_01RNhBecvpHv3hXHVQGej8hY
…ces (Tasks 8-14) Complete the progressive disclosure fix by wiring enforcement into the system: - Amend canon/meta/writing-canon.md: add Enforcement section, governs/complements metadata - Create odd/constraint/README.md: index of all three ODD constraints - Create docs/incidents/README.md: index of both incident records with "Led To" column - Amend docs/CONTENT-MAP.md: register anti-cache-lying in odd/constraint/, add docs/incidents/ - Amend canon/constraints/README.md: cross-reference ODD-level constraints - Amend odd/constraint/anti-metric-laundering.md: add See Also sibling links - Amend odd/constraint/anti-cache-lying.md: add See Also sibling links All cross-references verified: constraint siblings link bidirectionally, incident records link to their resolutions, DoD/Self-Audit link to Writing Canon, Writing Canon links back to enforcement mechanisms. https://claude.ai/code/session_01RNhBecvpHv3hXHVQGej8hY
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Three canon documents from the Anti-Cache Lying work violated every tier of
the Writing Canon progressive disclosure requirements (no blockquotes, no
Summary sections, generic headers). This commit rewrites all three with proper
progressive disclosure, documents the incident, and closes the structural gap
that allowed it:
Operating Constraint for Writing Canon validation, "The document exists" failure mode
and Description to reflect ten areas
https://claude.ai/code/session_01RNhBecvpHv3hXHVQGej8hY
Note
Low Risk
Documentation-only changes; main risk is unintended policy/enforcement expectations changing how work is declared “done,” not runtime behavior.
Overview
Reframes document writing quality as an enforceable deliverable: the Definition of Done now requires validating document outputs against the Writing Canon progressive-disclosure checklist, and the Self-Audit adds a dedicated document-structure validation step.
Adds an incidents registry (
docs/incidents/README.md) and a new incident report (docs/incidents/progressive-disclosure-failure-2026-02.md) to document why the enforcement exists, plus refreshes related incident/implementation docs (includingodd/constraint/anti-cache-lying.mdanddocs/oddkit/IMPL-content-addressed-caching.md) to comply with progressive disclosure.Introduces
docs/oddkit/IMPL-writing-canon-gate.mddescribing a future OddKit preflight/validate gate for checking blockquotes, summary sections, and header scan quality on document deliverables, and updates indexes (canon/constraints/README.md,docs/CONTENT-MAP.md,odd/constraint/README.md) to surface the new constraint/incidents content.Written by Cursor Bugbot for commit bd4fba8. This will update automatically on new commits. Configure here.