Publish manifest and wiki mapping recorded #12

Closed
opened 2026-10-06 10:13:28 +00:00 by pit · 0 comments
Owner

Part of #7

What to build

Make the publish decision explicit per document. A manifest that lives in the repo — not in the sync script — lists what reaches the wiki, with allowlist semantics, so a new, renamed or moved document cannot silently reach the wiki without a decision. Record the wiki page mapping against the wiki-sync work.

Acceptance criteria

  • A publish manifest lives in the repo, is allowlist by default (a document is published only if listed, or explicitly excluded), and carries the exclusions.
  • A coverage check fails when a document is neither published nor excluded, so changing the docs forces a publish decision. Running it shows it pass when covered and fail when not.
  • The page mapping is recorded (docs entry point to Home, architecture, runbooks index and pages as numbered runbook pages, decisions index and pages as numbered ADR pages, actions index, glossary), with the agent docs excluded and mirror semantics preserved.
  • The mapping change and the collision between the two decisions numbered 0001 are recorded on the wiki-sync issue; no sync, hook or workflow is built here.
  • Lands as its own PR.

Blocked by

Part of #7 ## What to build Make the publish decision explicit per document. A manifest that lives in the repo — not in the sync script — lists what reaches the wiki, with allowlist semantics, so a new, renamed or moved document cannot silently reach the wiki without a decision. Record the wiki page mapping against the wiki-sync work. ## Acceptance criteria - [ ] A publish manifest lives in the repo, is allowlist by default (a document is published only if listed, or explicitly excluded), and carries the exclusions. - [ ] A coverage check fails when a document is neither published nor excluded, so changing the docs forces a publish decision. Running it shows it pass when covered and fail when not. - [ ] The page mapping is recorded (docs entry point to Home, architecture, runbooks index and pages as numbered runbook pages, decisions index and pages as numbered ADR pages, actions index, glossary), with the agent docs excluded and mirror semantics preserved. - [ ] The mapping change and the collision between the two decisions numbered 0001 are recorded on the wiki-sync issue; no sync, hook or workflow is built here. - [ ] Lands as its own PR. ## Blocked by - #8
pit closed this issue 2026-10-06 12:14:42 +00:00
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
olympus/infra-forge#12
No description provided.