minio: cite the derived-value record as ADR 0202, not 0201 #117

2026-10-07T23:42:34Z

mesh-admin commented

2026-10-07 23:42:34 +00:00

Re-applied onto today's main (replaces #116, whose base was weeks old). minio's comments cite ADR 0201 for the derived-value record; it is 0202 (0201 is the key-value buckets). Comment-only.

mesh-admin added 1 commit 2026-10-07 23:42:34 +00:00

The derived-value record is ADR 0202 (was 0201)

mesh/merge-gate pass: builds minio, sent nowhere; no bus step; 1 wait(s) for a person; every machine composes with the change as it did without (4 of 4 com…

Details

mesh/repo-check pass: its merge-check.sh passed

Details

mesh/delivery delivered

Details

49f5ba377e

(cherry picked from commit ed10d96048)

mesh-admin commented

2026-10-07 23:42:59 +00:00

Delivery novox/mesh-catalog@49f5ba377ece — delivered since 2026-10-07T23:57:03Z

Delivery plan — builds minio, sent nowhere; no bus step; 1 wait(s) for a person

tier 0: minio
novox: waits for a person: minio
minio waits for a person: its policy records (module)
minio provides s3-bucket: its consumers are sent again after it
minio keeps data (ADR 0233): what it holds is backed up before it moves

Transitions

2026-10-07 23:42 (new) → proposed (announced): novox/mesh-catalog#117's head announced
2026-10-07 23:45 proposed → checked (checked): the verdict names this commit
2026-10-07 23:45 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
2026-10-07 23:55 ready → published (merged): on the trunk its modules follow: merged there, and its walk opened — or nothing for a walk to move
2026-10-07 23:55 published → delivering (go): its walk started: let go by this owner in its group's order, by a person, or on the controller's own path
2026-10-07 23:57 delivering → delivered (done): its walk is done: every machine of its deploy plan passed, or was left as its policy says

The commit's note under refs/notes/mesh-plan keeps every transition: git log --notes=mesh-plan.

**Delivery** `novox/mesh-catalog@49f5ba377ece` — **delivered** since 2026-10-07T23:57:03Z **Delivery plan** — builds minio, sent nowhere; no bus step; 1 wait(s) for a person - tier 0: minio - novox: waits for a person: minio - minio waits for a person: its policy records (module) - minio provides s3-bucket: its consumers are sent again after it - minio keeps data (ADR 0233): what it holds is backed up before it moves **Transitions** - 2026-10-07 23:42 (new) → proposed (announced): novox/mesh-catalog#117's head announced - 2026-10-07 23:45 proposed → checked (checked): the verdict names this commit - 2026-10-07 23:45 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail - 2026-10-07 23:55 ready → published (merged): on the trunk its modules follow: merged there, and its walk opened — or nothing for a walk to move - 2026-10-07 23:55 published → delivering (go): its walk started: let go by this owner in its group's order, by a person, or on the controller's own path - 2026-10-07 23:57 delivering → delivered (done): its walk is done: every machine of its deploy plan passed, or was left as its policy says The commit's note under `refs/notes/mesh-plan` keeps every transition: `git log --notes=mesh-plan`.

mesh-admin commented

2026-10-07 23:45:13 +00:00

Merge check at 49f5ba37

mesh/merge-gate: PASS — every machine composes with the change as it did without (4 of 4 compose) (modules: minio)
mesh/repo-check: PASS — its merge-check.sh passed

Delivery plan — builds minio, sent nowhere; no bus step; 1 wait(s) for a person

tier 0: minio
novox: waits for a person: minio
minio waits for a person: its policy records (module)
minio provides s3-bucket: its consumers are sent again after it
minio keeps data (ADR 0233): what it holds is backed up before it moves

Run by the build seat on g14 as build-1791416584531821137 (builds --log build-1791416584531821137).

--- the gate: minio
minio: ok, keeps data (valuable); WARNING: server stay(s) up and say(s) not how it is ready — judged by liveness alone, refused from 2026-11-18 (ADR 0240 rule 8)
long-running resources without health: 1
1 manifest(s) checked. Judged against the seats this binary carries; a claim on one of the mesh's own seats is judged fully at registration, and a seat declared by a module not given here reads as unknown. Identities judged on a 6-character machine name, against the bounds of the providers given here
judging 1 module(s) changed against 4 machine(s), as the snapshot of 2026-10-07T22:47:27Z says they run
composing every machine as the mesh is
the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued
the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued
composing every machine with the change
the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued
the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued
merge gate: PASS — every machine composes with the change as it did without (4 of 4 compose)
judged by controller development build against the facts of 2026-10-07T22:47:27Z

modules the change moves:
  - minio (changed)

machines:
  - a machine (f35): composes
  - holds mesh-dns-resolver (idt): composes
  - holds git, holds mesh-artifact-store, holds mesh-broker, holds mesh-catalog, holds mesh-delivery, holds mesh-dns-resolver, holds mesh-store, holds mesh-vault, holds npm-package-registry, the control node, the hub (ygcyr): composes
  - a machine (yvbpsm): composes

a merge would rebuild 1 module(s) in 1 tier(s): minio
--- its merge-check.sh (go toolchain)
ok  	git.novox.be/novox/mesh-catalog/checks/words	0.002s
words: 12 retired words, none in the 28277 strings of 524 files
long-running resources without health: 70, as kept
NOT TESTED HERE: modules/minio is TypeScript; the gate judges its manifest

**Merge check** at `49f5ba37` - `mesh/merge-gate`: **PASS** — every machine composes with the change as it did without (4 of 4 compose) (modules: minio) - `mesh/repo-check`: **PASS** — its merge-check.sh passed **Delivery plan** — builds minio, sent nowhere; no bus step; 1 wait(s) for a person - tier 0: minio - novox: waits for a person: minio - minio waits for a person: its policy records (module) - minio provides s3-bucket: its consumers are sent again after it - minio keeps data (ADR 0233): what it holds is backed up before it moves Run by the build seat on g14 as `build-1791416584531821137` (`builds --log build-1791416584531821137`). ``` --- the gate: minio minio: ok, keeps data (valuable); WARNING: server stay(s) up and say(s) not how it is ready — judged by liveness alone, refused from 2026-11-18 (ADR 0240 rule 8) long-running resources without health: 1 1 manifest(s) checked. Judged against the seats this binary carries; a claim on one of the mesh's own seats is judged fully at registration, and a seat declared by a module not given here reads as unknown. Identities judged on a 6-character machine name, against the bounds of the providers given here judging 1 module(s) changed against 4 machine(s), as the snapshot of 2026-10-07T22:47:27Z says they run composing every machine as the mesh is the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued composing every machine with the change the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued merge gate: PASS — every machine composes with the change as it did without (4 of 4 compose) judged by controller development build against the facts of 2026-10-07T22:47:27Z modules the change moves: - minio (changed) machines: - a machine (f35): composes - holds mesh-dns-resolver (idt): composes - holds git, holds mesh-artifact-store, holds mesh-broker, holds mesh-catalog, holds mesh-delivery, holds mesh-dns-resolver, holds mesh-store, holds mesh-vault, holds npm-package-registry, the control node, the hub (ygcyr): composes - a machine (yvbpsm): composes a merge would rebuild 1 module(s) in 1 tier(s): minio --- its merge-check.sh (go toolchain) ok git.novox.be/novox/mesh-catalog/checks/words 0.002s words: 12 retired words, none in the 28277 strings of 524 files long-running resources without health: 70, as kept NOT TESTED HERE: modules/minio is TypeScript; the gate judges its manifest ```

mesh-admin merged commit 4c8007c564 into main

2026-10-07 23:55:49 +00:00

mesh-admin deleted branch fix/minio-cites-0202

2026-10-07 23:55:49 +00:00

mesh-tools referenced this issue from a commit

2026-10-17 16:23:05 +00:00

Say on every directory how it treats files it does not know, and check it (issue 1024, ADR 0422)

mesh-tools referenced this pull request

2026-10-17 16:23:20 +00:00

Every directory says how it treats files it does not know, and the catalogue checks it (issue 1024) #349

~~mesh-tools referenced this pull request 2026-10-17 17:24:58 +00:00~~

Every directory says how it treats files it does not know, and the catalogue checks it (issue 1024) #349