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

Take in round 1 of design 47's G review: hear what nodes run, say what the forge is owed, reach the forge by its seat

Browse Source 
The reviewers found a seat's pass waiting on a call to a node that may be away, acts owed to the forge
that could be lost or done twice, a seat git that missed the gate's and half the parts' forge calls and
events, a merge that still judged a check the operator removed, and waits with no bound or condition.
The design now keeps what each node runs from its running events, makes every owed act safe to repeat
with its outcome said and recorded, gives the seat git every call and event with its act verbs granted
by the holder's callers, orders forge, bridge and gate with a way back, adds module-held and
check-could-not-run, numbers tests 56 to 60, and says how the store seat's holder takes its own build.

Claude-Session: https://claude.ai/code/session_01NcbgfFfQ4Z9UE5jK32PmE5
This commit is contained in:
jschoubben
2026-11-09 19:21:49 +01:00
parent 7f2f37d9e6
commit 2fd96e1e4e
3 changed files with 264 additions and 107 deletions
Download Patch File Download Diff File Expand all files Collapse all files
00-META/glossary.md
+4 -3
View File
@@ -813,9 +813,10 @@ controller (the planner, the rollout) until release 6 of ADR 0429; from each rel
- **git seat** — the seat `git`, held once for the mesh, delivering the provision `git`: the
repositories a build comes from ([26 — The seats](../03-DESIGN/01-to-be/26-the-seats.md) *The git seat*). A seat of
this domain, defined in `mesh-delivery-contracts`. From research 085's milestone its verbs are the one way a
delivery part reaches the forge: reads (`pull`, `open-pulls`, `tags`, `trees`, `file`, `commits`, `branches`,
`contains`) for the parts that declare them, and acts (`status`, `comment`, `view`, `note`, `merge-pull`) for the
forge bridge alone (design 47, *The verbs*). Not the **forge** itself, the server, nor the forge module's own tools.
delivery part and the gate reach the forge: reads (`pull`, `open-pulls`, `tags`, `trees`, `file`, `contains`,
`statuses`) for the parts that declare them, acts (`status`, `comment`, `view`, `note`, `merge-pull`) for the forge
bridge alone, as the holder's trusted value `callers` names, and the forge's events (`pull.*`, `forge.*`,
`repo.writable`) as the seat's (design 47, *The verbs*). Not the **forge** itself, the server, nor the forge module's own tools.
## Health and repair — what is wrong, and putting it right