Base layer: the mesh as it is, under the mesh as it should be
HQ held only the to-be. Every reader had to already know the system the decisions were about, and an as-is claim had nowhere to live except inside an intention. Adds 02-DESIGN/00-as-is — eleven documents written from the implementation and the operational record, not from intent, including the parts nobody would choose again. The two existing designs move under 01-to-be. Layers are declared in frontmatter and never mix: a design that ships does not move, its as-is counterpart is written, and both stand. Back-fills adr/0001-0014 for decisions taken in implementation and never recorded — the broker, the module abstraction, the mesh database, managed files, provisioning, migrations, the workspace removal, failing loudly, the constitution, application placement, linking, the employee model, the artifact, the three silos. Each marked reconstructed, dated from the history, and citing the evidence it was recovered from. The two existing records renumber to 0015 and 0016 so the ledger runs oldest first; 0017 extends 0015 to modules outside the core, principle only — the domain list is deliberately not invented here. how-we-build.md becomes the source of the mesh constitution, with a sync playbook, so the enforced copy stops being the only one that is true. Process becomes explicit: five playbooks, eight thin skills that defer to them, a repository map, and AGENTS.md with CLAUDE.md as its include. The five Observations become 04-ISSUES 001-005 where they can be owned and closed. 006 is new and uncomfortable: HQ is not indexed into the knowledge base. That claim is what decision 27 rests on, it was never checked, and the README now says so instead of repeating it. Also corrects the ADR index into something generated, the "02-DESIGN is empty" claim, the VISION.md pointer that did not survive the repo split, and a note asserting the symlink rule was contradicted — it was a misreading; the rule forbids hand-made links, the installer links by design.
This commit is contained in:
@@ -1,3 +1,8 @@
|
||||
---
|
||||
effort: 001-module-domain-decomposition
|
||||
updated: 2026-08-22
|
||||
---
|
||||
|
||||
# Current state → ideal state
|
||||
|
||||
## 1. The count is a symptom
|
||||
@@ -232,6 +237,6 @@ returns. That mechanism is the subject of a separate ADR.
|
||||
pipeline resolves dependencies across the registry rather than the filesystem?
|
||||
4. **SDK residue** — after extraction, does `hal/sdk` keep transport (`amqp-client`), or
|
||||
does that belong to `hal/stream`? Everything imports it, which argues both ways.
|
||||
5. **Human agent modality.** ADR 0001 requires a fact the mesh does not record: which
|
||||
5. **Human agent modality.** ADR 0015 requires a fact the mesh does not record: which
|
||||
user, on which node, a human agent acts as. Where does it live — an attribute of the
|
||||
agent, or of the agent-node binding?
|
||||
|
||||
@@ -1,6 +1,12 @@
|
||||
---
|
||||
status: ongoing
|
||||
initiated: 2026-08-22
|
||||
touches: [02-DESIGN/00-as-is/02-modules-and-manifests.md, 02-DESIGN/00-as-is/10-module-catalogue.md, 02-DESIGN/01-to-be/00-work-breakdown.md]
|
||||
became: [adr/0015-mesh-brokers-nodes-host-agents-think.md]
|
||||
---
|
||||
|
||||
# 001 — Module domain decomposition
|
||||
|
||||
- **Status:** ONGOING — ADR 0001 accepted; graduates when `02-DESIGN` carries the per-context specifications
|
||||
- **Initiated by:** jochen, 2026-08-22
|
||||
- **Areas touched:** every `hal/*` and `noxflow/*` module; the pipeline's dependency
|
||||
graph; the knowledge base; agent identity and credentials.
|
||||
|
||||
@@ -1,3 +1,8 @@
|
||||
---
|
||||
effort: 002-local-mesh
|
||||
updated: 2026-08-22
|
||||
---
|
||||
|
||||
# A mesh that runs locally — current state and obstacles
|
||||
|
||||
Evidence for Phase 0. Every claim here is either a file location or something measured on
|
||||
@@ -231,7 +236,7 @@ over either way.
|
||||
a local-mesh implementation detail — if the answer is that the mesh should own
|
||||
supervision, Phase 0 should not build a container-only workaround first. Under
|
||||
investigation; findings will land in [`003-service-supervision`](../003-service-supervision/)
|
||||
and, if it goes ahead, ADR 0002.
|
||||
and, if it goes ahead, a decision record of its own.
|
||||
|
||||
2. **What replaces `~/.config/hal/env` and `/services/` inside a container?** A configurable
|
||||
root keeps one code path; container-specific targets keep the host paths untouched. This
|
||||
@@ -248,9 +253,9 @@ over either way.
|
||||
|
||||
## References
|
||||
|
||||
- [`adr/0001`](../../adr/0001-mesh-brokers-nodes-host-agents-think.md) — the decision this
|
||||
- [`adr/0001`](../../adr/0015-mesh-brokers-nodes-host-agents-think.md) — the decision this
|
||||
phase unblocks
|
||||
- [`02-DESIGN/00-work-breakdown.md`](../../02-DESIGN/00-work-breakdown.md) — Phase 0 tasks
|
||||
- [`02-DESIGN/00-work-breakdown.md`](../../02-DESIGN/01-to-be/00-work-breakdown.md) — Phase 0 tasks
|
||||
and checkpoint
|
||||
- `troubleshooting/provision-adoption-rotates-live-credential` — fixture B, root cause open
|
||||
- `troubleshooting/deploy-reports-transport-not-effect` — the nine defects that shipped
|
||||
|
||||
@@ -1,6 +1,12 @@
|
||||
---
|
||||
status: graduated
|
||||
initiated: 2026-08-22
|
||||
touches: [02-DESIGN/00-as-is/04-delivery.md, 02-DESIGN/00-as-is/05-runtime-and-installation.md]
|
||||
became: [02-DESIGN/01-to-be/01-end-to-end-testing.md, adr/0016-a-lab-node-is-a-virtual-machine.md]
|
||||
---
|
||||
|
||||
# 002 — A mesh that runs locally
|
||||
|
||||
- **Status:** GRADUATED — the design is [`02-DESIGN/01-end-to-end-testing.md`](../../02-DESIGN/01-end-to-end-testing.md)
|
||||
- **Initiated by:** jochen, 2026-08-22
|
||||
- **Areas touched:** `install.d/`, `hal/meshware`, `hal/coordinator`, `hal/brain`,
|
||||
`hal/developer` (`dev_up`), `hal/sdk` (env generation, feature handlers, artifact
|
||||
@@ -9,7 +15,7 @@
|
||||
|
||||
## Summary
|
||||
|
||||
Phase 0 of [`02-DESIGN/00-work-breakdown.md`](../../02-DESIGN/00-work-breakdown.md) requires
|
||||
Phase 0 of [`02-DESIGN/00-work-breakdown.md`](../../02-DESIGN/01-to-be/00-work-breakdown.md) requires
|
||||
a mesh that comes up in containers, runs its own pipeline, and reproduces known faults on
|
||||
demand. Nothing else in the decomposition starts until it exists, because every fault the
|
||||
decomposition addresses was found in production — there was nowhere else to find it.
|
||||
@@ -18,7 +24,7 @@ This effort establishes what already runs in a container, what is welded to the
|
||||
what it would take to close the gap. It does **not** choose an approach: the central
|
||||
question — how a containerised node executes a module service, when a module service is
|
||||
defined today as a systemd unit shelling to `docker compose` in `/services/` — is not
|
||||
answered by ADR 0001 and is recorded below rather than decided.
|
||||
answered by ADR 0015 and is recorded below rather than decided.
|
||||
|
||||
## What was established
|
||||
|
||||
|
||||
@@ -1,3 +1,8 @@
|
||||
---
|
||||
effort: 003-service-supervision
|
||||
updated: 2026-08-22
|
||||
---
|
||||
|
||||
# Who supervises a service — the cost of leaving systemd
|
||||
|
||||
Measured 2026-08-22. Every claim is a file location or a count.
|
||||
@@ -123,10 +128,10 @@ What it costs, honestly:
|
||||
|
||||
---
|
||||
|
||||
## 5. Why it cannot be all-or-nothing — and ADR 0001 already says so
|
||||
## 5. Why it cannot be all-or-nothing — and ADR 0015 already says so
|
||||
|
||||
Some of what runs under systemd today **cannot** be containerised, and the reason is
|
||||
already in the domain model. ADR 0001:
|
||||
already in the domain model. ADR 0015:
|
||||
|
||||
> a non-human agent acts through a spawned session — a human agent acts through a shell or
|
||||
> desktop
|
||||
@@ -203,7 +208,7 @@ found by grep.
|
||||
**This no longer gates Phase 0.** When this was written, the local mesh was assumed to be
|
||||
built from application containers, which forced the question — there is no natural way to
|
||||
run an init system inside one. The decision of 2026-08-22 to build development nodes as
|
||||
**system containers** (see [`02-DESIGN/01-end-to-end-testing.md`](../../02-DESIGN/01-end-to-end-testing.md))
|
||||
**system containers** (see [`02-DESIGN/01-end-to-end-testing.md`](../../02-DESIGN/01-to-be/01-end-to-end-testing.md))
|
||||
removes that pressure entirely: a system container runs a real init, so the existing model
|
||||
works unmodified and the lab needs no answer here to exist.
|
||||
|
||||
@@ -218,7 +223,7 @@ fate-sharing reason in §3.
|
||||
## References
|
||||
|
||||
- [`002-local-mesh`](../002-local-mesh/analysis.md) — the effort this came out of
|
||||
- [`adr/0001`](../../adr/0001-mesh-brokers-nodes-host-agents-think.md) — agent modality, which
|
||||
- [`adr/0001`](../../adr/0015-mesh-brokers-nodes-host-agents-think.md) — agent modality, which
|
||||
decides what cannot leave the host
|
||||
- `modules/hal/meshware/daemon/src/cerebellum.ts:815-828` — the self-restart workaround
|
||||
- `modules/hal/meshware/systemd/hal-module@.service` — the per-module Docker lifecycle
|
||||
|
||||
@@ -1,6 +1,12 @@
|
||||
---
|
||||
status: ongoing
|
||||
initiated: 2026-08-22
|
||||
touches: [02-DESIGN/00-as-is/05-runtime-and-installation.md]
|
||||
became: []
|
||||
---
|
||||
|
||||
# 003 — Who supervises a service
|
||||
|
||||
- **Status:** ONGOING — evidence gathered, options costed, decision open.
|
||||
**No longer blocks Phase 0** (see below).
|
||||
- **Initiated by:** jochen, 2026-08-22, in response to
|
||||
[`002-local-mesh`](../002-local-mesh/analysis.md) open question 1
|
||||
@@ -34,7 +40,7 @@ This effort answers the cost half. It does not choose.
|
||||
- **There is a third option neither of us named**, and it is the one that also solves Phase 0:
|
||||
run HAL's own daemons as containers, making Docker the supervisor for everything. Local and
|
||||
production then have the same shape rather than a translation layer between them.
|
||||
- **It cannot be all-or-nothing**, and ADR 0001 already says why: a human agent acts through a
|
||||
- **It cannot be all-or-nothing**, and ADR 0015 already says why: a human agent acts through a
|
||||
shell and a desktop. Those parts are on the host by definition.
|
||||
- One incidental finding: the automatic node rescue that documentation describes **does not
|
||||
exist**. No unit declares `OnFailure=`, and nothing calls `hal-rescue.sh` on a timer.
|
||||
@@ -43,5 +49,5 @@ Detail and costs in [`analysis.md`](analysis.md).
|
||||
|
||||
## Decision needed
|
||||
|
||||
Which supervision model the mesh adopts, recorded in ADR 0002 before Phase 0 builds
|
||||
Which supervision model the mesh adopts, recorded in a decision record before Phase 0 builds
|
||||
anything. The options and their costs are in `analysis.md` under "Options".
|
||||
|
||||
@@ -1,3 +1,8 @@
|
||||
---
|
||||
effort: 004-lab-network
|
||||
updated: 2026-08-22
|
||||
---
|
||||
|
||||
# Reproducing the mesh network in a lab
|
||||
|
||||
Established 2026-08-22 by reading the generating code and the live mesh DB. Every claim is a
|
||||
|
||||
@@ -1,6 +1,12 @@
|
||||
---
|
||||
status: ongoing
|
||||
initiated: 2026-08-22
|
||||
touches: [02-DESIGN/00-as-is/01-mesh-and-transport.md, 02-DESIGN/01-to-be/01-end-to-end-testing.md]
|
||||
became: [adr/0016-a-lab-node-is-a-virtual-machine.md]
|
||||
---
|
||||
|
||||
# 004 — Reproducing the mesh network in a lab
|
||||
|
||||
- **Status:** ONGOING — topology established and mapped; not yet stood up
|
||||
- **Initiated by:** jochen, 2026-08-22 — *"the most difficult part of our VM setup will be
|
||||
the networking part"*
|
||||
- **Areas touched:** `modules/wireguard`, `modules/dnsmasq-app`, `modules/traefik`,
|
||||
|
||||
+37
-7
@@ -4,13 +4,43 @@ Investigations that have not yet hardened into design.
|
||||
|
||||
## Structure
|
||||
|
||||
Each effort lives in `NNN-descriptive-name/` and **must** contain `status.md` with:
|
||||
Each effort lives in `NNN-descriptive-name/` and **must** contain `status.md`, carrying its
|
||||
state in YAML frontmatter and a prose summary below it:
|
||||
|
||||
- a short summary of the effort
|
||||
- who initiated it
|
||||
- the areas it touches
|
||||
- current status: `ONGOING`, `GRADUATED`, or `ABANDONED`
|
||||
```yaml
|
||||
---
|
||||
status: ongoing | graduated | abandoned
|
||||
initiated: YYYY-MM-DD
|
||||
touches: [] # design docs, subsystems or areas the effort bears on
|
||||
became: [] # required when status is terminal — what it turned into
|
||||
---
|
||||
```
|
||||
|
||||
An effort graduates by producing an ADR and a `02-DESIGN` entry. It is abandoned in
|
||||
place — never deleted. What was rejected, and why, is the more expensive half to
|
||||
The prose says what is being investigated, why, and what it touches. It does not restate the
|
||||
status — status lives in one place, and two places is one too many.
|
||||
|
||||
Further documents in the same folder hold the work itself: notes, evidence, option analyses,
|
||||
draft designs.
|
||||
|
||||
## Lifecycle
|
||||
|
||||
| status | Meaning |
|
||||
|---|---|
|
||||
| `ongoing` | Investigation in progress. |
|
||||
| `graduated` | Checked against `00-GENESIS`, decided in `adr/`, and specified in `02-DESIGN` — see `became:`. |
|
||||
| `abandoned` | Stopped or superseded. Nothing is deleted. |
|
||||
|
||||
An effort graduates by producing a decision record **and** a `02-DESIGN` entry. It is abandoned
|
||||
in place — never deleted. What was rejected, and why, is the more expensive half to
|
||||
rediscover.
|
||||
|
||||
Starting and closing efforts is playbook territory:
|
||||
[`00-GENESIS/process/01-research.md`](../00-GENESIS/process/01-research.md) and
|
||||
[`02-graduation.md`](../00-GENESIS/process/02-graduation.md).
|
||||
|
||||
## Rules
|
||||
|
||||
- Markdown only. Do not skip or reuse a sequence number.
|
||||
- **Evidence, not assertion.** An effort that measured nothing has not finished.
|
||||
- Research describes real observations but **never identifies the mesh it observed**. The shape
|
||||
of a finding survives anonymisation intact.
|
||||
|
||||
Reference in New Issue
Block a user