jschoubben
e1febe8e0f
The consolidation left a sparse sequence -- 1, 4, 6, 7, 9, 10, 12, 15, 16, 18, 19, 25, 34, 35, 36, 37, 40, 42, 44, 45, 48, 49, 58 -- where the gaps were only the archaeology of what used to be there. Renumbered contiguously. Renames run in ascending order, so every target number is already free and no two files ever collide. The reference rewrite is one simultaneous pass rather than a sequence of replacements. Numbers moved into slots other numbers were vacating -- the node host went 37 to 16 while the lab went 16 to 9 -- so replacing one at a time would have cascaded and silently pointed things at the wrong record. Seven plain-text references survived the merges as prose rather than links, naming records that no longer existed: the enrolment token, the link boundary, what a declaration is, reachability, the repository structure. Each mapped to the consolidated record that now holds it. Verified rather than assumed: every [ADR NNNN](path) link now has matching text and target, checked across the whole repository, and the checker passes. Frontmatter `consolidates:` lists dropped -- they named records that are gone, and each consolidated record already says in prose what it absorbed.
3.0 KiB
3.0 KiB
status, initiated, touches, became
| status | initiated | touches | became | ||||
|---|---|---|---|---|---|---|---|
| active | 2026-08-22 |
|
|
001 — Module domain decomposition
- Initiated by: jochen, 2026-08-22
- Areas touched: every
hal/*andnoxflow/*module; the pipeline's dependency graph; the knowledge base; agent identity and credentials.
Summary
HAL has 124 modules. That number is not a maintenance problem in itself — it is the symptom of missing bounded contexts. Modules are split not because they model different domains, but because splitting is the only lever the platform offers:
- no way to run one daemon on one node without making it a module
(
hal/claude-licences— one daemon, single-node) - no way to expose two of a kind from one module
- no namespace separating the mesh from the software it runs
This effort establishes the current state, the ideal state, and the sequence between them.
Trigger
A night of debugging that produced four fixes and one conclusion. Every fault was a boundary fault:
- Per-agent Claude credentials had to be written by the noxflow runtime, because
agents.claude_accountis in noxflow's database — even though agent identity is a mesh concept and node identity already lives in the mesh registry. - Whether
hal/brainmay depend on noxflow took three attempts to answer, twice wrongly, because the ownership boundary was never stated. - Authoritative documentation existed in
mesh_docsand was not found, while a proposal in repo markdown was invisible to search entirely.
Decisions taken (2026-08-22)
| Question | Decision |
|---|---|
| What should noxflow become? | Decompose into hal/* modules; noxflow returns to tasks/workflows |
| Who owns agent identity? | hal/agents — a mesh concept, alongside nodes |
| Where do third-party apps live? | Out of this repo. They run on the mesh; they are not of it |
| Knowledge structure | Modelled on papa-hq; implementation choice left open |
Open questions
Tracked in analysis.md under "Open questions".
Deliberately not decided
Recorded so they are not mistaken for oversights. Each is open, and each comes out of
ADR 0008; this effort stays
active until they are answered.
| Question | Status |
|---|---|
hal/scheduler — infrastructure, or part of the work context. |
Open. |
| Which context owns the executor. | Open. |
| Catalogue destination — one repository or many. | Open. Phase 4. |
| What the shared library keeps after extraction. | Open. Phase 3. |
| Where human agent modality is recorded — which user, on which node, a human agent acts as. | Open. Required by the model; not yet stored. |
| Which domains the modules outside the platform core group into. | Open, from ADR 0019, which settles the principle and deliberately not the list. |