Aller au contenu

BC-068D — Documentation Consolidation

Status: HISTORICAL This report records the BC-068D documentation consolidation. For the current architecture, see: ../index.md.

Verdict

BC-068D is closable.

Only documentation was changed.

Strategy

Chosen strategy for BC-068D:

  • consolidate current truth into a small set of CURRENT documents;
  • mark BC-064 → BC-068 reports as HISTORICAL;
  • mark only clearly superseded draft material as OBSOLETE;
  • keep the BC-068 worktree manifest unchanged for documentation classification, because the current docs/operations/bc-068* catch-all already prevents fresh unknown drift and BC-068D stayed docs-only.

Current documents

Doc Current owner Scope Authoritative
docs/index.md BC-068D single documentation entry point yes
docs/architecture/dependances.md architecture dependency contract yes
docs/design/frontend.md frontend boundary frontend responsibilities / forbidden deps yes
docs/design/runtime.md runtime boundary runtime responsibilities / forbidden deps yes
docs/adapters/wordpress.md WordPress adapter boundary bootstrap / adapter / transport boundary yes
docs/runtime/overview.md runtime architecture runtime topology + dormant-runtime final state yes
docs/frontend/projections.md frontend compatibility projection shim compatibility yes
docs/projections/overview.md projection boundary projection responsibilities and invariants yes
docs/operations/runtime-current-state.md operations operational runtime posture yes
docs/operations/write-inventory-current-state.md operations business/runtime write inventory yes
docs/operations/technical-write-inventory-current-state.md operations technical WordPress write inventory yes

Historical documents

Historical and still useful:

Historical doc family Still useful Superseded by Keep
docs/architecture/bc-064*.md yes current dependency / projection docs yes
docs/architecture/bc-065*.md yes current dependency / runtime docs yes
docs/architecture/bc-066*.md yes current dependency / runtime docs yes
docs/architecture/bc-067*.md yes current dependency / runtime docs yes
docs/operations/bc-068a-*.md yes this report + current index yes
docs/operations/bc-068b-*.md yes this report + current index yes
docs/operations/bc-068c-*.md yes this report + current index yes

Obsolete documents

Doc Superseded by Safe to remove later
docs/frontend/navigation-runtime.md docs/frontend/projections.md, docs/projections/overview.md, docs/adapters/wordpress.md yes

Unknown documents

None newly introduced by BC-068D in the consolidated current/historical set.

Broader repository-wide unknown classification remains a BC-068E topic, not a BC-068D blocker.

Contradictions corrected in CURRENT docs

Topic Previous issue Correct current state Action
runtime docs “target design” wording could be read as not-current runtime boundary docs now explicitly describe the current certified boundary corrected in CURRENT docs
frontend docs generic design wording could hide projection-first final state frontend is now explicitly documented as projection-first and read-only corrected in CURRENT docs
WordPress docs “topologie cible” wording could imply not-yet-certified state topology is now documented as certified current state corrected in CURRENT docs
documentation entry point index mixed old project posture with current architecture truth single CURRENT index now points to authoritative docs corrected
Source doc Broken link Action
docs/frontend/navigation-runtime.md absolute filesystem references replaced with relative repo paths
docs/operations/bc-068a-worktree-consolidation-audit.md absolute manifest link replaced with relative path

Repetitions reduced

Repeated topic Canonical owner
current documentation navigation docs/index.md
WordPress adapter / bootstrap truth docs/adapters/wordpress.md
runtime boundary docs/design/runtime.md
runtime topology + dormant-runtime final state docs/runtime/overview.md
frontend projection compatibility docs/frontend/projections.md

Risks

  • many older non-BC docs outside the BC-064 → BC-068 consolidation path still exist and may need later classification;
  • historical reports intentionally preserve old wording and decisions, so readers must enter through docs/index.md;
  • broader documentation IA cleanup remains a BC-068E candidate.

Rollback

  • restore modified docs;
  • remove docs/operations/bc-068d-documentation-consolidation.md;
  • rerun validation commands;
  • no SQL rollback;
  • no runtime sync.

Preparation for BC-068E

Recommended next step:

  • classify the broader long-tail docs still outside the compact CURRENT set;
  • decide whether additional generic overviews should become HISTORICAL or OBSOLETE;
  • optionally normalize status banners beyond the BC-064 → BC-068 families.