novox/hq
3
0
Fork 0
Code Issues 4 Pull Requests 5 Releases Wiki Activity

Order the records the way the system is learned

Browse Source 
Jochen asked whether the order made sense. It did not -- it followed when
things happened to be decided, which after consolidation is fictional anyway
since record 5 alone folds decisions taken across a week.

Concretely wrong before: the domain statement sat at 8, after five engineering
rules; the constitution was scattered across 5, 12 and 17; the tiers landed at
15, 16, 21 and 22 with process records in between.

Now it walks: what the mesh is (1-3), its tiers from the bottom up (4-8), what
runs on them and how it gets there (9-10), how it is built (11-16), how it is
checked (17-18), how we work (19-23).

Two things made this safe rather than free. It is a permutation, not a
compaction, so the renames go through temporary names -- otherwise two files
want one slot and one is lost. And the reference rewrite is a single
simultaneous pass, because almost every number moved into a slot another number
was vacating; replacing one at a time would have cascaded and pointed things at
the wrong record while still resolving.

Verified: 284 [ADR NNNN](path) links across the repository, all with matching
text and target.

The ordering principle is now stated in 19 rather than left implicit -- the
repository already said "the numbering is the flow" about its folders, and
there was no reason for the records to be the exception.
This commit is contained in:
jschoubben
2026-08-28 23:30:42 +02:00
parent e1febe8e0f
commit 333356cff3
85 changed files with 471 additions and 465 deletions
Download Patch File Download Diff File Expand all files Collapse all files
04-ISSUES/001-failed-package-install-reports-success/00-report.md
+2 -2
View File
@@ -31,14 +31,14 @@ exists to catch — a step that failed, reported success, and left the next step
state that was never produced.
It is also a direct violation of a decision already taken and recorded:
[ADR 0023](../../02-DECISIONS/0023-delivery.md) says a step that fails must fail the
[ADR 0010](../../02-DECISIONS/0010-delivery.md) says a step that fails must fail the
job. That record notes the rule is applied instance by instance and enforced by no mechanism.
This is an instance where it was never applied.
## Evidence
- Observed 2026-08-22 while declaring the virtualisation package required by
[ADR 0009](../../02-DECISIONS/0009-the-lab.md).
[ADR 0016](../../02-DECISIONS/0016-the-lab.md).
- A fix is written and open as a pull request, unmerged since 2026-08-20.
## Open questions