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

Say rollout, not walk, for the sending of a batch across nodes (issue 646)

Browse Source
This commit is contained in:
jschoubben
2026-10-15 19:57:20 +02:00
parent 99a9da0950
commit 437523554e
82 changed files with 561 additions and 561 deletions
Download Patch File Download Diff File Expand all files Collapse all files
README.md
+1 -1
View File
@@ -14,7 +14,7 @@ and why. Today that is almost entirely **Novox Mesh**, the foundation everything
| [`04-ISSUES`](04-ISSUES/) | The front door for "something is wrong" at the level of design or governance. |
**The numbering is the flow.** Research produces a decision; the decision authorises a design.
That is why decisions are `02` and design is `03` — a reader following the numbers walks the
That is why decisions are `02` and design is `03` — a reader following the numbers rollouts the
process in the order it happens. The research efforts and decision records themselves live in the knowledge
base, the seat `knowledge-base`, read and written through the mesh MCP server from any node (ADR 0290).