golden 0.209.0 BAKED, PUBLISHED, ROUND-TRIP VERIFIED — the currency gate goes green (R-242)
gates / gates (push) Failing after 29s

The G-1 session released controller v0.209.0 (R-247), which made golden_currency_gate.py correctly
red and REFUSED THE PUSH: no golden carried the newest release. The honest answer to that is the bake
it asks for, not --no-verify. The gate's own docstring says the cost of a trip is one bake, which is
the operation this project wants to be routine.

656 697 956 B, sha256 c9c4bcd6..e818ff. Round-tripped: the published bytes downloaded back, hashed
independently, size and sha identical, and ./etc/felhom-controller-image read OUT of the downloaded
archive says felhom-controller:0.209.0 — the delivered artifact naming the controller it will start.

Acceptance markers all green (overlay2 x1, mount points x2 rootfs+mp0, upload HTTP 201 x1,
excluding/FATAL/mp1 x0), Result=success, ExecMainStatus=0. 404 pre-gate with a 200 control on
0.208.0 so a 404 could not mean "wrong URL". Token file->file into a 0600 file read inside the VM;
systemctl show grep = 0; committed-log grep = 0 WITH a control returning 1 to prove the grep works.
Bake VM destroyed, /root residue clean, qemu confirmed gone, drill disk restored to virgin.

IT ALSO CONSOLIDATES THE OPERATOR'S APPROVAL. Golden 0.208.0 was baked last night and never vouched;
0.209.0 contains everything it did plus R-247, so it supersedes rather than wastes it. One Save, not
two — STATUS.md updated accordingly and back to its 93-line screen.

NOT VOUCHED. Fresh installs still land on 0.207.0 until the operator saves. And R-242's untouched
half showed itself again: this gate flipped green on the presence of the evidence DIRECTORY, with no
vouch anywhere near it. Recorded, not built — ROADMAP G-8.

repo_gates --fast: all 8 OK, including wire-contract and golden-currency.
This commit is contained in:
2026-08-08 09:01:26 +02:00
parent b080ecf411
commit 2ce3c2a0f2
3 changed files with 440 additions and 11 deletions
+12 -11
View File
@@ -62,20 +62,21 @@ per-guest network health, which we already lost 1 h 15 m to once.
## What we're working on
- **Widening the check** so a fourth secret-in-a-page is caught by a machine, not by someone. *(R-255)*
- **Deciding the twenty-one** — for each: give it a reader, or stop sending it. *(R-264)*
- **Proving the hub really keeps the old sealed key** when a machine re-seals. *(R-198)*
- Still open from the overnight sweep, none urgent: *(R-256…R-259, R-261…R-263)*
- **Widening the check** so a fourth secret-in-a-page is caught by a machine. *(R-255)* · **Deciding
the twenty-one** — each gets a reader, or stops being sent. *(R-264)*
- **Proving the hub really keeps the old sealed key** when a machine re-seals. *(R-198)* · Still open
from the overnight sweep, none urgent: *(R-256…R-259, R-261…R-263)*
## Waiting on you
- **One approval: the new base image.** Tonight's release is baked, published and byte-checked, and
**installations still receive yesterday's version until you press Save.** Hub → Configuration →
Day-0 artifacts → Golden **0.208.0** → Save. One field moves; the other two are already right and
were checked. Reversible — re-select 0.207.0 and Save. *(R-242)*
- **Third time in three days, so worth a minute.** A check now catches the *baking* being forgotten;
**nothing catches the approval being forgotten** — tonight's bake proved it, going green before the
approval existed. Two ways to close it are written up, neither built. *(ROADMAP G-8)*
- **One approval, and now it is the only one: the new base image.** Baked, published, byte-checked
and **installations receive an older version until you press Save.** Hub → Configuration → Day-0
artifacts → Golden **0.209.0** → Save. One field moves, the other two were checked and are right,
and it is reversible. It supersedes last night's unvouched 0.208.0, so this is one decision, not
two. *(R-242)*
- **Fourth time in three days, so worth a minute.** A check now catches the *baking* being forgotten
— it caught it again today and refused the push until it was done. **Nothing catches the approval
being forgotten.** Two ways to close that are written up, neither built. *(ROADMAP G-8)*
## DooPlex infrastructure — separate from the product