Caesar III explicit range stage and compact consumers, 2026-11-12
The actual production chunk provisioner now accepts an explicit existing absolute stage_dir. Its portable default is unchanged. Caesar's own emitted caller freezes /dev/shm in stage-selection.json and passes it through Transport.provision. One bounded 4 MiB raw range is staged there, then removed; there is no fallback, whole-media copy, RAM admission gate, increased cap, retry, or remote rollback claim. Source identity, whole SHA, ordered coverage, per-range checks, assembly and final fresh remote reread remain unchanged. chunk-ready.localStagePath records the actual working path.
Evidence: scratch/runs/20261112-caesar3-range-stage-food-2355/. stage-tests.log tests the actual Transport and HTTP PUT/command peer with 4,352,000 synthetic bytes, two ordered ranges, real generated assembly and final reread. Both explicit RAM staging and the unchanged portable default pass. Mutation, source truncation, HTTP refusal, lost POST ACK, cancellation, and truncated command evidence clean only the owned temp directory, preserve an unrelated sentinel, and reject a second provision without another POST. Invalid explicit directories fail without fallback. emitted-stage-test.json additionally runs the actual own Caesar control.provision and emitted command callback, validates every real local range under /dev/shm, reconstructs full bytes/SHA/order, and reads its compact closure receipt.
The own compact helper now stores immutable lifecycle JSON in a locked stream of closed gzip members with an atomically published seal. Readers validate encoded and raw size/SHA plus each logical path's exact bytes. A partially published member, missing seal, duplicate name, or ambiguous raw/compact representation cannot become success. Each lifecycle process has a unique sealed caller journal, retaining exact events and the logical caller/upload aliases; the manager closes its create segment before runtime finalization. finalize-remote.py obtains launch identities through that sealed consumer. The actual lifecycle provision gate reads compact ACK/closure/wait receipts, retaining PID, manifest and deadline SHA equality and actual status-zero/both-EOF requirements. consumer-tests.json records these checks and damaged/unsealed/ambiguous negatives. The original metadata artifacts remain retained; there is no existing-reclaim claim and the parent's 9.4 MB deficit is not erased by this representation.
Focused production upload tests (9), explicit-stage tests (2 methods / 8 upload cases plus invalid-directory negatives), API custody tests (13), emitted caller integration, compact consumer tests, and flock /tmp/wine-build.lock bash tools/build.sh passed. Accepted deadline/input fixtures are reused by exact SHA in reused-accepted-fixture.json, without repeating the 78b4 matrices. The run's owned-inputs.patch preserves new helper sources; Git and runtime-uncommitted.patch preserve source identity. No source/media archive, cache, reserve, DB, session, vendor-path or intentional runtime-binary change was made.
The fresh freeze used Git 012b482f9ba4935cf096f9ca3654184aebaac179, 696 runtime/helper paths and 114 unchanged original media references. Only the two newly published provider/custody files changed among inherited runtime paths; both runtime WASM hashes remain the parent's exact 04c534… / 29722b… identities. final-frozen-input-reread.json rechecks the whole closure. owned-inputs.patch SHA-256 c4e135f056d953cd7ab92da584ad2db2e6b8cfe0bf8c02865a8a7a3f871274c8 reconstructs all 20 new helper/test sources byte for byte; helper-patch-verification.json records that independent reconstruction. The final local evidence seal covers 60 files and 18 independently recovered logical lifecycle records. No source/media archive was made.
The independent four-hour watchdog was armed and observed alive before create. The actual create gate measured 1,500,708,864 bytes available, then created bx_a67gb47n at 23:31:45Z, initially expiring 03:31:44Z. Before provisioning could proceed, the actual watch measured 1,498,836,992 bytes, below the strict floor. The child was terminated and actually joined -15 with separate stdout/stderr EOF; its SIGTERM arrived before a durable provision event or successful remote closure was recorded. There are no observed PUT/command events, no successful provision, and no native launch or unique remote runtime artifact from this attempt. No upload was replayed. The loopback full-byte assembly qualification above remains distinct from live whole-provision success, which was not established. Final measured availability was 1,497,759,744 bytes. This live capacity failure is the concrete blocker; moving the bounded range off /home does not reclaim the parent's retained artifacts or guarantee headroom against other concurrent writes.
After local unique evidence was retrieved/reread and hash-verified, the manager normally stopped its own box. An independent GET and the manager both confirm ARCHIVED, expiry null, stop stop_6650964feb0efe52 completed, forced false, error null, at 23:33:22Z. Watchdog, manager and launcher each actually joined 0 with separate stdout/stderr EOF. The outer tool returned 0; its separate EOF channels are UNKNOWN rather than inferred from nested receipts. Historical canceled rome1.wav effects remain UNKNOWN/unreplayed; no preexisting box was resumed or altered.
Assignment 2 wheat/granary and new native food consequences remain unobserved. Next is actual sustained disk headroom, then one fresh independently watched private box, full joined provisioning with fresh hashes, and the ordinary compact tutorial/Victory/Clerk/Assignment 2 food route. No new GPU/FPS/audio, population/resource/clock/config-memory write, forced-call, unsupported native Save, or fabricated continuation claim is made.