giles
72e461cf2c
The forge already DRIVES sessions (briefing → tmux launch, sx-fix-up.sh).
This records what comes BACK, making the forge a true system of record:
- sx-fix-writeback.sh <forge-agent> [kind] [base-ref]: reads new commits on
loops/sx-<slug>, appends a record per commit to writeback.sxsrc (idempotent,
matched by sha), then rebuilds the forge + replays them as agentic-sx
commit!s on agents/<forge-agent> and re-dumps forge.sxdata.
- forge-build.sxsrc: fb-writeback-records / fb-replay-writeback / fb-do-writeback
— each real-git commit becomes an agentic-sx commit whose tree is a small
commit.sx pointer (sha/branch/message/files); real git holds the code, the
forge holds the index, so the CID stays small.
- writeback.sxsrc: the append-only record log (source of truth for what's
been recorded); replayed chronologically so agent branch heads advance right.
Verified live: the sx-gate loop's first real commit (f09368e1, "pin K18
expt-overflow float-promotion") is now recorded as a test-kind agentic-sx
commit on agents/ws-W14 (session log: spawn → finding → writeback), its
commit.sx pointing back at the real-git sha.
Loop closed: forge → tmux (drive) and tmux → real-git → forge (record).
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
SX Review — 2026-07-03
Findings from three parallel review sessions of the SX language/runtime, plus the master remediation plan.
| File | What |
|---|---|
| PLAN.md | Master remediation plan: 15 workstreams (W1–W15), execution order, and a full per-finding coverage ledger. Start here. |
| RULINGS.md | 40 draft normative rulings (R1–R40). Phase-0 gate — ratify before the semantics fixes. |
| core.md | Language core / spec semantics lane (K01–K110). |
| hosts.md | Per-host implementations + FFI lane (J*, C*, JS*, P*, S*, PY). |
| conformance.md | Cross-host agreement + test adequacy lane (F1–F15, S1–S5). |
Status: the quick-wins batch (commit dc7aa709) landed 13 fixes + 4 partials; suite at baseline
5762p/274f (fail set byte-identical). Everything else is OPEN/GATE/DEFERRED per PLAN.md's ledger.
Highest-value open items: K01 (guard/handler re-raise hang — DoS-able, server+browser), S1 (live HTTP crash under load), K03 (shift-k double-execution), and W14 (test gate — the enabler that makes all other fixes verifiable).
Blocking decisions (maintainer): D1 host lineup, D2 ratify rulings, D3 gate definition.