4.2 KiB
4.2 KiB
STATE-SNAPSHOT-20260828-2000 (pre-compact #4)
Read order: BOARD.md -> this -> HUD.md -> log tail. PMO pinned session 78cf63b8a72f4282 (screen RCEO-PMO). Work pinned e1079fafb8c37d60 (RCEO-Work).
THE PIVOT (dominates everything)
Charles decreed: custom agent harness in GO ("MOPAC") replaces the bash/screen/doorbell/_crossfeed hack stack. All patterns from 2026-08-28 carry over; only substrate changes. Done by 0800 target; slow/steady grind, no quota burn, keep going overnight.
MOPAC layout (/home/reachableceo/projects/meta/MOPAC/)
- harness/ : git repo, AGPLv3 VERBATIM LICENSE, DESIGN.md (v0 + additions),
go.mod. PUBLIC on gitea reachableceo/MOPAC (pushed, 5+ commits,
https remote works). Committed: spec, parity target, org model
(verticals first-class), interaction layer = Redmine/Discourse/Gitea ONLY,
Go-only toolchain HARD RULE (CMMC/SCI/ITAR; node exceptions = containerized
- logged, Playwright-class needs his sign-off), dedicated CLIs (approved): MOPAC/tools/{redmine-cli,discourse-cli,bitwarden-go}.
- reference/ : clones crush (charmbracelet), maki (tontinton), KNELSecretsManager. STUDY = PORTING-NOTES-*.md in harness/docs/.
- siblings/ : KNEL-AIMiddleware moved here (from _crossfeed/tooling); ~/projects/KNEL-AIMiddleware symlink repointed.
- lsp/ : LSP task creating (gopls critical; dockerfile/marksman/yaml/bash; node ones containerized, accepted exceptions).
SoR status (interaction layer)
- Redmine: projects.knownelement.com (creds ~/.creds/redmine.env; was hung on Cloudron, he bounced it, works). Project MOPAC created PUBLIC + 7 issues. ALL MOPAC work tracked there.
- Gitea: reachableceo/MOPAC public, AGPL-3.0 detected. tea works
(
tea repo create --name Xno --owner; https push OK). - Discourse: category creation 403 (key not admin). Fallback: repo docs; port when he drops admin key in ~/.creds/discourse.env.
Infra live
- LiteLLM proxy: 192.168.3.78:4001 (4000 taken). 8 virtual keys (receo $50/30d, TSG $30, offstage $15; values in tooling/credentials/litellm-virtual-keys.md 600 gitignored). REQUIRES postgres for vkeys/spend (he approved -db container; litellm-db.env exists — VERIFY it actually got deployed; sqlite path failed). crush wiring: ~/.config/crush/crush.json (600) — NOT providers.json (crush auto-regenerates it; caused transient 401). Backups: *.pre-litellm.bak. Usage API verified: /key/info shows spend.
- Known flake: z.ai "Message content shorter than read bytes" on ~2 of 5 headless turns — redispatch works; LiteLLM adds retry layer eventually.
Overnight machinery (running now)
- work-chain-harness screen: sequential chain via ~/.coordinate/scripts/work-chain.sh harness — status ~/.coordinate/logs/harness.status. Order: study-crush DONE -> study-maki RUNNING -> study-secrets -> harness-skeleton (TASK-20260828-1903). BUG FIXED: launch with ABSOLUTE task paths; missing task = halt not skip.
- Parallel turn: work-turn-lsp (TASK-20260828-1915-lsp-stack): containers, wrappers per KNEL pattern, crush wiring, verify diagnostics flow.
- dispatch-turn.sh: semaphore-gated headless turns; doorbell to RCEO-PMO is OK tonight (accepted), dies with harness v1. -Founder gate: tonight's standing go covers MOPAC build chain (he said keep grinding); NO live-stack cutover; pilot = read-only/demo scope.
Open items (owner)
- HIM: 0800 acceptance criteria proposed (skeleton+dry-run+1 real turn writeback+LSP+3 notes; NOT mcp/clis/bitwarden) — awaiting his confirm.
- HIM: discourse admin key; oauth-defer (default yes); events T0 (default yes); sudo root-migrate-coordinate.sh (morning fine).
- PMO: verify litellm-db postgres actually deployed (report said approved path; confirm container running + db_url set).
- PMO: when chain REPORTs land -> verify, archive TASK, UPDATE REDMINE ISSUE statuses (mirroring = new standing practice).
- PARKED: D2 pilot scope (MOPAC redmine project IS it now), D4, account-split beyond shared assets, MIGRATION-projects, chipreverse->CTO, vertical reactivation, scroll polish, founder/ dir rename, RCEO-ScrollTest kill.
Comms protocol reminder
Spoonfeed ONE item/turn; HUD table end of every reply; longform to files; never "founder"; medium verbosity per his iPad ask tonight; keep him focused.