One Singapore scene.
Two futures to compare.

Six rounds. B0 starts at clinic socket 0 with one charge; B1 starts with the courier with one charge. Batteries are clinic-only, retain their IDs and never recharge. Three powered engineer repairs activate grid power for both facilities from the next round.

Roles have fixed logical waypoints: medic at clinic may request/wait; engineer at workshop may repair/wait; courier at the spare waypoint may deliver-spare/wait. Request is a factual message, not a resource effect. Delivery changes the courier's logical waypoint to clinic and B1's holder to socket 1 in one committed round. Its short body movement happens afterward as presentation, not proof of unrestricted navigation or a physical inventory transaction.

1. Apply initial allocation or the one permitted reroute between rounds 2–6. Freeze one round input and base revision.
2. Collect one bounded proposal per role. Validate against the same frozen input; stage valid delivery. Earlier staged work must not make later role proposals stale.
3. Determine power from grid active at round start, otherwise assigned generator, otherwise a charged installed clinic battery in ID order B0 then B1. Batteries never power the workshop.
4. Apply at most one valid powered repair, while progress is below three. Add one downtime round if clinic is unpowered. Consume exactly one charge only if a battery supplied clinic power; generator/grid consumes none.
5. Reaching three repairs schedules grid activation next round. Deduplicate epoch/round/action IDs, append all effects atomically and advance one round. End after round six.

The proposed request budget is 20 seconds total per round attempt, measured and frozen at the first runtime gate. Allow at most one explicit retry, then reset or restart an explicitly approved labelled fixture/recorded run. Never mix modes inside an episode.

Canonical fixtures, no reroute

Courier waits in round 1 and delivers in round 2 in both fixtures. Medic may request without changing resources. A assigns the generator to clinic throughout and engineer waits. B assigns it to workshop, with engineer repairs in rounds 1–3, then waits.

B0 stays in socket 0; B1's holder becomes socket 1 from round 2. A never activates grid. B activates it in round 4; round 3's outage remains. Display a six-cell clinic-power timeline, downtime, repair, grid-active round, remaining charge and each branch's allocation/reroute. Do not invent a combined score.

These are arithmetic-checked proposed rules, not playtested balance or guaranteed live outcomes. At noon, after at most 20 seconds of explanation, a human should explain what they changed, what happened and what they would try next. If unclear, simplify controls/animation before adding detail.

Pin a small C++ value-state reducer, checkpoint records and runtime adapter. Gameplay owns the complete observation/proposal/provider path. Prefer one bounded three-role proposal batch through an approved existing endpoint; the executable never contains its API secret. Python is editor automation only. Keep the same chosen build configuration from package one through release, explicit default map and required asset references.

One initial checkpoint. Increase a non-rewindable epoch; stop/reset old visual jobs before restoration. Restore resources, allowances, logical waypoints and committed facts. A stays immutable; B gets fresh/stateless provider context seeded only from checkpoint/current-B facts. Clear or namespace branch-owned memory, notebooks, receipts, caches and provider workspaces. Diagnostic history and credentials never enter B's observations. Fence late model results, memory writes and visual callbacks at their authority.

Store positions as waypoint IDs or transforms relative to the fixed scenario anchor, never transient camera coordinates. Explicitly reset body transforms. Camera, physics and animation are projections, not rollbackable transactions. Recorded replay makes zero model calls. Inspectors show actual proposals, validation, committed effects and which roles are live; the medic explains/requests, courier delivers and engineer repairs.

1. Actual downloaded package opens without Unreal installed and completes a fixture FORK action. Required assets, locator, controls, quit/reset and credits work.
2. Canonical traces and charge conservation pass. Wait, illegal intent, malformed response, timeout, duplicate and late response have the specified effects.
3. Three restores reproduce state and role positions. Inspect B's exact request/memory sources: an A-only canary fact and receipt are absent, including after runtime restart.
4. Complete the whole A/rewind/B in the selected mode on the recipient setup. Record live waits, full-run duration and measured Laptop frame rate, targeting 1080p/30 with a documented lower preset if needed.
5. A submission baseline has an actual release ID, accepted mode, clean-start core acceptance and matching footage. An 11:10 launch shell is diagnostic only. If no qualifying baseline exists, say so.

Use existing private SSH/Tailscale and one scoped root per machine. A proven machine-local runner records job ID, PID plus start time, exact input SHA, owner, log and completion. Test one harmless disconnect/reconnect completion and actual GPU capture when permitted. Ordinary remote background launch alone is not persistence evidence. If unproved, a human operates long Desktop jobs; do not create a scheduler. No power changes or visible UI takeover are authorised by this page.

Freeze inputs and stop the prior writer before changing revisions. No live sync of open assets. Main transfers through the approved private origin or a verified Git bundle over SSH; LFS, packages and media are separate checksummed artifacts. Main must possess the result SHA and artifacts before acceptance. Capture the installed package on Desktop and transfer completed files with release ID, mode, size and checksum. Keep the accepted package and matching film on Laptop. Reconcile running jobs after disconnect; a timed-out lease does not prove a writer stopped.

• Use requested Astra Ultra where supported; verify Fast separately. Create peer tasks only through an actual callable API, otherwise named lead subagents with real IDs. If unavailable, prepare exact briefs for Lucas. Do not invent visible chats or automate UI task creation.
• Each committing writer gets its own worktree/branch, including leaves. One Git mutation owner per worktree and one binary-asset owner across devices. First prompts name absolute worktree, base SHA, plan revision/hash, contract, exact writable files, ignored status/evidence/outbox, machine lease and cutoff.
• Main alone writes the canonical manifest; unassigned paths remain Main-owned until explicitly leased. Leads receive the shared game contract plus their relevant packet and integration point, not the entire reference page.
• One pending immutable delivery/team: ID, base/result SHA, changed files, artifact hashes, actual checks, limitations and stopped-writer/job status. Main verifies receipt and integrates the exact commit. Reject binary conflicts for the owner to fix.
• Escalate after five minutes blocked or two failed fixes; access/ownership immediately. Stop expansion when two deliveries wait or the required Desktop job is queued. Deadline handoffs include useful verified partial work. Reuse actual task IDs after restart; never duplicate or take over an unconfirmed writer.

B = build/bundle, notices/hash, upload, evaluator download, required clean setup/prerequisites, full chosen-mode A/B and restore, plus margin. Distinguish first-time setup from cached updates; budget the actual judged route.

C = stop/switch to pinned package, launch/load, camera/roles, full demo/reset, one bounded retake, local playback, verified transfer and required development restart. E = remaining Laptop edit/audio/title replacement, encode, full local playback and margin. U = video upload, processing, evaluator access, full hosted playback and bounded retry margin.

X = min(14:20, 14:40 − U) is the completed local-video deadline.
M = min(14:05, X − E) is checked-media arrival.
S = min(13:35, 14:00 − B, M − B − C) is the latest start of the final Desktop release chain.

A three-second sample proves codec/bitrate only. By 12:30 time the full chosen-mode A/rewind/B and live waits; revise C and the full-run usability limit. Probe the approved host when permitted and revise U with rough-cut size. Reserve Desktop and human attention; finish Laptop package checks before E. Move leaf/candidate cutoffs earlier or retain an actual accepted baseline if the chain will not fit.

The baseline registry records release ID, SHA, initial-checkpoint hash, accepted mode, clean-start core acceptance and matching footage. A fixture release is a fallback for a live-only minimum only with Lucas's explicit acceptance. A shell or an unrecorded target is not a protected release.

Critical repair: accept only if now plus repair, affected validation, repackaging/reupload, required recapture/transfer and audio/title replacement fits recalculated M/X/U. Repair and verification never exceed 14:15. Unknown duration means retain the accepted release. A changed release gets a new ID.

Startup or late failure: an identified repair gets at most 15 minutes after 11:10. No launchable recipient package completing one deterministic FORK action by 11:25 means the original schedule is no longer credible. Choose a disclosed smaller deliverable with Lucas. No automatic late engine switch; the alternative must independently have passed readiness and recipient checks.

Remote or human shortage: reconcile jobs, preserve Laptop's accepted package/film and use human-operated long jobs if needed. Do not silently migrate heavy Unreal work or install another editor. With one human, use static shots, early narration and omit secondary inspection; recompute C/E before polishing.