jochen
feeea127e2
Issues 203–205: what the first node-tools rollout found — an unissued credential pushed, a stale declaration during a controller handover, a package resource against a stale database
2026-10-02 23:47:12 +02:00
mesh-admin
5938d40dee
Merge pull request 'ADRs 0164–0166 and issue 190: the container runtime gets a module, a seat and declared settings' ( #271 ) from decision/docker-module into main
2026-10-02 20:14:58 +00:00
jschoubben
e4a0c73e2b
Merge remote-tracking branch 'origin/main' into issues/192-193-console-registration-and-store-query
2026-10-02 22:14:24 +02:00
jschoubben
d1aeee42a4
Regenerate the decision index after merging main
2026-10-02 22:14:21 +02:00
jschoubben
131a5e4714
Issue 201: what was established about the race while closing the outage half
2026-10-02 18:19:12 +02:00
jschoubben
329a24fdae
ADRs 0184 and 0185: a service is still running a moment later; a control plane behind its row serves what it can; issue 201 half closed
2026-10-02 18:16:24 +02:00
jschoubben
d0d5799884
Issue 201: a push recreated the controller at a digest older than the seat row its successor wrote
2026-10-02 17:15:22 +02:00
jschoubben
98eb3aa76f
ADR 0169 → 0170: the firewall seat's record renumbered after a collision on main; its built note; cycle.py refuses two records sharing a number
...
Another session's 0169 landed first. The collision check from issue 155
covered issue folders only; it covers decision records now, and would have
refused this.
2026-10-02 14:51:22 +02:00
jschoubben
0e7b85f184
Issues 199 (resolved: a node-scoped seat's verb through the console) and 200 (the controller's answer to a long console call is refused by the bus)
2026-10-02 14:25:03 +02:00
jschoubben
17ca9a262b
0164: a setting names the file it lands in (issue 198's leak between one module's files); 190 notes the fourth machine now has the resolver
2026-10-02 12:23:28 +02:00
jschoubben
967c793eaa
Merge remote-tracking branch 'origin/main' into decision/docker-module
2026-10-02 12:23:27 +02:00
mesh-admin
78351560f7
Merge pull request 'Issue 198: the home network's DNS server ran outside the mesh, and its filter closed it' ( #283 ) from jschoubben/the-lans-dns-is-the-mesh into main
2026-10-02 10:22:51 +00:00
jschoubben
426f741ad0
Issue 198: the home network's DNS server ran outside the mesh, and its filter closed it
2026-10-02 12:22:31 +02:00
jschoubben
9bed54d3be
Issue 197 resolved: the wired port is guarded before it is plugged in
2026-10-02 12:22:15 +02:00
jschoubben
413daf8ad5
Issue 197: a physical link that is down is not filtered when it comes up
2026-10-02 12:22:15 +02:00
jschoubben
7c3be48db2
Issues 143 and 144 resolved: the live row of ADR 0168 read on the home server and the control node
2026-10-02 12:11:17 +02:00
jschoubben
1bd13446d4
ADR 0168: a converged machine is filtered by the mesh alone, and the host says what else refuses (group 7)
...
Designs 08 and 05 revised; 141 resolved by ADR 0140 and 084 by ADR 0102 and
issue 128, both by reading; 143 and 144 decided, built on the matching
branches in mesh-host and mesh-controller, resolved when the home server's
record names the predecessor's chain.
2026-10-02 11:58:18 +02:00
jschoubben
bd6c55d225
Group 6 closed: 086, 090, 098, 099, 100, 101 resolved on the operator's decision, each saying the live row was not run
2026-10-02 11:37:08 +02:00
jschoubben
c8935aceca
Issue 194 resolved: the fixed host forgot its former archive on all four machines
2026-10-02 11:31:29 +02:00
jschoubben
d05ac367f1
Issue 196 resolved: the hub relays the mesh, re-swept live
2026-10-02 11:23:37 +02:00
jschoubben
1c0dafb918
Issue 196: the hub relays the mesh only on the ports it publishes itself
2026-10-02 11:17:11 +02:00
mesh-admin
018ee359ae
Merge pull request 'Issue 194: the host's own former archive stops every machine applying anything' ( #274 ) from issue/194-the-hosts-own-former-archive-stops-every-apply into main
2026-10-02 09:04:30 +00:00
mesh-admin
c5535eeebd
Merge pull request 'ADR 0163 built: the take digest, the minted-secret refusal, the networks setting, settings judged where stored, genesis raising the forge as declared' ( #270 ) from feat/a-take-is-a-comparison-the-rest into main
2026-10-02 09:04:21 +00:00
jschoubben
28d53dcc28
Issue 191 resolved: internal-only routes are served to the mesh, live on both proxies
2026-10-02 09:49:25 +02:00
jschoubben
df667eb710
ADR 0167: a membership carries what its module receives, and who the mesh is
...
Issue 191's route proxy needs to know who the mesh is to serve an
internal name correctly, and the first fix had it work that out alone.
The membership on the bus now carries it, from the same list the filter
uses. ADR 0138 gains an insight that the proxy is where internal reach
is kept; designs 08 and 25 say how.
2026-10-02 09:49:19 +02:00
jschoubben
098a2ca485
Issue 191: a route with only an internal name is dropped as naming nothing
2026-10-02 09:49:19 +02:00
jschoubben
db5ff5a5ee
Issue 195: every assigned module is counted as a bus user without a credential
...
The status warning names 49 users; 48 are modules that never speak on the
bus, and the one real fault, a declared broker secret filled with a
generated value, looked the same as the rest.
2026-10-02 02:44:24 +02:00
jschoubben
780c2b6e58
Issue 194: the host's own former archive stops every machine applying anything
...
Rule 5 of ADR 0163 (a former target is removed) met issue 162 (an archive
has no removal) in the host's own archive, the first time a host carrying
former targets replaced itself; every machine applied nothing from then on.
2026-10-02 02:42:19 +02:00
jschoubben
27c1db8a86
Review of 0164-0166 and 190: the mesh's own setting words stay settable; changing runtime verbs are not the console's wildcard; migration steps 1-2 are one push; dnsmasq's dns key dates from 09-23
2026-10-02 00:48:06 +02:00
jschoubben
24aeb203f7
Issue 193 resolved: both readers live on every machine, checked by asking each copy who it is
2026-10-02 00:35:03 +02:00
jschoubben
afbfd5f29d
Issue 193: mssql's variable substitution and shell commands, proven and fixed by mesh-catalog PR 210
2026-10-02 00:25:48 +02:00
jschoubben
696957aa5e
Issue 193: proven on a throwaway server, fixed for postgres by mesh-catalog PR 209; mssql has the same hole
2026-10-02 00:09:38 +02:00
jschoubben
3d54fcbb86
Merge remote-tracking branch 'origin/main' into decision/docker-module
2026-10-02 00:02:57 +02:00
jschoubben
b13ef1be81
Issues 192 and 193: the console reaches a person only by hand; the store's read-only query is not
...
192: no provision says where the console is, its port was never assigned, and nothing
owns a person's agent configuration since the predecessor left. 193: the query verb wraps
the caller's text in a read-only transaction the text can end, and its rows come back
keyed by BEGIN.
2026-10-02 00:02:51 +02:00
jschoubben
c4151e6bc4
ADR 0163 built: the take digest, the minted-secret refusal, the networks setting, settings judged where stored, genesis raising the forge as declared; issues 096, 097, 126 resolved
...
The record gets its built note; designs 05 and 09 the revisions; 086, 098,
099, 100 and 101 stay located because every machine is converged and the
record's live row — a take read on an adopted machine — has not been run;
090 is built in part, its network difference left for the take to say.
2026-10-01 23:45:57 +02:00
jschoubben
f1941304cc
ADRs 0164-0166 and issue 190: the container runtime gets a module, a seat and declared settings
...
Proposed for the operator's review: settings declared with defaults and cost (0164),
container-runtime as a kernel capability (0165), node-container-runtime seat with the
host creating containers through its holder (0166), and the runtime's file written by
modules that are not its own (190).
2026-10-01 23:13:18 +02:00
jschoubben
6f26f97fdb
Issue 189: the plan's half is built; the moved word stays for a decision
2026-10-01 22:25:31 +02:00
jschoubben
48ca2fb41b
Issue 189: a rebuild from the same commit is not a move, so a packaging module's new image never rolls out
2026-10-01 21:54:44 +02:00
jschoubben
2904c359b8
ADR 0163: taking a module over is a comparison — what it compares, refuses and carries; designs 05 and 09; group 6's issues located, 093 resolved
2026-10-01 21:12:36 +02:00
jschoubben
a2c9fbb665
Issues 184 and 188 resolved: the merge handler returns at once; a machine is resolved with its pins and a dropped one is said
2026-10-01 20:54:10 +02:00
jschoubben
606fbb7add
Issue 188: the second fault beneath the first, and its fix
2026-10-01 18:22:19 +02:00
jschoubben
a92e4bf121
Issue 188: what the live fault was and how it was resolved
2026-10-01 18:14:37 +02:00
jschoubben
187442ec7b
Issue 188: a refusal inside on-the-network drops a machine silently
2026-10-01 18:10:57 +02:00
jschoubben
b0a74b23fd
ADR 0162: a merge produces a tiered plan the mesh keeps; dependencies are one relation; design 30; issues 184, 186
2026-10-01 17:45:48 +02:00
jschoubben
86d1763cfa
Issues 106 and 138 resolved (ADR 0161 built and live); 187 notes a report lost without retry
2026-10-01 17:18:17 +02:00
jschoubben
03e39316ea
Issue 184: a handler replaced mid-merge loses the rest of its work, and the redelivered announcement reads as history
2026-10-01 16:25:38 +02:00
jschoubben
6be284c781
Issue 187: the mesh tells nobody when it stops working
2026-10-01 16:21:05 +02:00
jschoubben
9ddd7215ad
Issue 186 located: the delivery dropped the asks, not the queue; a merge now rebuilds dependents; the release decision stands
2026-10-01 16:16:59 +02:00
jschoubben
180e3b8f7e
Issue 186: a release across repositories is an order in a person's head, and a build is a line in a queue nobody keeps
2026-10-01 16:01:45 +02:00
jschoubben
f35f3757bb
ADR 0161: what deserves a seat — the vault's seat, the hub as a placement of capacity one, the uplink holder as the machine's dialect; design 26; issues 105, 106, 138
2026-10-01 15:55:15 +02:00