mesh-grants places modules by the node-engines' haves while the assigner's assignments view does not answer (issue 1966, bootstrap recovery)

Conversation 1 Commits 3 Files Changed 3

+251 -14

3 Commits

Author	SHA1	Message	Date
jschoubben	69b6b89af5	mesh-grants: the bootstrap row proves a removed have places nothing mesh/delivery merged: source.main moved to novox/mesh-delivery@dcc48b82d0cb Details Review round 1 of issue 1966's fix: the membership check alone did not pin the removed phase; the row now reads the inputs and requires mod-y off b while its have is removed. Claude-Session: https://claude.ai/code/session_01NcbgfFfQ4Z9UE5jK32PmE5	2026-11-07 22:51:35 +01:00
jschoubben	ffaff3d3aa	mesh-grants: prove the haves fallback lets the indexer serve the seat list's verb Issue 1966: the seat list is read through mesh-catalog's seat-definitions, which got no responders only because nothing was placed. A row shows that, the assignments view unanswered, the indexer placed by its have (its real manifest) is composed to hear mesh.seat.mesh-catalog.* and its membership serving seat-definitions is published, while the seat list stays unread and other modules still wait for it. Claude-Session: https://claude.ai/code/session_01NcbgfFfQ4Z9UE5jK32PmE5	2026-11-07 22:40:31 +01:00
jschoubben	9756dd6f1f	mesh-grants: place by the node-engines' haves while the assignments view does not answer Bootstrap only (issue 1966, notes 63 and 64; the operator chose it 2026-11-07 22:19, bending ADR 0567 §9 for the bootstrap). An assigner that serves no first views answers no assignments, so the grants part placed nothing and wrote no grant, membership or bucket for anything, not even for the assigner that would serve the view. When the assignments read fails and the haves read, each module is placed on the node whose have says it runs (any phase but removed), the bus node found among them, and what runs composed from each have's fingerprint instead of the assigner's wants. Said as a gap naming the fallback, and kept as Inputs.ByHaves: such a pass retires no account and deletes no withheld hearing (ReadFailures), and seals no list that drops a user of the list in force or of the loaded list (holdsBack). Once the view answers, the fallback is unused. Quick fix; the thorough one stays the module-graph edge (the assigner's views before the grants part that reads them) in the delivery plan. Claude-Session: https://claude.ai/code/session_01NcbgfFfQ4Z9UE5jK32PmE5	2026-11-07 22:37:56 +01:00

Author

SHA1

Message

Date

jschoubben

69b6b89af5

mesh-grants: the bootstrap row proves a removed have places nothing

mesh/delivery merged: source.main moved to novox/mesh-delivery@dcc48b82d0cb

Details

Review round 1 of issue 1966's fix: the membership check alone did not pin the removed
phase; the row now reads the inputs and requires mod-y off b while its have is removed.

Claude-Session: https://claude.ai/code/session_01NcbgfFfQ4Z9UE5jK32PmE5

2026-11-07 22:51:35 +01:00

jschoubben

ffaff3d3aa

mesh-grants: prove the haves fallback lets the indexer serve the seat list's verb

Issue 1966: the seat list is read through mesh-catalog's seat-definitions, which got no
responders only because nothing was placed. A row shows that, the assignments view
unanswered, the indexer placed by its have (its real manifest) is composed to hear
mesh.seat.mesh-catalog.* and its membership serving seat-definitions is published, while
the seat list stays unread and other modules still wait for it.

Claude-Session: https://claude.ai/code/session_01NcbgfFfQ4Z9UE5jK32PmE5

2026-11-07 22:40:31 +01:00

jschoubben

9756dd6f1f

mesh-grants: place by the node-engines' haves while the assignments view does not answer

Bootstrap only (issue 1966, notes 63 and 64; the operator chose it 2026-11-07 22:19,
bending ADR 0567 §9 for the bootstrap). An assigner that serves no first views answers
no assignments, so the grants part placed nothing and wrote no grant, membership or
bucket for anything, not even for the assigner that would serve the view.

When the assignments read fails and the haves read, each module is placed on the node
whose have says it runs (any phase but removed), the bus node found among them, and what
runs composed from each have's fingerprint instead of the assigner's wants. Said as a gap
naming the fallback, and kept as Inputs.ByHaves: such a pass retires no account and deletes
no withheld hearing (ReadFailures), and seals no list that drops a user of the list in
force or of the loaded list (holdsBack). Once the view answers, the fallback is unused.

Quick fix; the thorough one stays the module-graph edge (the assigner's views before the
grants part that reads them) in the delivery plan.

Claude-Session: https://claude.ai/code/session_01NcbgfFfQ4Z9UE5jK32PmE5

2026-11-07 22:37:56 +01:00

mesh-grants places modules by the node-engines' haves while the assigner's assignments view does not answer (issue 1966, bootstrap recovery) #170