Your own Singapore.
Two possible futures.

Six committed rounds. B0 starts at clinic socket 0 with one charge; B1 starts with the courier with one charge. Both retain their IDs and holders when empty. Batteries only power the clinic and never recharge. The player gets an initial generator allocation and one reroute before rounds 2 to 6.

Freeze the round state and collect all proposals against one revision. Stage delivery first. Derive power, apply repair, count downtime and consume only a battery that supplied the clinic. Commit the whole round once. Body movement follows as presentation, not a rollbackable inventory transaction.

Clinic priority is grid active at round start, allocated generator, then first charged installed battery by ID. Workshop uses grid or generator only. Three repairs activate grid next round, powering both facilities. Generator/grid consume no battery. All-wait or rejected-intent rounds still advance and consume normal clinic power.

Show the six-cell clinic timeline, allocation/reroute history, downtime, repair, grid activation round and charge. No invented combined score. These arithmetic-checked fixtures are not playtests or guaranteed live behavior. The complete contract and court-relative anchors are in the execution brief.

Identify each batch by branch, non-rewindable epoch, round, base revision and request ID; identify each role action separately. Stage all roles against one frozen revision and commit once. The server deduplicates effects and reconciles a lost acknowledgement from its receipt.

Valid waits and illegal role intents recorded as rejected waits still advance the round with normal clinic consumption. A malformed/incomplete batch, transport error or timeout commits nothing. Begin with a 20-second total attempt budget, measured at the runtime gate. Allow one explicit retry, reset or a Lucas-approved whole-run fixture reduction. Cancel stays responsive. Failed body movement reports a presentation error and settles to the committed anchor without changing resources.

Use one proposal batch where supported, otherwise collect three calls within the same 20-second whole-round attempt budget, including provider queues. Inspectors show each role's proposal, validation, effect and actual mode. Live, fixture and recorded labels remain consistent; recorded replay calls no provider. Never switch modes silently mid-run.

Record development/runtime authentication, model/effort/Fast and limits separately. Use the offered Astra capacity for useful work; verify runtime access and queue limits. Reduce development load if it delays runtime. Fast guarantees no latency. Live inhabitants are preferred product scope; the event listing does not explicitly require in-app inference. A fixture submission remains Lucas's scope choice.

The baseline court uses plain solid blocks and air, fixed weather/time, no autonomous mobs, invulnerable fixed-roster characters and known visual inventory. Scenario batteries are abstract records. General survival inventory, death, fluids, redstone, containers and block entities are outside the restore contract.

1. Pause input, increment the epoch and stop every old-epoch provider turn, script and visual controller job. The server checks the epoch before every deferred mutation. Confirm no old writer remains before restore.
2. Restore every cell in the explicit 16 by 16 by 16 cuboid, including expected air, and the fixed actor anchors and complete initial scenario state. Protect ground, controls and scenery. Do not use a reset that clears columns to world maximum height as a bounded restore.
3. Create a fresh branch context and provider session. Namespace or replace branch-owned notebooks, observed memory, receipts, recovery summaries and provider workspaces. Preserve credentials separately. A fresh chat alone does not erase durable memory. Keep branch A's diagnostics and result archive read-only and outside B's context.
4. Verify full cuboid state, outside sentinel blocks, three identities and resource totals before resuming. B gets a new branch ID. Restore the initial allocation allowance and compare at the same round.

The demolition mask contains at most 64 plain facade cells, is wholly inside the cuboid and excludes all functional stations and ground. A server command removes that mask and plays an effect without native explosion physics or entity damage. Allow it only while paused at the initial checkpoint; disable scored advance until the court has been restored.

A checkpoint manifest joins the pristine world snapshot, scenario snapshot, role-context seed, code/schema versions and hashes. Keep epoch and immutable branch results outside that rewindable bundle. If fast restore fails, a clean stopped-world reload of this complete bundle is a measured, labelled reduction. Never copy an active world as a verified backup. If even that fails, report the missing core feature.

1. Pin official Arnis v3.2.0 as a candidate until its executable passes. Check hash and --help. Keep Earth/Java, local projection, scale 1, rotation 0, normal height and flat geo-only. Disable optional Overture, canopy, external 3D, photo facades, extended height, lighting bake and LOD. Record actual bundled sources.
2. Use one complete local OSM XML or Overpass JSON input. A regional PBF needs an already working extraction and conversion route preserving referenced objects. Raw PBF and shoreline GeoJSON are not Arnis inputs. One owner acquires data; failed queries do not trigger parallel country requests.
3. A 64 by 64 disposable sample checks conversion, save/stop/reopen, blocks, dependencies and one character action. Before proposing country scale, inspect representative dense/high-rise and sparse/coastal output, including a multi-region sample with intended settings. Record phase times, peak memory/paging, scratch/output bytes and transfer cost. Samples screen candidates; they do not prove linear scaling.
4. The compact path shares 20 minutes across fetches, probes, retries and acceptance. Default start follows the 11:10 fixture proof. Deadline is the earliest of start plus 20 minutes, 11:35 and the next required device lease. Reserve at least five minutes or longer measured conversion/reconciliation time before it. One half-size retry fits only inside that allowance. 256 by 256 is the initial target; accept the largest completed compatible world or retain the fictional court.
5. One additional fresh candidate may start after action proof, ready input and measured spare capacity, without waiting until 11:35. Protect the compact world by 11:35. Stop wider generation by 11:45 or earlier for complete conversion, stopped reopen, court placement, fixed transform, absolute camera binding and fixture acceptance by noon. Miss that gate and the compact world ships. Freeze geography, interiors and bindings before the 12:30 chosen-mode rehearsal. No later country jobs or world replacement.

Use Arnis's own region processing in one job. Record its actual generated child directory. Place the court last through a proven interface and one fixed transform per release. Never append independent runs, merge region files or route district bounds through the arena structure importer. Wider scenery does not enlarge reset or tool bounds.

Record named latitude/longitude fields in degrees, source CRS, bbox order min_lat,min_lng,max_lat,max_lng, scale, vertical units, rotation, local origin and safe spawn height. At zero rotation, X is east and Z is south. Use the pinned generator's transform including its quantization; do not invent another formula. The district centre and two visible features must agree within one block plus source uncertainty. Keep the court's own relative anchors stable.

The generator writes an older Java chunk version. The accepted saved-and-reopened snapshot is the release input. Arguments · World writer · Acquisition · Fabric conversion context.

Keep the human-scale court at 1.0. Arnis scale 0.3 is a compressed object-bearing candidate; 0.05 to 0.1 is terrain overview, not a full city. Compression can remove useful small-building interiors. For the reviewed administrative rectangle, initial region-template writes are about 72 GiB at 1.0 and 6.7 GiB at 0.3 if every rectangle region is emitted. These are not final world, ZIP, storage or timing estimates. Its capped preprocessing grid remains about 102.5 million cells at both scales. Source calculations do not establish machine capacity.

Arnis interiors use a global --interior true switch and templates; some types and small footprints are skipped. They can add loot and block entities. Enable only on the one isolated bounded candidate with server-verified containment. Generated state stays outside scored restoration. Count an interior only after a street-to-room-to-exit walk with headroom and collision checks. Spectator views are labelled views. Court furnishings remain plain blocks with open entrances.

Travel uses a validated destination allowlist in the existing command/console flow. Check world/dimension, loaded terrain and safe arrival; keep Return to court available during loading. Stop pending role jobs first. Fence generic role primitives and director placement to bounded committed presentation. Reject use, pickup/drop, crafting, breaking/placement and persistent-state transfer across the scenery/court boundary. Off-court exploration is read-only: block persistent interactions throughout that area, as well as transfers into the court. Game mode alone is insufficient. Failed containment excludes generated interiors.

Record actual bounds, holes, source date and named offshore scope. A national-land claim includes Pedra Branca or labels its inset overview-only. Administrative sea bounds are not coastline. Distinguish source heights, floor-count estimates and defaults; imported counts do not measure all real buildings. No authentic floorplans are verified.

Default to one heavy job per device. Concurrent expansion requires measured CPU, RAM/paging, scratch/copy/archive disk, network and thermal headroom. Reserve the operator and Laptop editor. Extra hosted model capacity creates no extra machine lease. Never remove an accepted package or film to make a candidate fit.

Keep one logical project with a root on each device. Mini PC holds canonical source. Desktop uses a small fixed pool of reusable, exclusively leased checkouts and caches. Each job records device, absolute paths privately, input commit, world/profile hash, job ID, PID plus start time, logs and a completion record written after exit.

Use a proven machine-local persistent runner. At the opening gate, test one harmless job through a deliberate SSH disconnect/reconnect. A PID or successful SSH login alone does not prove persistence or GPU capture. If that cannot be proven promptly, humans launch the long game/capture processes while agents deliver files. Build no general remote scheduler.

One process owns a world. Import immutable snapshots into stopped instances. Stop the development server/coordinator before starting the capture copy; resume after its lease. Keep ports private and the bridge loopback-only. Camera paths are absolute-coordinate client-local files. Bind world hash, dimension, fixed court transform and player arrival anchor; verify the exact capture profile. Warm chunks with the operator nearby. Stop playback before travel/rewind. Camera stop does not return the player. Keep the Minecraft clock running for cameras while FORK rounds pause.

Reserve one active human game-client session. Disconnect Laptop play before Desktop capture unless a second legitimate account is available. Include client switching and login readiness in C.

Main transports committed source through the new private origin, or accepts a verified Git bundle over existing SSH when origin is unavailable. Required worlds/media and any LFS content travel separately with size and checksums. A handoff is received only when its exact commit and artifacts exist locally. Keep an accepted package and matching footage on Laptop. Never synchronize open worlds, credential directories or account state.

Reconcile task IDs, process start times and completion files after disconnect before retrying. A time-expired lease does not authorize takeover of an unknown writer. Use hidden job routes; visible play/capture is human-operated unless Lucas grants an explicit device/scope. No power changes or exposed agent bridge.

Authorised by Lucas, 13 September. During execution, Main may start, monitor and resume headless Codex CLI threads through ssh desktop and ssh laptop. This is an available worker route alongside local subagents and callable peer-task tools. Main stays on Mini PC and owns canonical integration, GitHub pushes and publication.

Read-only checks on 13 September found Desktop CLI 0.153.4 and Laptop CLI 0.154.0, both reporting an existing ChatGPT login. Both support exec, stdin prompts, JSON events and exec resume. No remote Codex task or model inference was started for this plan edit. A CLI session is tracked by its actual thread ID; appearing automatically in the app sidebar is not a requirement.

1. Place the work. Main can place World or Gameplay workers on Desktop and Cinematic workers on Laptop, or retain any worker on Mini PC. Count all local sessions, remote CLI roots and their children together: four owners initially, up to seven planned build sessions. Replace an owner's placement rather than creating a second active owner. Only Main launches remote root sessions; leads request further placements and may use their allocated local subagents. Leaves spawn neither subagents nor CLI workers.
2. Prepare before dispatch. Create a distinct branch/worktree for each writer under the chosen device's scoped project root, with the exact base commit present locally. Supply the current user instructions, accepted plan/contract, role, device, absolute worktree, exclusive writable paths, permitted Git metadata/outbox paths, dependencies and SGT cutoff in its first private prompt. Ban canonical/root writes and unleased game/world changes. Main's conversation, plugins, permissions and model settings do not automatically transfer across SSH.
3. Use existing access. Resolve the installed CLI and its already authenticated Windows user/profile. Keep credentials on that machine. Verify actual model, Ultra/Fast availability, effective tools and scoped write permissions in the runner's user context. Reuse the proven Java/toolchain helper when required. Desktop's version lacks the newer automatic --worktree option, so Main prepares Git worktrees explicitly on both machines.
4. Launch a persistent job. SSH starts the existing hidden, machine-local runner. The runner feeds a private UTF-8 prompt file into Codex stdin and records JSON stdout, separate stderr and the final answer in a private job directory. Use the approved scoped permission settings; an implementation worker needs write access to its leased files. Before its first implementation assignment, a bounded read-only Codex turn must survive the launcher SSH disconnect, finish, and resume by its exact ID. Fit this into the opening gate; otherwise keep that work on Mini PC and preserve the 11:10 game gate.
5. Track and resume. Record owner, device/user, worktree/branch/base SHA, prompt hash, runner job ID, PID plus start time, Codex thread.started ID, logs, deadline and exit completion. Keep session files. After disconnect, inspect that job before retrying. Resume only after the prior process is confirmed stopped, on the same machine/user and worktree, with the recorded ID and a new follow-up file. A dropped SSH connection is not permission to launch a duplicate writer.
6. Receive and integrate. Workers commit only their assigned branches and return the exact commit, checks and artifact hashes through their outbox. Main retrieves verified Git bundles or read-only fetches, plus required media/world files separately, and accepts a delivery only after it exists locally. Main controls publication. Remote jobs and any children obey the same 13:10/13:20/13:25 cutoffs or earlier measured stops; reconcile known process trees before releasing their leases.

The runner uses these command forms inside the selected worktree, with actual model/profile choices and scoped permissions resolved before launch. Feed the private prompt through stdin; write logs to separate private files. OpenAI non-interactive CLI documentation.

codex exec -C "<leased-worktree>" --sandbox workspace-write --json -o "<job-folder>/final.txt" -

# After the prior process has stopped, in the same worktree/user:
codex exec resume "<recorded-thread-id>" --json -o "<new-job-folder>/final.txt" -

Every process must fit the existing machine reservations. Multiple light Codex sessions can coexist only with measured headroom; builds, generation, game capture and editing/export retain their leases and one-heavy-job default. All devices share the actual account/service limits. This authorises headless worker execution, not power changes, visible app control, credential copying or earlier game implementation.

Every concurrent committing writer, including receiving leads, gets its own branch/worktree. First prompts contain resolved absolute paths, base SHA, plan/contract hash, exact existing-file leases, inputs, acceptance and current absolute deadlines. Main derives each owner's packet from this self-contained brief. Worktrees do not isolate shared worlds/caches: lease those separately, with job ID, PID plus start time, input/settings hashes, output/cache paths, stop time, log and observed completion or NONE. World alone owns generation jobs: at most one optional candidate and one heavy job per device under measured leases. Main alone admits candidates and changes accepted release.

Main alone writes the canonical manifest. Each team gets a named ignored .work/fork/<team>/ status/evidence/outbox directory in its worktree. Escalate a blocker after five minutes or two failed repairs; access/ownership problems immediately. Keep at most one pending immutable delivery per team. Stop adding leaves when two team deliveries wait or a required runtime job queues.

Handoffs contain ID, exact base/result SHA, contract version, changed paths, world/camera hashes, focused checks, limitations, stopped-writer and remote-job status. Main inspects and integrates the exact received result. No binary/world merge by guesswork. On restart reuse actual task IDs, reconcile jobs and preserve unknown writer leases. Deadline stops return useful verified partial output.

Record conservative first estimates by 11:35 and replace them with full-route measurements by 12:30. A three-second clip estimates codec/bitrate behavior only. The synthetic codec/transfer measurements do not establish the real capture, editing or upload budgets.

• B: bundle/build, hashes/notices, upload, recipient download, actual clean install and prerequisites, full chosen-mode A/B with restore, plus margin. Distinguish a cached update from first-time judge setup.
• C: stop/save, world/profile switch, launch, role/provider readiness, camera setup, complete real demonstration, checkpoint reset and one retake, local capture check, verified transfer and any required development restart.
• E: remaining editing, audio/title replacements, final encode and full local playback, plus margin. Narration and the rough edit already exist.
• U: video upload, host processing, evaluator-access check, full hosted playback and a bounded retry margin.

X = min(14:20, 14:40 - U) is the export deadline.
M = min(14:05, X - E) is final media arrival.
S = min(13:35, 14:00 - B, M - B - C) is the latest start of the serial final delivery path.

W = min(13:10, S - 25 minutes), L = min(13:20, S - 15 minutes) and H = min(13:25, S - 10 minutes) are worker stop, lead acceptance and handoff. They move earlier together and do not reopen geography. Reserve all C on Desktop/operator. A protected delivery backup is a recipient-tested package plus its complete matching 90-second film, played locally on Laptop, with U reserved or complete. Raw clips do not qualify. Keep a tested smaller export and approved alternate upload route.

For the single early candidate, set Dmode = min(12:30, L), also respecting earlier runtime/media reservations; Dgeo = min(12:00, W, Dmode - Rmode); Dgen = min(11:45, Dgeo - P - V - R0 - K, Q - K). Start only by Dgen - G. G is bounded acquisition/generation; P is conversion, stopped reopen, immutable preparation and transfer; V is court/camera/coverage/interior and full fixture acceptance; K is stop/reconciliation plus margin; R0 reserves compact-world recovery and remaining acceptance; Rmode reserves chosen-mode checks, three restores and full rehearsal; Q is the next conflicting required lease. Unknown durations deny expansion. Failure uses R0, quarantines output and ends heavy expansion for the event.

Accept a critical repair only when its repair, affected validation, repackaging/reupload, required recapture/transfer and audio/title changes fit the recalculated M/X chain. Repair and verification never run after 14:15. If a duration is unknown, retain the prior accepted release with its actual ID. Never relabel an 11:10 launch shell as that fallback.

If Desktop remains unreachable, first preserve the files already on Laptop. A local Laptop runtime/capture route may replace it only after a measured launch, provider and capture check and a recomputed editing reservation. No automatic engine switch or last-minute installation is hidden inside the schedule.

Record by section, with two seconds of clean room tone before and after each take. Speak briskly and naturally; fit each line within its slot without stretching the full interval. The numerical base script requires the accepted labelled fixture or a captured live run with those exact outcomes. Keep one runtime mode throughout.

Record the needed alternatives in the same session

Final captions follow the recorded take. Use at most two short lines, reserve a clear caption area and keep them off the comparison values. Put map/data credit beside the corresponding shot and full asset notices in credits.txt and the publication description.

1. Prepare now: this script, the exact cut, fallback lines, card copy, sound direction and acceptance. Create new project media and the edit template within the event window unless further host guidance permits it earlier.
2. By 10:45: Main leases Cinematic's edit/output folders, names the capture operator and narrator, and records the final MP4 as Cinematic's responsibility. Mini PC coordinates; Desktop records the game locally with OBS; Laptop assembles and exports.
3. By 11:35: prove one 15-second edit on the actual Laptop route using existing tools: trim/join, a title, narration over music, export and local playback. Use existing FFmpeg for agent assembly if it passes. Otherwise the partner uses existing Resolve while the lead owns shot selection, timings, assets and final acceptance. End tool experiments at this gate. Reserve this work around required game tests. Choose a suitably licensed instrumental with its credits, or commit to game sound and sparse accents.
4. By noon: lock the accepted-scope script, title and scope cards, locator, mode labels, credit layout, soundtrack and the complete 90-second edit structure. Internal temporary footage stays clearly marked. Bind camera cues to the accepted world using existing controls.
5. By 12:30: accept the timed narration, full capture rehearsal and rough edit, then recalculate the existing capture/edit/upload budgets. Capture the complete causal A/rewind/B sequence first. Record scenic and optional play shots only after it is safe.
6. Finish the film: insert checked footage, replace every temporary asset, fit the mix and captions, export, play the whole local film, then hand the finished package to Main for publication and complete hosted playback by 14:40. Earlier measured X/M deadlines still apply. No editing is left for Lucas at submission.

A human still supplies narration and operates capture when existing access requires it. The lead packages the complete video rather than stopping after production instructions. If Desktop screen access remains unavailable, prove Laptop-local game/capture performance early and reserve capture and editing serially. Resume no deferred sign-in workflow automatically.

• fork-demo-1080p30.mp4: exactly 90 seconds and 2700 frames, H.264 with AAC 48 kHz; measured local and hosted full playback, clear sound, readable UI and no temporary cards, missing media or private information.
• fork-demo.srt, final voice WAV, asset/data/Agent Arena credits, and an editable project or edit manifest with the exact render command. Captions are also visible in the submitted film.
• film-manifest.json: accepted code/world/mode, input clip IDs and hashes, actual source in/out points, output hash, repository/video URLs, music/asset source and licence, and local/hosted review status. The submitted repository must be accessible to judges; Main manages its approved visibility/access.
• Use a restrained grade, consistent audio and a legible title/end card. Target −16 LUFS integrated and at most −1 dBTP. Voice stays clearly above music. Rewind effects support real forward-playing reset footage; the locator is an explicit static-map cut.
• The ten-second comparison remains legible at intended viewing size. If optional footage is unavailable, fill its reserved block with accepted court views. Keep the complete film at 90 seconds. No new game feature, rendering stack or generated in-between footage is needed for this cut.

Headless codec and transfer checks are useful preparation. Actual OBS gameplay capture, narration quality, Laptop edit/playback and the final film have not passed yet. The existing measured deadline calculation governs all later changes.