Compose as the controller does, so a node's shadow can answer same (issue 1126, group fix/1126-seed-same)

Conversation 1 Commits 3 Files Changed 18

+808 -26

3 Commits

Author	SHA1	Message	Date
jschoubben	3028c7ec4e	A drifted own secret is read from a resource id as a node runs it, its module's name first (only-office.needs-jwt), so the node agent finds what to hand the vault (issue 1126, cause C4; review round 2) mesh/delivery merged: source.main moved to novox/mesh-sdk@79eb58efe4b0 Details mesh/delivery-group group fix/1126-seed-same merged: every member is merged Details mesh/check failed: integration: github.com/novox/mesh-host/cmd/mesh-host.TestNatsANodeThePlacementNamesComposesAndAppliesItsOwn: the node did not comp… delivery.OwnNeedName reads <module>.needs-<name> and the bare needs-<name>; OwnValuesDiffer and the node agent use it. The fixtures carry the id shape captured from novox's shadow answer.	2026-10-28 10:00:29 +01:00
jschoubben	1062b33d32	A node's shadow answer counts the values that drifted from the vault's, and names the own secrets among them (issue 1126, cause C4) delivery.OwnValuesDiffer, ValuesDiffer and WithValuesDiffer read the shown bodies masked as another value; a candidate answer carries values_differ. The node agent hands the vault those own secrets' running values through move-in's replace_running, so no seat verb and no bus grant changes here.	2026-10-28 09:49:03 +01:00
jschoubben	16b8d8a1ee	Compose as the controller does, so a node's shadow can answer same (issue 1126, C1 C2 C3 C5 C6, T1) Seals are reused and compared by slot (resource, field), never across resources; one rule says which resolved config values are laid; a seat path that steps back is owned by the seat it steps back for, whatever the seat order; a folded module of an old-form build is composed from what runs of it; the operator export's file is carried as it runs; a differing resource names its differing JSON paths, found before its bodies are cut, and an answer is fitted to the node's key.	2026-10-28 09:36:36 +01:00

Author

SHA1

Message

Date

jschoubben

3028c7ec4e

A drifted own secret is read from a resource id as a node runs it, its module's name first (only-office.needs-jwt), so the node agent finds what to hand the vault (issue 1126, cause C4; review round 2)

mesh/delivery merged: source.main moved to novox/mesh-sdk@79eb58efe4b0

Details

mesh/delivery-group group fix/1126-seed-same merged: every member is merged

Details

mesh/check failed: integration: github.com/novox/mesh-host/cmd/mesh-host.TestNatsANodeThePlacementNamesComposesAndAppliesItsOwn: the node did not comp…

delivery.OwnNeedName reads <module>.needs-<name> and the bare needs-<name>; OwnValuesDiffer and the node agent use it.
The fixtures carry the id shape captured from novox's shadow answer.

2026-10-28 10:00:29 +01:00

jschoubben

1062b33d32

A node's shadow answer counts the values that drifted from the vault's, and names the own secrets among them (issue 1126, cause C4)

delivery.OwnValuesDiffer, ValuesDiffer and WithValuesDiffer read the shown bodies masked as another value; a candidate
answer carries values_differ. The node agent hands the vault those own secrets' running values through move-in's
replace_running, so no seat verb and no bus grant changes here.

2026-10-28 09:49:03 +01:00

jschoubben

16b8d8a1ee

Compose as the controller does, so a node's shadow can answer same (issue 1126, C1 C2 C3 C5 C6, T1)

Seals are reused and compared by slot (resource, field), never across resources;
one rule says which resolved config values are laid; a seat path that steps back
is owned by the seat it steps back for, whatever the seat order; a folded module
of an old-form build is composed from what runs of it; the operator export's file
is carried as it runs; a differing resource names its differing JSON paths, found
before its bodies are cut, and an answer is fitted to the node's key.

2026-10-28 09:36:36 +01:00

Compose as the controller does, so a node's shadow can answer same (issue 1126, group fix/1126-seed-same) #114