2.9 KiB
2.9 KiB
id, epic, title, type, status, feature, depends-on, blocks, created, updated
| id | epic | title | type | status | feature | depends-on | blocks | created | updated | |
|---|---|---|---|---|---|---|---|---|---|---|
| 06-doc-wiring | compliance-docs-scaffolds | Wire compliance docs into CLAUDE.md, README, and glossary | technical-story | done | ~ |
|
2026-05-20T12:00:00Z | 2026-05-20T12:52:53.917Z |
Goal
Complete the one-directional wiring of Epic D's new documents into the three shared navigation surfaces: add a "Policy templates" section to docs/compliance/README.md, add four new glossary entries to docs/glossary.md, and add a compliance-overview.md pointer to CLAUDE.md's "Read First" section.
Why
Without these changes, compliance-overview.md is orphaned from the primary AI navigation entry point (CLAUDE.md), the policy templates have no discovery path in docs/compliance/, and the [FILL IN:] marker convention has no canonical glossary definition. The PRD specifies these as the final wiring step, after all new documents exist so links resolve.
Done when
docs/compliance/README.mdhas a "Policy templates" section that explains: thedocs/compliance/templates/directory, the copy-to-compliance/workflow, the[FILL IN:]convention, and thegrep -rn '\[FILL IN:' compliance/verification one-liner.docs/glossary.mdhas four new entries:pre-launch compliance checklist,compliance overview,fill-in template,[FILL IN:] marker.- CLAUDE.md "Read First" lists
compliance-overview.md(with path and one-line description matching the existing entries' style). - No existing content in any of the three files is removed or modified.
- Every relative Markdown link added resolves to an existing file.
pnpm lint && pnpm typecheck && pnpm test && pnpm conformance && pnpm fallow:auditall pass.
In scope
docs/compliance/README.md— add "Policy templates" section.docs/glossary.md— add 4 entries.CLAUDE.md— addcompliance-overview.mdpointer to "Read First".
Out of scope
- Any changes to
docs/guides/compliance-overview.mdor the templates (they are complete by the time this story runs). - Any changes to the existing compliance guides (
dsr.md,consent.md, etc.). - Broadening
docs/compliance/README.mdbeyond the generator schema + policy template scope.
Tasks
- Add a "Policy templates" section to
docs/compliance/README.md(explaining thedocs/compliance/templates/directory, copy-to-compliance/workflow,[FILL IN:]convention, and thegrep -rn '\[FILL IN:' compliance/one-liner) and add four glossary entries (pre-launch compliance checklist,compliance overview,fill-in template,[FILL IN:] marker) todocs/glossary.md; commit asdocs(compliance): document policy template convention in README and glossary. - Add
docs/guides/compliance-overview.mdto the "Read First" section ofCLAUDE.mdwith a one-line description matching the existing entries' style; commit asdocs(core): add compliance-overview.md to CLAUDE.md Read First.