Skip to content

TRACKING — Epic #84: realign org-level ADRs with platform reality #94

Description

@Polichinel

Epic: #84

Checklist for epic #84. Work the stories top to bottom and tick them off. Each links to a fully specified issue — context, work, acceptance criteria, and validation commands live there, not here.

Phase 1 — Retire what is wrong (no dependencies between these three)

Phase 2 — Adjudicate the rest (fully parallel; each needs a human call)

Phase 3 — Make staleness visible (strictly sequential)

Parallel track — open early, runs long


Epic acceptance — verify before closing #84

  • No org-level ADR contradicts a sibling ADR without an explicit Superseded by pointer
  • Every surviving record carries owner and review_date; check_adrs.py reports 0 warnings and 0 errors
  • Supersession detection exists, is wired into validate_docs.sh, and has a passing offline test
  • ./scripts/validate_docs.sh exits 0
  • python3 scripts/generate_adr_index.py --check passes
  • grep -c '_unassigned_' ADR/index.md returns 0
  • Register: C-02, C-03, C-06 updated; C-11 and C-12 registered and dispositioned
  • þing open on target-scale authority, or a recorded decision explaining why not

Run after every story

./scripts/validate_docs.sh
python3 scripts/generate_adr_index.py && python3 scripts/generate_adr_index.py --check

Regenerate ADR/index.md whenever a status changes — it is generated, and CI checks it is current.


Out of scope — do not pick these up here

Work Belongs to
Onboarding guide, internal_technical_guide.md #82 · epic views-platform/views-appwrite#26
Relocating monthly_run_guide.md views-platform/views-models#387
Relocating the technical setup guide views-platform/views-pipeline-core#453
Editing sibling repositories' ADRs Their repositories — ADR-0000 cl. 2
Migrating build systems Follow-on issues from #88, if the decision requires them

⚠️ Known collision — read before touching the onboarding guide

Issue #83 was closed NOT_PLANNED arguing that the [Internal Tech Guide] link should not be filled while its target describes a setup that hard-fails — views-models tools/credentials/platform_env.sh exits with FATAL: the Appwrite coordinate registry does not exist (lines 75, 114, 125, 149 on origin/development).

During pre-epic work on 2026-08-13 that link was filled anyway. It satisfies the link checker and contradicts #83's reasoning. The change is unstaged and belongs to #82, not this epic. Reverting or reconciling it is a decision for that epic's owner.

Source

review-base-docs audit, 2026-08-13 — 1 critical, 3 high, 5 medium, 2 low.
Register: reports/technical_risk_register.md (6 open, 4 resolved).

Metadata

Metadata

Assignees

No one assigned

    Labels

    documentationImprovements or additions to documentationepicLarge body of work tracked across multiple storiestrackingChecklist issue tracking an epic to completion

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions