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

ADR 0152: the operator's surface is a module, the console

Browse Source 
The work order's group-3 question answered: an ordinary module the mesh assigns to the machine a
person sits at, holding a minted credential, calling tools under a manifest grant (invokes), serving
MCP on loopback. Design 34; pointers in 33, 25 and 0095; module check designed into 12 (issue 148);
README stops claiming an indexing nothing provides (issue 006).
This commit is contained in:
jschoubben
2026-09-30 16:08:52 +02:00
parent 0cf1ad5dad
commit ad4a5ea004
12 changed files with 397 additions and 11 deletions
Download Patch File Download Diff File Expand all files Collapse all files
README.md
+9 -6
View File
@@ -87,12 +87,15 @@ rather than location** — that these documents would be indexed into the knowle
symptom search returns them beside everything else. One source, many surfaces. Where the source
is authored is then a separate question.
**That indexing does not exist.** It was checked on 2026-08-23 and returns nothing; it appears
never to have existed. Until it does, the objection stands unanswered and this repository is
the fourth knowledge system it was argued not to be. Recorded as
[`04-ISSUES/006`](04-ISSUES/006-hq-is-not-indexed-into-the-knowledge-base/00-report.md), and
left standing here rather than quietly reworded, because a claim that held up a decision and
was never checked is precisely the failure this repository exists to name.
**That indexing never existed, and the store it would have indexed into is gone.** It was checked
on 2026-08-23 and returned nothing; the knowledge base it named was the predecessor's, and since the
mesh moved to its own bus on 2026-09-28 nothing can reach it at all. The claim is recorded as
[`04-ISSUES/006`](04-ISSUES/006-hq-is-not-indexed-into-the-knowledge-base/00-report.md) and answered
by [ADR 0025](02-DECISIONS/0025-the-design-record-is-read-not-copied.md): these documents are
**read, not copied** — an agent reads this repository and a search consults it — and that agent is
not built. So today this repository is reachable by whoever knows to open it and surfaces to nobody
else. Said here rather than quietly reworded, because a claim that held up a decision and was never
checked is precisely the failure this repository exists to name.
Answered separately, a repository of its own is the better home: