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
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).
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)
Start here. The one actively misleading record. Blocks S2 — Reconcile ADR-0008 with ADR-055 and the column-name-free PredictionFrame #86 and S9 — Open a þing on target-scale and transform authority #93.
Depends on S1 — Supersede ADR-0007: the transform-prefix convention was retired platform-wide #85. Half supersedes, half survives —
pred_is still live in code.productionbranch in any of 33 reposIndependent of S1 — Supersede ADR-0007: the transform-prefix convention was retired platform-wide #85/S2 — Reconcile ADR-0008 with ADR-055 and the column-name-free PredictionFrame #86. The Contribution Guides are already right — do not "fix" them.
Phase 2 — Adjudicate the rest (fully parallel; each needs a human call)
needs-decision. Scopes the ADR only; migrating build systems is out of scope.Smallest story in the epic.
.githubcannot be renamed;docsviolates its own rule.needs-decision. Note the audit correction:ŷandỹare adopted; onlyỸis not.Phase 3 — Make staleness visible (strictly sequential)
ownerandreview_date, then promote the check to errorDepends on S1 — Supersede ADR-0007: the transform-prefix convention was retired platform-wide #85–S6 — Reconcile ADR-0009 with its actual partial adoption #90. Only assign accountability for records that survive. Ends with
check_adrs.pyat 0 warnings.Depends on S7 — Backfill owner and review_date, then promote the check from warning to error #91. The capstone. Must be tested against a reconstructed ADR-0007 case — a detector that would not have caught it is not done.
Parallel track — open early, runs long
Depends on S1 — Supersede ADR-0007: the transform-prefix convention was retired platform-wide #85.
blockedon seat-holders across five repositories. Open it early; do not let it gate Phases 1–3.Epic acceptance — verify before closing #84
Superseded bypointerownerandreview_date;check_adrs.pyreports 0 warnings and 0 errorsvalidate_docs.sh, and has a passing offline test./scripts/validate_docs.shexits 0python3 scripts/generate_adr_index.py --checkpassesgrep -c '_unassigned_' ADR/index.mdreturns 0Run after every story
./scripts/validate_docs.sh python3 scripts/generate_adr_index.py && python3 scripts/generate_adr_index.py --checkRegenerate
ADR/index.mdwhenever a status changes — it is generated, and CI checks it is current.Out of scope — do not pick these up here
internal_technical_guide.mdviews-platform/views-appwrite#26monthly_run_guide.mdviews-platform/views-models#387views-platform/views-pipeline-core#453ADR-0000cl. 2Issue #83 was closed
NOT_PLANNEDarguing that the[Internal Tech Guide]link should not be filled while its target describes a setup that hard-fails —views-modelstools/credentials/platform_env.shexits withFATAL: the Appwrite coordinate registry does not exist(lines 75, 114, 125, 149 onorigin/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-docsaudit, 2026-08-13 — 1 critical, 3 high, 5 medium, 2 low.Register:
reports/technical_risk_register.md(6 open, 4 resolved).