Files
agentic-dev/docs/work/epics/compliance-docs-scaffolds/06-doc-wiring/_story.md
Danijel Martinek 96a8554871 chore(work): decompose compliance-docs-scaffolds epic
Generated 1 epic + 6 stories under docs/work/epics/ from the approved
PRD docs/work/prds/compliance-docs-scaffolds.prd.md. Stories cover
landing + refreshing operator-checklist.md, the seven fill-in policy
templates, the pre-launch compliance checklist, the compliance-overview
hub, and doc wiring (CLAUDE.md, README, glossary). Final epic of
ADR-025. Ready for `pnpm work dispatch --execute`.
2026-05-20 13:58:24 +02:00

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 todo ~
05-compliance-overview
2026-05-20T12:00:00Z 2026-05-20T11:58:25.281Z

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.md has a "Policy templates" section that explains: the docs/compliance/templates/ directory, the copy-to-compliance/ workflow, the [FILL IN:] convention, and the grep -rn '\[FILL IN:' compliance/ verification one-liner.
  • docs/glossary.md has 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:audit all pass.

In scope

  • docs/compliance/README.md — add "Policy templates" section.
  • docs/glossary.md — add 4 entries.
  • CLAUDE.md — add compliance-overview.md pointer to "Read First".

Out of scope

  • Any changes to docs/guides/compliance-overview.md or 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.md beyond the generator schema + policy template scope.

Tasks

  • Add a "Policy templates" section to docs/compliance/README.md (explaining the docs/compliance/templates/ directory, copy-to-compliance/ workflow, [FILL IN:] convention, and the grep -rn '\[FILL IN:' compliance/ one-liner) and add four glossary entries (pre-launch compliance checklist, compliance overview, fill-in template, [FILL IN:] marker) to docs/glossary.md; commit as docs(compliance): document policy template convention in README and glossary.
  • Add docs/guides/compliance-overview.md to the "Read First" section of CLAUDE.md with a one-line description matching the existing entries' style; commit as docs(core): add compliance-overview.md to CLAUDE.md Read First.