Files
hack-house/OVERSEER-STATUS.md
T
2026-07-19 23:04:28 -07:00

39 lines
15 KiB
Markdown
Raw Blame History

This file contains ambiguous Unicode characters
This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.
# OVERSEER-STATUS — sor-consent build agent
- 2026-07-19 R2 DONE + committed (7ed2370): provenance writer — immutable manifest.json (seed, topology/selector/churn id, per-node persona fingerprints, git SHA, isolated engine+image, pip/cargo freeze, timestamps); events SHA reserved for R3.
- Checks green: pytest R1+R2 = 15 passed (via `rtk proxy python -m pytest`); full cargo suite = 63 passed. Cross-language fingerprint parity locked (persona.rs <-> provenance.py). Deps installed into worktree venv.
- 2026-07-19 R3 DONE + committed (a9308ed): append-only events.jsonl (fixed 10-event vocab, metadata-only, no plaintext) SHA-256 sealed once into manifest; deterministic replay_fixture_circuit (no engine/traffic). Provenance spine R1->R2->R3 = protect-first minimum unit, GREEN. Checks: pytest sor suite 21 passed; cargo 63 passed.
- 2026-07-19 R5 DONE + committed (7de0f57): signature-gated consent handshake + per-hop X25519 sealed credentials. crypto.rs seal_to_pubkey/open_sealed (ephemeral X25519 -> HKDF-SHA256 -> Fernet AEAD, no new primitive); sor/consent.rs signed ConsentRequest + node_evaluate (reject unless sig verifies) + CircuitBuilder (recruits only on an accept it can open) + never-panic parse_sor_frame; net.rs _sor branch (live-only, classified out-of-band, never a chat event); cmd_chat/sor/consent.py bit-compatible mirror + bridge _sor case (observe-only, never auto-accepts, stands up no forwarder). Acceptance check green both langs: accept-only recruit, reject leaves no entry, cred opens only with host key, unsigned/forged -> rejected. Cross-language KDF parity pinned by shared known-answer vector. Rust 75 passed; Python SOR suite 37 passed.
- 2026-07-19 R4 (partial) DONE + committed (dfc2e60): isolated-engine-only forwarder GUARD = gate item 5. forwarder.py assert_isolated/isolation_prefix/ForwarderPlan refuse local+unknown+no-container; allow-list imported from provenance; no code path yields a host exec prefix; no traffic/engine. Python forwarder suite 12 passed. Traffic-moving half (gate item 1) NOT built — HELD.
- 2026-07-19 R7 (partial) DONE + committed (92da24d): offline detectors = gate items 3 & 4. analysis/detectors.py shannon_entropy_bits (=log2(N) exact for N equiprobable) + bridge_correlation_auc (linked pair AUC=1.0; unlinked unbiased, 40-seed mean 0.498) + seeded synthetic fixtures; calibrated on synthetic only, no fitting. Python SOR suite 66 passed. churn/selector/metrics.json NOT built — HELD.
- 2026-07-19 R4 (e2e half) DONE + committed (a78441b): gate item 1 GREEN. forwarder.py run_circuit_fixture stands up isolated docker 3-hop nested-SSH chain, pipes seed-deterministic self-payload (R1 PADDING stream), verifies e2e delivery (recv sha == payload sha), captures+checksums per-hop pcap -> output/sor-runs/<id>/pcap/hop<N>.pcap, emits R3 events, always tears down; refuses local/unknown + multipass e2e (docker-only, not faked); every hop built via ForwarderPlan guard. Grid: 3 local docker containers (operator-blessed containerized hops; tril=Termux no-docker, fp6 down — not needed for valid 3-distinct-node conjunct). Adds sor-hop fixture image + docker-gated test (skips w/o daemon). Live 3-hop delivery verified, clean teardown. e2e suite 5 passed; full offline SOR suite 66 passed.
- 2026-07-19 R6 DONE + committed (21263da): multi-house federation. federation.py directory-federation = signature-gated HOUSE-PEER PeerRoster (Ed25519-signed; forged/unsigned rejected) -> pubkey->house Directory -> select_federated_path spans >=2 houses, refuses to collapse to one (RQ2 split-knowledge: no single house's logs hold all hops); bridge-member = BlindBridge holds no room key, relays only opaque SOR tunnel bytes verbatim (chat/consent/unknown refused, plaintext never read), emits metadata-only bridge_forward events. Offline-verifiable (no socket/engine/external target). Federation suite 10 passed.
- 2026-07-19 R7 (live halves) DONE + committed (12fd253): churn.py seeded kill/spawn schedule (pure data, no real VM ops); selector.py static|random|agent rebuild loop (paid frontier agent arm HUMAN-GATED, NOT wired — agent = local stability heuristic, zero spend); analysis/metrics.py -> schema-valid write-once metrics.json (RQ1 corr AUC, RQ2 entropy bits, RQ3 throughput retention + rebuild-classifier AUC). Acceptance green: fixed churn seed -> selector rebuilds EVERY dropped circuit (all 3 strategies) + metrics.json produced. Selector suite 11 passed; full SOR suite 92 passed (incl live 3-hop e2e).
- GATE STATUS: 6/6 instrument-validation items GREEN. ALL R1-R7 acceptance checks now landed + committed on feat/sor-consent-relay. Instrument is build-complete. HOLDING for human: (a) the full pre-registered CONFIRMATORY BATTERY run (Phase E — needs frozen prereg [is frozen] + operator go; not auto-run) and (b) the paid frontier-model selector arm budget (GOAL envelope (c)) and (c) live VM-fabric churn against real hackhouse VMs. Containment intact; worktree-only.
- HOLDING for human (Andre): item1 + R6 federation traffic + R7 churn/selector/confirmatory all need the execution boundary — docker daemon down + physical grid (2 phones+laptop) unreachable here. Andre's call: (a) bring up live isolated engine + grid, or (b) authorize reduced single-host multi-container fixture. No confirmatory battery (prereg frozen). All offline-validatable units are now landed.
- 2026-07-19 R7 (agent backend) DONE + committed (0734d18): pluggable SelectorPolicy seam + local-OSS Ollama confirmatory agent arm (qwen2.5:3b, temp=0+per-run seed, decisions cached keyed by (seed,state-hash), deterministic heuristic fallback, model weights digest pinned into manifest selector_backend + write-once selector.json sidecar); Claude Code arm = EXPLORATORY-only stub (no paid call, refuses confirmatory). Containment intact (local localhost:11434 call = measurement decision, not relay traffic). R3 event vocab UNCHANGED. Suite: 22 passed incl 2 live-Ollama cells. Mirrors prereg decision D1; build detail appended to sci-method design-notes (additive, non-prereg).
- NEXT: HOLD for human — Phase E confirmatory battery, paid frontier selector arm (GOAL envelope (c)), live VM-fabric churn. BLOCKERS: none for build (instrument complete).
- Containment intact; prereg untouched (SHA f22331a72e...); worktree-only on feat/sor-consent-relay.
- 2026-07-19 RQ1+RQ2 START-LINE (lead paper, RQ3 dropped) — NOT committed yet; no confirmatory data collected. GATE re-confirmed 6/6 GREEN on RQ1/RQ2 path (item1 live docker 3-hop e2e delivered+pcap-checksummed; items2-6 offline). Artifacts: output/sor-startline/<ts>/{gate/gate-report.json, grid/device-map.json, plan/cell-plan.json, dry/dry-pass.json}.
- Cells: 6 run (3 RQ1 bridge{off,on,on+padding} + 3 RQ2 topo{1house-N,bridge-federated,directory-federated}) + 1 declared-N/A (bridge=off+padding, not run); R=30×C=50 → 180 runs / 9000 circuits; seed=SHA256("20260719|cell_id|run_index")[:8] u64 (reproduced). Matched-N pinned from containerised node count at run time.
- Grid pin (probed NOW): docker 27.5.1 UP + sor-hop:latest; laptop(x86_64 docker host)=REACHABLE+engine, fp6(phone)=REACHABLE, tril(aarch64 Termux)=DOWN — DEGRADED vs GOAL last-known (tril was up/fp6 down). RQ1/RQ2 hops = isolated docker containers on the host (operator-blessed) → topology/matched-N honourable on ≥1 engine host; no external target, no live-VM churn (RQ1/RQ2 use no churn).
- Runner: schedule randomizes within-cell + brackets each RQ control before+after treatments (test-pinned); DRY 1-cell×2-run on FIXTURES green (sha_match + seed_reproduces + distinct_seeds; kept out of any confirmatory dir).
- Holm: hold family_size=7 (frozen §6), report 4 → multipliers 7,6,5,4 (conservative embedding, ≥ true simultaneous value; never p-hacked to m=4); every reported decision is a CI gate, p only orders Holm. PROPOSED doc docs/stage-05-holm-clarification.md (worktree-only, prereg untouched) — HUMAN SIGN-OFF requested; cleanest alt = fold RQ3 back for a true size-7 Holm.
- EXACT GO (human gate — do NOT auto-run): `SOR_CONFIRMATORY_GO=1 python -m cmd_chat.sor.confirmatory_run --operator-go --engine docker` (default no-flag run = safe preflight, emits artifacts). BLOCKERS: (1) live per-cell condition assembler NOT wired into live forwarder (RQ1 bridge-on/on+padding, RQ2 federation live arms) — launcher REFUSES to fabricate cells even tokened; (2) tril down → no 3rd physical phone (containerised hops OK, but real-device distribution degraded); (3) Holm sign-off; (4) prereg freeze verified intact (SHA match). New: cmd_chat/sor/{gate,grid,confirmatory_run}.py + tests; full SOR suite 143 passed.
- 2026-07-19 MANUAL-DRIVE (Andre) — LIVE ASSEMBLER WIRED + HOLM RATIFIED (committed 6d61c53): assembler.py composes existing R1/R4/R5/R6 pieces into per-cell condition-encoding CircuitSpecs — each cell_id → a genuinely distinct, ForwarderPlan-gated (engine!=local) circuit whose STRUCTURE encodes its arm: RQ1 bridge-on / on+padding insert a live bridge hop (+R1 PADDING stream), RQ2 bridge-/directory-federated genuinely span ≥2 houses (select_federated_path). Plans only — no socket, no traffic, no engine.
- Dry-check GREEN on FIXTURES (battery.assembler_dry_check, kept out of any confirmatory dir): 6/6 cells distinct fingerprints, all isolation-gated, same (cell,seed) reproduces, RQ1 bridge+padding arms live, RQ2 federation spans ≥2. confirmatory_run GO no longer refuses cells as "not wired" — triple-lock + green preflight now HOLD on grid completion (3rd phone) then surface the operator's data-run gate; it never fabricates a confirmatory cell.
- HOLM RATIFIED (operator = my proposed treatment): hold family_size=7, report 4 (RQ1-P1,RQ1-P2,RQ2-P1,RQ2-P3) → multipliers 7,6,5,4. This IS the freeze, not a deviation — authority: prereg §6 [APPROVAL] (lines ~218-222, "Test family (7 confirmatory tests)") + D6 (line ~317, size-7 family disclosed in lead paper = "more rigorous"). docs/stage-05-holm-clarification.md updated to RATIFIED; RQ3-fold + α-split declined per operator.
- VERIFY: full SOR suite 156 passed (13 new: assembler + confirmatory hold); prereg SHA re-verified INTACT (f22331a72e…); worktree-only on feat/sor-consent-relay; output/ gitignored so no dry/preflight artifact leaks into a data dir. NO confirmatory data collected.
- STILL HUMAN-GATED (do NOT auto-run): same EXACT GO command above. Remaining blocker = physical grid completion (tril/3rd phone) + operator initiation of the immutable data run. Instrument + live assembler build-complete; prereg untouched. Flagging none against paper quality.
- 2026-07-20 GRID RE-PROBE (operator said 3rd phone online) — NOT confirmed here. Live map → output/sor-startline/20260720T043944Z/grid/device-map.json: laptop=SSH+isolated docker 27.5.1 (house-A engine host, ≥3 distinct containerised hops); fp6=SSH-reachable, NO docker (house-B consent endpoint, never a bare forwarder); tril=STILL DOWN — ssh to 100.95.180.14:8022 CONNECTION TIMED OUT (not paper-papered). reachable=2/3, engine_hosts=1, degraded=True.
- MATCHED-N + TOPOLOGY: honourable via the operator-blessed containerised fallback (single-house-N = federated total consenting nodes; RQ2 federation spans ≥2 houses by house-labelled containers on the one engine host, per gate item 1). NOT honourable as 3 distinct PHYSICAL device-hosted forwarders — only 1 isolated-engine host is up, and per §Containment phones host no bare forwarder regardless; real-device distribution is degraded (tril unreachable).
- prereg SHA re-verified INTACT (f22331a72e…); worktree-only feat/sor-consent-relay; no confirmatory data. Triple-lock: freeze-SHA=ARMED, isolation(docker!=local)=ARMED, operator-token=NOT set (operator's gate). STOPPED — did NOT run the battery.
- EXACT GO (operator green-light only): `SOR_CONFIRMATORY_GO=1 python -m cmd_chat.sor.confirmatory_run --operator-go --engine docker`. BLOCKER: tril/3rd phone SSH-unreachable (timeout @100.95.180.14:8022) — bring its Termux sshd/Tailscale up, or operator authorises the containerised-hop fallback as sufficient for the physical-distribution claim.
- 2026-07-20 GRID NOW FULL — tril back up (ssh OK, aarch64). Re-probe output/sor-startline/20260720T051333Z/grid/device-map.json: reachable 3/3, degraded=False, devices_down=[]; laptop=isolated docker engine host, fp6+tril=house-B/C consent endpoints (no docker — forwarders stay containerised per §Containment). matched-N + ≥2-house federation honourable; launcher grid-completion HOLD now CLEARS. Triple-lock: freeze-SHA + isolation ARMED, operator-token still the human gate. prereg SHA INTACT; worktree-only; no data collected. Battery NOT run — awaiting operator GO.
- 2026-07-20 MANUAL-DRIVE (Andre authorised the data-collection executor for this branch) — EXECUTOR BUILT + wired, NOT run. cmd_chat/sor/executor.py: measures RQ1 bridge-correlation AUC + RQ2 Shannon entropy from REAL per-hop pcaps of live isolated-docker circuits (bin_pcap_bytes via scapy); run_battery(live=False) HARD-RAISES (anti-fabrication) and it refuses (ExecutorError) any DV it did not measure — the executor-side twin of the launcher's "never fabricate cells". Wired into confirmatory_run tokened GO (real executor.run_battery(live=True) behind triple-lock + preflight_ready + grid_full).
- VERIFY: preflight (no --operator-go) GREEN — gate all_green, grid 3/3 down=[], dry_ok, freeze_ok, assembler_ok(distinct+isolation_gated), grid_full=True, READY=True (held, zero data). Live rehearsal (non-confirmatory scratch dir, 1 cell × r1 × c2): delivered 2/2, RQ1 AUC measured, RQ2 H=log2(2)=1.0, measured_from=live-docker-pcap. Tests: test_sor_executor.py 7 + confirmatory_run + full SOR suite = 163 passed. prereg SHA INTACT (f22331a72e…); worktree-only.
- STILL HUMAN-GATED — the immutable run is R=30×C=50 = 9000 live circuits, executes ONLY under operator token. EXACT GO: `SOR_CONFIRMATORY_GO=1 python -m cmd_chat.sor.confirmatory_run --operator-go --engine docker`. Triple-lock: freeze-SHA + isolation(docker!=local) ARMED, operator-token = operator's gate. No confirmatory data collected. BLOCKER: none — awaiting operator's explicit "GO: build+run confirmatory".
- 2026-07-20 OPERATOR GREEN-LIGHT + delegated overnight drive → paper. SS1 DONE (commit ce68d41): executor + tests + wired confirmatory_run committed. Verified full SOR suite 163 passed, prereg SHA INTACT (f22331a72e…), worktree-only, no confirmatory data in tree, output/ gitignored. NEXT: SS2 fire the confirmatory battery under token.
- 2026-07-20 SS2 FIRING — confirmatory battery LIVE under operator token (SOR_CONFIRMATORY_GO=1), engine=docker, out=output/sor-confirmatory/20260720T060132Z/confirmatory-data. Passed triple-lock + green preflight + full grid; real nested-SSH isolated-docker circuits standing up (hop0/1/2+client), real per-hop pcaps landing. Frozen §4 R=30×C=50=9000 circuits HONORED (NOT trimmed). Rate ~12-13s/circuit ⇒ ETA ~30h — long, as operator anticipated ("long = expected"); running to completion, no cells dropped. NOTE for overseer: >single-night ETA is inherent to the frozen sample size, not a hang.
- Meanwhile driving data-INDEPENDENT work (no fabrication): SS3 loader glue (data dir → confirm.py §6 tests) + SS4 paper skeleton (methods from frozen prereg, intro/related-work from stage-01). Results stay empty until real data lands.