jschoubben
87f4f29cc6
ADR 0027 — the product is Novox Mesh, shortened to mesh internally. HAL was never chosen: it arrived with the dotfiles repository this grew out of, it is borrowed, and it is borrowed from the canonical untrustworthy machine intelligence, which is an odd flag for infrastructure trusted with credentials. Timing is the substance of the decision, not an aside — the skeleton is not built, so renaming costs a search and replace now and a migration later. Nox is an identity of Novox, and specifically the agent of the MESH rather than of a node. Nodes keep their own identities. Nox addresses them, and a human mostly talks to Nox — which makes it the concrete form of the mission's vision: state an intent, and the mesh works out which node holds the thing. It holds no private channel. The gap this opens is recorded: ADR 0012 binds every agent to a home node, and a mesh-scoped agent has none, so the model needs extending. ADR 0028 — HQ is company-scoped, novox/hq, with the mesh as its first product. Checked rather than assumed: the company organisation already holds live projects that the mesh builds and deploys, so they are tenants rather than peers, and the mesh is the ground they stand on. There is also company work outside the mesh already, which strengthens the case and means the eventual split is closer than "some day" — so each document's scope is fixed now, in a table, making that split mechanical instead of archaeological. The folders are deliberately not restructured yet. The skeleton takes the new vocabulary: mesh-host, mesh-substrate, mesh-control, mesh-surfaces, mesh-catalog. Substrate drops to four services now that identity is a hosted workload rather than a dependency. Research 009 opens the migration, with the reframing that lowers its risk: replace the control plane, do not move the workloads. Their data never moves, so it is re-declared rather than adopted — which keeps adoption out of scope, as the lab design requires. Self-hosting is the last phase, or a failed cutover takes away the means to fix it.
2.4 KiB
status, opened, located-in, fixed-by, amended-design
| status | opened | located-in | fixed-by | amended-design | ||
|---|---|---|---|---|---|---|
| open | 2026-08-23 |
|
006 — This repository is not indexed into the knowledge base, and the claim that it is holds up a decision
Symptom
README.md states, as the answer to the objection against creating this
repository:
These documents are still indexed into the knowledge base, so
recall_searchreturns them beside everything else. One source, many surfaces — which was always the actual requirement.
Searching the knowledge base for this repository's content returns nothing.
Evidence
Verified 2026-08-23, two searches against the mesh's operational memory:
| Query | Result |
|---|---|
| The full title of a decision record in this repository | No results |
| A distinctive phrase from the decision ledger | No results |
No entry, no partial match, no stale copy. The indexing does not exist and appears never to have existed.
Why this is an issue and not a task
The claim is load-bearing. Decision 27 separates HQ into its own repository, and the objection it answers was that a fourth knowledge system repeats the mistake the mesh's knowledge consolidation was created to fix. The recorded answer is "indexing, not location" — that the split is safe because these documents remain searchable alongside everything else.
Without the indexing, the objection stands unanswered and this repository is precisely the fourth knowledge system it was argued not to be. Either the indexing is built, or decision 27's reasoning is amended to something that is true.
It is also, exactly, the failure this repository names in its own rules: a document stating a rule about the mesh must say how the rule is checked. This one stated a mechanism and nobody checked it — including in the same commit that wrote the rule.
Open questions
- Where would the indexing run? The operational memory is written through a mesh capability; is this a periodic sync of a repository into it, or a search surface that reads the repository directly?
- Which store — the flat symptom-indexed memory, the structured archive, or both? They have
different lifecycles (
03-DESIGN/00-as-is/07-knowledge.md), and this content is governed rather than incidental. - Public repository, private mesh: the sync direction must not become a path for mesh-specific content to arrive into these documents.