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

2026-10-07T23:23:59Z

mesh-admin commented

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

minio's comments (client.ts:319, provisioner/index.ts:15,77) cite ADR 0201 for the derived-value record. 0201 is the key-value-buckets record; the derived-value record is 0202. Comment-only change.

minio's comments (`client.ts:319`, `provisioner/index.ts:15,77`) cite ADR 0201 for the derived-value record. 0201 is the key-value-buckets record; the derived-value record is 0202. Comment-only change.

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

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

mesh/merge-gate fail: builds minio, sent nowhere; no bus step; 1 wait(s) for a person; a manifest the change touches fails the module check: minio grants s…

Details

mesh/repo-check fail: mesh/repo-check is required here and this head defines no merge-check.sh — a person adds one, or lifts the requirement from the branc…

Details

mesh/delivery stopped: the pull request closed unmerged

Details

ed10d96048

mesh-admin commented

2026-10-07 23:24:58 +00:00

Merge check at ed10d960

mesh/merge-gate: FAIL — a manifest the change touches fails the module check: minio grants s3-bucket and does not say what it keeps for its consumers: data.consumers.s3-bucket with a class — irreplaceable, valuable, rebuildable, cache, or none (novox/hq ADR 0233) (modules: minio)
mesh/repo-check: FAIL — mesh/repo-check is required here and this head defines no merge-check.sh — a person adds one, or lifts the requirement from the branc…

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 shanks as build-1791415468441989014 (builds --log build-1791415468441989014).

--- the gate: minio
minio grants s3-bucket and does not say what it keeps for its consumers: data.consumers.s3-bucket with a class — irreplaceable, valuable, rebuildable, cache, or none (novox/hq ADR 0233)
minio mounts its directory "data" into a container to be written, and declares no data in it: data.own with a class — cache if it is disposable (novox/hq ADR 0233)
minio: ok; 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
mesh-controller: 2 problem(s) in 1 manifest(s)
--- the same manifests on main
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

**Merge check** at `ed10d960` - `mesh/merge-gate`: **FAIL** — a manifest the change touches fails the module check: minio grants s3-bucket and does not say what it keeps for its consumers: data.consumers.s3-bucket with a class — irreplaceable, valuable, rebuildable, cache, or none (novox/hq ADR 0233) (modules: minio) - `mesh/repo-check`: **FAIL** — mesh/repo-check is required here and this head defines no merge-check.sh — a person adds one, or lifts the requirement from the branc… **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 shanks as `build-1791415468441989014` (`builds --log build-1791415468441989014`). ``` --- the gate: minio minio grants s3-bucket and does not say what it keeps for its consumers: data.consumers.s3-bucket with a class — irreplaceable, valuable, rebuildable, cache, or none (novox/hq ADR 0233) minio mounts its directory "data" into a container to be written, and declares no data in it: data.own with a class — cache if it is disposable (novox/hq ADR 0233) minio: ok; 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 mesh-controller: 2 problem(s) in 1 manifest(s) --- the same manifests on main 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 ```

mesh-admin commented

2026-10-07 23:25:01 +00:00

Delivery novox/mesh-catalog@ed10d9604836 — stopped since 2026-10-07T23:42:44Z

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:24 (new) → proposed (announced): novox/mesh-catalog#116's head announced
2026-10-07 23:24 proposed → checked (checked): the verdict names this commit
2026-10-07 23:24 checked → rejected (refused): the gate failed or could not run, or the repository's own check failed
2026-10-07 23:42 rejected → stopped (closed): the pull request closed unmerged

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

**Delivery** `novox/mesh-catalog@ed10d9604836` — **stopped** since 2026-10-07T23:42:44Z **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:24 (new) → proposed (announced): novox/mesh-catalog#116's head announced - 2026-10-07 23:24 proposed → checked (checked): the verdict names this commit - 2026-10-07 23:24 checked → rejected (refused): the gate failed or could not run, or the repository's own check failed - 2026-10-07 23:42 rejected → stopped (closed): the pull request closed unmerged The commit's note under `refs/notes/mesh-plan` keeps every transition: `git log --notes=mesh-plan`.

mesh-admin closed this pull request

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

mesh-admin referenced this pull request

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

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

mesh-tools referenced this pull request

2026-10-16 09:13:05 +00:00

A delivering group says success on mesh/delivery-group, so its later members can merge (issue 902) #329