jschoubben
235b9ea0e5
Issues 096 and 097, and 094 diagnosed: a setting stored where it cannot work, and a resource that changed target
...
094's cause is one blind spot read from two ends, written up in its diagnosis; the fix
answers the first open question and not the other two, which become 096. 097 was found
looking at what the forge's cutover left running.
2026-09-23 02:20:48 +02:00
jschoubben
515cb8adc1
Issues 094 and 095, both found in the first module's cutover
2026-09-23 01:57:10 +02:00
jschoubben
43b55d6664
Research 013: the forge and the registries — a seat answers the wrong question; issues 090 and 085 corrected from the code
2026-09-23 00:38:34 +02:00
jschoubben
a23ede495e
ADR 0104: a provision may be answered by an adapter to the predecessor; issue 093 located; connectivity says how the proxy hands over
2026-09-22 23:57:38 +02:00
jschoubben
d697c6f776
Issue 093: the successor proxy cannot serve what the predecessor still serves, so no web module can migrate one at a time
2026-09-22 23:45:49 +02:00
jschoubben
a7b3f7823b
Issue 092: it happened twice more — the registry's mesh name, and the mesh's own trust naming the default port
2026-09-22 23:37:05 +02:00
jschoubben
cc3af29084
Issue 092: genesis publishes to a registry the container runtime does not yet trust
2026-09-22 22:43:17 +02:00
jschoubben
fb9d3035d4
Issue 091: a module definition carries a machine port, measured across the catalogue
2026-09-22 22:26:14 +02:00
jschoubben
5c5821b210
Issue 085 resolved: the packages port is a node setting; two of its open questions stay open
2026-09-22 22:00:38 +02:00
jschoubben
1728765fe3
Issues 089 and 090: a contributed route does not follow a moved port; the forge module cannot take over the forge genesis raised
2026-09-22 21:54:35 +02:00
jschoubben
e609ccdbfb
Issue 088: the forge's own address names a port it may not have
2026-09-22 21:41:58 +02:00
jschoubben
87ae893407
Issue 087: the controller cannot tell that a node's host is too old for what it sends
2026-09-22 19:43:01 +02:00
jschoubben
c74ea2a4a8
Records say what the build does: 0101 names only measured daemons; 0102 adds to lists and keeps what it writes over; 0103 names every held kind, the found-service rule, conflicting found rules, guards, and what of 0100 it replaces; designs 05, 09 and 17 in step; issue 084's diagnosis in its own file
2026-09-22 19:38:16 +02:00
jschoubben
ca1f648973
Issue 086: taking a module narrows a port the predecessor served, without saying so
2026-09-22 19:00:59 +02:00
jschoubben
019184ec0f
Issue 085: the packages port given at genesis is not a setting, and a later module can undo it
2026-09-22 18:17:21 +02:00
jschoubben
84761f0600
ADR 0102: the mesh writes into a shared file, never over it; issue 084 located
2026-09-22 17:46:06 +02:00
jschoubben
6165a7ae02
Issue 084: taking networking on an adopted node restarts every container, and the held runtime file blocks pulling
2026-09-22 17:09:21 +02:00
jschoubben
4de74880cb
Issue 083: the proof, the replay caveat, and what is not closed, as three reviews found them
2026-09-22 14:39:29 +02:00
jschoubben
266ee34b5c
Issue 083: the diagnosis describes held messages, the enrolment's order, and what is not closed
2026-09-22 14:24:31 +02:00
jschoubben
2d45aa5f42
Issue 083 resolved: nothing the control queue carries is lost while the store restarts; an enrolment claims its token and spends it last
2026-09-22 14:11:44 +02:00
jschoubben
0d40918e92
Issue 081: proven by the two-node bed, and what it found about baserow's data directory
2026-09-22 13:53:00 +02:00
jschoubben
f6ded3102d
Issue 083 opened (other control messages lost while the store restarts); 082's diagnosis carries its review
2026-09-22 13:34:05 +02:00
jschoubben
9a75f2b6a9
Issue 082: a report that arrives while the store restarts was lost; 081's diagnosis corrected on review
2026-09-22 13:25:33 +02:00
jschoubben
5d1a0372cb
Issue 081 resolved: neither cache consumer can keep its keys under its login, so neither takes the shared cache
2026-09-22 12:27:12 +02:00
jschoubben
35e44c3e5e
Issue 081 opened (a cache consumer does not use its login); 079 and 080 diagnoses carry the review's consequences
2026-09-22 02:04:29 +02:00
jschoubben
f760bf632c
Issue 080: a cache grant let the consumer flush the server; 079: the names follow the resolver's rule for the private network
2026-09-22 01:39:29 +02:00
jschoubben
e31e077fc8
Issue 079: the suffix is handed down, not written twice
2026-09-22 01:27:53 +02:00
jschoubben
17cc36069f
Issue 079: every machine named twice over, found by the large mesh bed; what running that bed cost, on 074
2026-09-22 01:13:29 +02:00
jschoubben
3ea5e47c21
Review: 077 says what closed it and what did not; 078 names module issue; 074's retired fixture; ADR 0099's scope
2026-09-21 23:58:15 +02:00
jschoubben
ead8913a74
Issue 078: module issue's orphan account, refused before it is made
2026-09-21 23:46:51 +02:00
jschoubben
faa7196ad6
Issue 074: opened date restored
2026-09-21 23:44:22 +02:00
jschoubben
8d159cee84
Issue 074 resolved: the declared list is empty of WEARING; what the last three cost
2026-09-21 23:43:31 +02:00
jschoubben
0e0f0298c6
ADR 0099: a step that runs once names what it reads; issues 077 and 078 resolved; designs 08 and 20 amended
2026-09-21 23:33:47 +02:00
jschoubben
6bc9df4b49
Review corrections: 076 and ADR 0098 say what the authority could and could not do; issues 077 (a fetched fact is fetched once) and 078 (secret accept takes any name) opened
2026-09-21 22:55:11 +02:00
jschoubben
6d3cb60949
Issue 076: the route-forwarding bed proves ADR 0098; what the run taught about the overlay
2026-09-21 22:44:24 +02:00
jschoubben
252c6042e8
ADR 0098: a fact a provider makes at first start is fetched from it; issue 076 resolved; design 08 amended; 074 down to one bed
2026-09-21 22:27:32 +02:00
jschoubben
bc373797c7
Issue 076 opened: a served fact made at first start cannot be served; ADR 0097's refusal of an undeclared base is live
2026-09-21 22:16:15 +02:00
jschoubben
ac11bea77f
Issue 020 resolved: the symptom was the bed's, proven against Pebble and step-ca alike
2026-09-21 22:12:51 +02:00
jschoubben
c1a10dc3f8
Issue 066 resolved: a file and its reader are guarded by a gate, proven by the coupled-pair spike; design 20 says so
2026-09-21 22:04:14 +02:00
jschoubben
e993233004
Issue 074: six of the ten beds retired rather than converted
2026-09-21 21:53:11 +02:00
jschoubben
2d77911511
Issue 064 resolved: the package half placed by the genesis run, the image half by ADR 0097
2026-09-21 21:52:32 +02:00
jschoubben
71072e240d
ADR 0097: a vendor image is a declared build input; issue 064's image half decided; design 18 amended
2026-09-21 20:45:36 +02:00
jschoubben
8d981e21b1
ADR 0096: an upstream image is copied between registries; issue 046 resolved; design 18 amended
2026-09-21 20:43:07 +02:00
jschoubben
39a01b7f7e
ADR 0095: the control plane is the way to ask a module; issue 049 resolved; design 19 amended
2026-09-21 20:38:23 +02:00
jschoubben
acc9824949
ADR 0094: a module may hold several secrets from one provider; issue 069 resolved; design 24 amended
2026-09-21 20:29:29 +02:00
jschoubben
a259d1292f
Merge pull request 'ADR 0093: a fixture that runs a module's runtime carries its name; 074 diagnosed; 075 resolved' ( #66 ) from feat/mesh-tests-and-runtimes into main
2026-09-21 19:36:44 +02:00
jschoubben
76cd91413e
ADR 0093: a fixture that runs a module's runtime carries its name; 074 diagnosed, two beds converted; 075 resolved
2026-09-21 19:30:35 +02:00
jschoubben
d92068be7b
Issues 072 and 073 name their merges, the branches being gone
2026-09-21 19:24:28 +02:00
jschoubben
6a35e5a58c
Merge pull request 'Multiple fixes: status vocabulary aligned, 065/026/070/007 resolved, 066/069/049/046 located, 064 diagnosed' ( #64 ) from feat/multiple-fixes into main
2026-09-21 19:23:34 +02:00
jschoubben
bf4d99843f
Merge pull request 'Issue 072 diagnosed: genesis registers the manifest its build produced; design 17 says so' ( #63 ) from feat/one-controller-manifest into main
2026-09-21 19:23:31 +02:00
jschoubben