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
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
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
e993233004
Issue 074: six of the ten beds retired rather than converted
2026-09-21 21:53:11 +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
5dcb9dfbf6
ADR 0089: a bed reads the catalogue it proves; issue 073 diagnosed; issues 074 and 075 opened
...
The end-to-end design held 'the run rebuilds what it tests' for binaries and images
and not for manifests. The beds' inline copies fell into three kinds; only the first
is a stale copy. The other two are named: a mesh test wearing a catalogue module's
name (074) and a stocked runtime image the run never rebuilds (075).
2026-09-21 14:35:08 +02:00
jschoubben