Files
stack/docs/native-kanban-sot/DOCUMENTATION-CHECKLIST.md
jason.woltje 49e8a54105
All checks were successful
ci/woodpecker/push/publish Pipeline was successful
ci/woodpecker/push/ci Pipeline was successful
docs(#751): Publish native Kanban/SOT canon (#752)
2026-07-14 17:08:09 +00:00

1.9 KiB
Raw Blame History

Documentation Completion Checklist — Native Kanban/SOT Canon

Tracking: Mosaic Stack issue #751 Scope: Requirements and contract publication only; runtime implementation follows in separate slices.

Required artifacts

  • Project docs/PRD.md exists; the workstream requirements refine its task/project-management scope.
  • Canonical workstream requirements published at docs/requirements/native-kanban-sot.md.
  • Mission manifest, task decomposition, frozen shared contract, and typed contract declarations included.
  • docs/SITEMAP.md updated.
  • Independent initial review and final GO report stored under docs/reports/native-kanban-sot/.
  • Task scratchpad stored under docs/scratchpads/.
  • User/Admin/Developer guides — N/A for canon-only publication; required in implementation slices that change behavior or operations.
  • OpenAPI and endpoint index — N/A until KBN-105 freezes implementation-ready endpoint contracts.

Structural and root hygiene

  • Canonical requirements are under docs/requirements/.
  • Workstream artifacts are under docs/native-kanban-sot/.
  • Review reports are under docs/reports/native-kanban-sot/.
  • No new unscoped document was added to the docs/ root.
  • Root mission/task rollups link to the workstream.

Review gate

  • Author and independent reviewer are different agents.
  • KCR-001016 closure was independently verified.
  • Ultron final gate returned GO with zero BLOCKER/HIGH findings.
  • Formatter, lint, typecheck, strict contract TypeScript, link, scope, and invariant publication validation passed in the current Stack toolchain.
  • PR review, CI, squash merge, and issue closure remain required before publication completion.

Publishing

  • Canonical source remains in-repository.
  • No external publishing platform is required for this internal architecture contract.