UKRRS/mopac-pmo
2
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

pmo: file 523 alpha exit gate — roadmap no longer overstates self-hosting

Browse Source
This commit is contained in:
mrcharles
2026-08-29 07:12:13 -05:00
parent 5906c3e7d7
commit 9ad10c378c
2 changed files with 13 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files
log.md
+1
View File
@@ -92,3 +92,4 @@
2026-08-29T07:04:03-05:00 | PMO | hb 07:02 chain check: no REPORTs ready — q14 README done 07:03, REPORT imminent (wake-q14 fuse armed 15m); q15 mid-B4, loop.test running 10m-timeout; q16 correctly gated on q15 screen; loop idle-scan; no flakes; chain full — nothing to dispatch
2026-08-29T07:07:24-05:00 | PMO | sync audit (Charles ?): Gitea clean (unpushed=0 all repos; stale pre-rename clones noted for retirement cleanup). Redmine gap found+fixed: 519 writes 502'd 11:28Z cloudron blip; loop.jsonl has errors but scan never retries (updated_on stale) — PMO drafted briefing v0 from SPEC, posted note to 495, resolved 519; mred passed live-write acceptance (2 writes rc=0) — python glue retired for PMO ops; 506 close at 07:18 fuse
2026-08-29T07:11:17-05:00 | PMO | CHARLES DIRECTIVE executed: all 17 Phase 3 tickets -> Production due 9/1 0630 (496/498/500-515 via mred, verified Phase 3=0 open, Production=21 open incl 492/493/516/517); directive note on 498; Phase 3 version retired-by-absorption (empty, left open — mred lacks version update). Critical path: 1900 wiring gates 504/505/503/500/497; 517 gates keyproxy; 521 gates loop capacity
2026-08-29T07:12:13-05:00 | PMO | Charles callout fixed: Alpha roadmap lied (518-520 closed => 100% while dev.sh screen still wraps attached docker run --rm, no restart policy, crush still driving). Filed 523 Alpha exit gate (Infrastructure, Immediate, due today) w/ acceptance: restart-policy container, dev.sh screen dead, crush screens retired, autonomy proof; 521 blocks 523; Alpha now truthfully 3/4 open-1
outbox/desc-523-alpha-gate.md
+12
View File
@@ -0,0 +1,12 @@
Alpha is NOT complete. Roadmap showed Selfhost Alpha at 100% because 518-520 closed, but the loop daemon currently runs as a screen session wrapping an attached `docker run --rm` via dev.sh — no restart policy, no supervisor, dies with the screen, and crush still drives the build chain.
This ticket is the explicit exit gate for the Selfhost Alpha version. Alpha stays open until ALL hold:
1. Loop runs as a container with restart policy (compose `unless-stopped` or equivalent) — survives crash and host reboot without any screen/crush involvement.
2. dev.sh screen (`mopac-loop-alpha`) killed; container is the only driver.
3. All crush screens retired per Charles's standing order (q14/q15/q16 landed first).
4. Container proves autonomy: picks up a New ticket, turns it, posts REPORT + Redmine mirror unattended.
Bootstrap work lands via 521 (container + tool-widening, in flight); 521 blocks this ticket. PMO verifies against these acceptance criteria before setting Alpha done.
Filed by PMO on Charles's callout 2026-08-29: "we are not self hosted."