jschoubben
f05e4a0dce
Research efforts move from status.md to 00-overview.md with active / graduated / abandoned, matching papa-hq so the two repositories read the same way. Playbooks, skills, README and the ledger follow. Reverses yesterday's withdrawal of the symlink note in GENESIS. The note was right and the withdrawal was wrong: the intent is that the mesh creates no symlinks at all, so a founding document listing "symlinks, not copies" as a design principle does point the opposite way from where this is going, and that is a contradiction rather than a stale detail. ADR 0018 records the position, proposed. ADR 0011 stays as it is — it is the historical decision and the incident behind it is why anyone believes either record — and is superseded in intent, not edited. Its one editorial line, which called the wider reading false, is corrected to state what is actually true: centralising who may link narrowed the incident class without closing it, because a link the installer makes resolves exactly like one made by hand. The argument that kept linking was staleness. ADR 0004 removed it: every managed file is already derived and reconciled, so a copy is the natural form and a pointer into source is the shape the mesh's own model forbids everywhere else. What is not settled, and is marked open, is how staleness gets detected — which is the decision that makes or breaks it.
60 lines
2.9 KiB
Markdown
60 lines
2.9 KiB
Markdown
---
|
|
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
|
|
|
|
- **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
|
|
manager), `test/pipeline/`, `test/dev-mesh/`, the provisioning path in
|
|
`modules/postgres/`.
|
|
|
|
## Summary
|
|
|
|
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.
|
|
|
|
This effort establishes what already runs in a container, what is welded to the host, and
|
|
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 0015 and is recorded below rather than decided.
|
|
|
|
## What was established
|
|
|
|
- The two existing container harnesses are **neither of them a mesh**, and one of them has
|
|
not been able to build since 2026-06-04.
|
|
- Node identity is already portable — a single environment variable, no host handshake.
|
|
- Four concrete host couplings block a containerised node, all with known locations.
|
|
- All three Phase 0 fixtures are reproducible; one of them is documented in the knowledge
|
|
base with an open root cause and is the cheapest place to start.
|
|
|
|
Detail and evidence in [`analysis.md`](analysis.md).
|
|
|
|
## Questions — all settled 2026-08-22
|
|
|
|
**Phase 0 is a development environment**, not a fixture rig — it is what the host-borrowing
|
|
dev tooling becomes.
|
|
|
|
**The trigger is a real source-forge container**, because the webhook relay is part of what
|
|
is under test.
|
|
|
|
**A node is a system container**, promotable to a virtual machine per node. This answered
|
|
the question the effort was stuck on, and dissolved it rather than solving it: against a
|
|
real node with a real init, the four host couplings catalogued in `analysis.md` §3 are not
|
|
couplings — they are how a node works. They were obstacles only to a node modelled as an
|
|
application container.
|
|
|
|
Consequently [`003-service-supervision`](../003-service-supervision/) **no longer blocks
|
|
Phase 0**. It remains a live architecture question, on its own timeline.
|
|
|
|
The remaining questions in `analysis.md` — what replaces host paths in a container, and how
|
|
faithful the lab must be — are answered in the design: nothing replaces them, because the
|
|
paths are real; and the divergences are enumerated rather than discovered.
|