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

Research 045: the knowledge base holds no counter of its own, and the cleanup is in review
mesh/merge-gate pass: the change touches no module of the mesh's graph
Details
mesh/repo-check pass: its merge-check.sh passed
Details
mesh/delivery delivered
Details

Browse Source
This commit is contained in:
jschoubben
2026-10-11 00:53:27 +02:00
parent 9631b17d16
commit e41fd0de1d
1 changed files with 7 additions and 8 deletions
Download Patch File Download Diff File Expand all files Collapse all files
01-RESEARCH/045-a-knowledge-base-the-mesh-writes/01-findings.md
+7 -8
View File
@@ -118,7 +118,7 @@ with a text description an agent reads. They are a later slice (section 10) and
The 16 concurrent collisions all come from reading the next number off a repository that many branches write
at once. The issue tracker hands out numbers by compare-and-set on a counter key
([to-be 53](../../03-DESIGN/01-to-be/53-the-issue-tracker.md) §4); the knowledge base does the same.
([to-be 53](../../03-DESIGN/01-to-be/53-the-issue-tracker.md) §4); the knowledge base asks it for every number.
- **One sequence per kind**: decision, research, and later design. Numbers keep their meaning in conversation
("ADR 0276").
@@ -243,12 +243,12 @@ decision record.
## 10. Slices
1. **Clean the input** (this repository, one pull request): repair the loose links of section 7, so the import
reads clean records. Done in the pull request that declares every partial supersession in both records
and adds the `partial-supersession` check. Beside it, a shared instruction section proposed for every session: take a decision
or research number from the counter once it exists, name a partial supersession in a field, never only in
prose.
reads clean records. In review as hq pull request 305, which declares every partial supersession in both
records and adds the `partial-supersession` check. Beside it, a shared instruction section for every
session: take a decision or research number above every one on `main` and on open branches until the
counter exists, and name a partial supersession in a field, never only in prose.
2. **The knowledge base, decisions and research**: a Go module serving one seat held once for the mesh, on
the control-node beside the issue tracker. The counters, the import, the rules and links, and the answers:
the control-node beside the issue tracker. The import, the rules and links, and the answers; numbers come from the issue tracker (section 3):
| Verb | Answers |
|---|---|
@@ -260,8 +260,7 @@ decision record.
| `import` | this repository's decisions and research at a commit, repeatable |
Storage is a database in the store, provided to the module: the structure is small, but `ask` needs ranked
full-text search, which the store's server does and a bucket does not. The counters stay bucket keys with
compare-and-set, as the tracker's. Every answer is bounded in size.
full-text search, which the store's server does and a bucket does not. Every answer is bounded in size.
3. **Frontmatter leaves this repository**, kind by kind, once the import is proven equal.
4. **Issues whole in the tracker** (section 9): documents, import, links rewritten, folders removed.
5. **Designs, playbooks and glossary entries** into the knowledge base the same way.