Called fixed. Then looked at from where the player stands
One developer and a crew of AI agents built DECOMMISSIONED in four nights. This is the record of what was built, what was claimed, what the evidence showed, and what changed.
A game by Thendo Mukhavhuli, solo developer. Studio: Downstage. Made for the Epic AI MegaJam 2026.
The cut content is your power
The creatures the Programme approved have turned and killed the undercity’s lights. The ones it cut are still loyal, sealed in vaults.
As Zee, you push down dark streets, restart each block’s power and hold while the lamps come back. Then you free the creature inside the vault and bind it to your shadow, and take the Spire before dawn. That is the Director’s Cut.
Unreal Engine 5.8 · Windows · a run is about 20 minutes, drop-in to dawn.
PushDark streets are deadly. The turned machines spawn where the lamps are out.
HoldRestart the block’s power and defend it. One clock, 42 to 196 seconds.
RelightThe lamps come back. Light is safety, and people return to the street.
ReinstateOpen the vault, free a cut creature, bind it to your shadow.
The story, painted
The perfect ones, the machines the board approved, have turned.
The cut ones wait in the vaults.
The Editor decides what makes the cut.
Light is safety, and people come back to the street.
Painted by the art lane on Sunday, for the last build’s loading screens and the Editor’s comic.
Controls
Action
Keyboard and mouse
Controller
Move
WASD
Left stick
Look and aim
Mouse
Right stick
Sprint (uses stamina)
Shift
L3
Jump
Space
A
Dodge roll
Ctrl or C
B
Fire, or confirm an aimed sign
Left mouse
RT
Aim down sights, or cancel a sign
Right mouse
LT
Reload
R
X
Melee strike
V
R3
Interact, pick up, swap weapon
F
hold X
Throw a flare
G
Y
Trace the way to the objective
T
Right stick up
Pistol, primary, heavy
123 or Mouse wheel
LBRB
Warden, Lull, Lantern, Chorus
QEZX
D-pad up, right, down, left
District map
Tab
Back
Pause
Esc
Start
Signs are aimed: press the key, place the ring, then fire to cast. From the key table of candidate 7; it is checked again against the build that ships.
Thendo Mukhavhuli is the director here: he decides what makes the cut. Agents never wait on a question: they log it, take the simpler option, and keep building.
That is the house rule the whole project ran on. He played every build that mattered, said what he saw, and went to sleep. The agents worked in separate lanes on separate branches, and a judge with no write access to the game scored each build.
Thendoafter the first playtest, Thu 12 Nov, 23:00“We don’t have a game yet.”
Thendoafter playing candidate 5, Sun 15 Nov, 12:49“The style has been established… Now we have to put a bow on everything.”
3 a.m. Four nights of building a street. Painted by the art lane for this record.
Four nights
Thursday 12 to Sunday 15 November 2026. Each row is one stretch of work, with what was said at the end of it. Times are SAST.
Thu12 Nov · day
The version that got cut
The first concept was a container-port defence game. By 17:20 it had a casting screen, an audio system and a packaged build that passed every check. A critic agent scored a recorded night: Fun 2 out of 5.
The first agent on the desktop wrote a test bot, a fake player that plays a whole night. Its first run proved the flare gun had never hit anything. “Verified” had meant compiled, not played.
DECOM_AUTOTEST CHECK F FAIL flare shots=30 damaging+stunning hits=0
Thendofrom the road, 17:51“Realistically I cant even see what’s happening.”
Thu22:30 to 07:12
Re-cut from a phone, rebuilt overnight
Thendo played it and cut it. Claude put each choice to him as a multiple-choice question; he answered 14 of them from a phone, and at 23:55 the answers became a spec every overnight agent had to follow.
Eight lanes, one integrator. Each lane had its own branch, a list of files it owned, and a hard stop. At 05:45 Windows Update restarted the PC and killed the 06:00 build. Every lane had pushed, so nothing else was lost. The morning build was packaged at 07:12 and played with real keyboard and mouse before he woke.
SPEC-NIGHT.mdthe one rule“If anything here is unclear, do not ask and do not wait. Log the question in your lane’s QUESTIONS.md, take the simpler option, and keep building.”
The cast, generated and rigged in Hyper3D Rodin that night. The rig test failed once, the error was read, and it passed: 89 Unreal-named bones.
Fri13 Nov
Played to dawn, then three crashes
At 09:12 Thendo recorded the first human run of the new game, start to finish: 25 minutes, all three vaults, the boss, the dawn card. 19:17 run time, 410 hostiles, 3 of 3 vaults.
The afternoon build crashed on him at 17:26, 17:31 and 17:34. All three were one stack: a garbage-collected material in the hit-effect pool. The bots had never died there, because a bot does not play for fifteen minutes the way a person does.
The gate that came of it: nothing reaches Thendo until two full packaged runs, the soak, finish with zero crashes and zero ensures.
Dawn · from Thendo’s own recording, 13 Nov.
Sat14 Nov · 00:00 to 07:55
The night the measurements argued back
The judge lane is a separate session with no write access to the game. On Saturday morning it said ship, scored the build 25.5 out of 35, and listed the misses as plainly as the passes.
The night’s work was an argument about numbers. The director was corrected three times by his own agents, in writing. He blamed a repaint for colours that were not in the paint script. He relayed a figure nobody could find in a committed note. And a wrong conclusion drawn from a true log line travelled through two lanes before the lane doing the work caught it.
The rule the day produced“A correction is a claim like any other, and the standard has to apply to it too.”
A hold in Saturday’s release candidate. Zee spoke 104 of her own lines in this run. The build before it had four, and all four were the radio.
Sat19:00 to 23:10
Eight instruments that could not see
Three hunts found the same fault: an instrument reported confidently on something it could not see. A painting drew at 3% opacity for two days. An enemy threw away the one return value that would have told it it was failing. And eight of our own measuring tools did it to us.
The seventh was the author of the dev log, who wrote “this build records no frame-rate data” after searching the log for fps. The log records frame_ms.
FX laneits own note, 20:31“Five instruments reported confidently today on something they could not see… Four of my five wrong answers today came from that, not from the engine.”
The rule: before you believe an instrument, make it prove it can see the thing you are pointing it at.
Sun15 Nov · 00:37
“It’s still really lacking”
The director played the whole game, start to credits, talking for 33 minutes. The soak had passed: 202 checks, zero crashes, 187 fps at 1280×720. None of that is what he saw.
The log agreed with him, in numbers the gate had never been asked for. Wall-running, cloth simulation and extra bosses were cut the same hour, in writing, because each is a system and not a fix.
hold length, his run:
Market 48 s → Foundry 302 s → Canal 563 s
path failures from ground level: 1,074
(he stood on a crate; nothing could reach him)
Thendoend of the run“It’s still really lacking… lacking a lot of depth… the graphics don’t look so good to me any more.”
The climax, as built on Saturday night. A white, untextured boss. The texture fix existed on an unmerged branch.
Sun05:00 to 12:33
Six candidates before lunch
At 05:03 he gave his orders by voice and went to sleep: no time limits, “build until you’re happy”, do not rush. Claude Fable 5.2 took over the Claude lanes that hour. Between 07:04 and 12:33 the integrator packaged six candidates.
Each time, something was called done from the nearest evidence, and then someone looked from where the player stands. The cases are below, and every build is listed after them.
People come back when a district is cleared. Five townspeople made in Rodin; a sixth was dropped because his face read as a ghost under the teal light.
Sun12:25 to 12:49
He plays candidate 5
The first time a person played a Sunday build. His verdict: the systems work, he likes the townspeople and the map, and what lets it down is finish: Zee’s animation, the interface, the intro and cutscenes.
He asked for the building labels and automatic guide pulses to go, for a boss death that says what happened, and for the intro to be rebuilt so nothing rushes. Those are the brief for candidate 7.
Thendoplaytest notes“The thing I’m most disappointed about… is definitely Zee’s character animations… If the animations get fixed on Zee, mostly the game is good.”
Candidates 7 and 8 are not built yet; each has a row waiting under Every build. He records the trailer on one of them.
Same camera, before and after
A fix is not judged from a close-up. These pairs were shot from one camera position, before the change and after it.
Called fixedCandidate 3
The white boss, fixed twice. At 07:04 it was “seen textured in packaged frames”. Those frames were close-ups. From fight distance it still read white, and its ring and health bar were orange, the colour that means lamps. See case 16.
Ink too dark×12, cold rim
Outlines that were there, but invisible. At that point in the render chain the scene colour sits at about a tenth of display value, so every ink colour was ten times too dark. Thursday night, case 4 in the PDF. These frames show Zee's retired look from that build.
Called fixed Every claim gets checked from where the player stands. Painted by the art lane for this record.
Called fixed
Twenty-one times something looked finished and was not, or looked broken and was not. Each row starts with the claim. Press Look to see the evidence and what changed.
0 of 21 looked at
No cases from these days.
Thu 12 Nov · File 01Claim
The gun that had never hit anything
Claimed
Antigravity built the foundation in 78 minutes, 15 tasks, each one marked “verified”.
Evidence
A fake player that plays a whole night headless was written that afternoon. Its first run:
CHECK F FAIL flare shots=30 damaging+stunning hits=0
Changed
The cause was a collision channel and the fix was one line. The lesson held for the rest of the jam: “verified” has to mean played, not compiled.
Thu night · Case 3Claim
“Blew out to pastel”, three times
Claimed
The painterly post-process does not work. It failed three times and was set aside.
Evidence
On the fourth try the agent read the rendered game’s log. The headless runs never compile shaders, so they had never said a word.
M_PostInk: Failed to compile Material ... Missing Clamp input
Changed
The Clamp node’s input pin has no name, so Unreal had been silently swapping in its default material. Fixed, and a rule went into the log: always search the rendered run for “Failed to compile Material”.
Fri 13 Nov · File 05bClaim
Three crashes in fifteen minutes
Claimed
The build passed every autotest and every bot run. Nothing had ever crashed.
Evidence
Thendo played for fifteen minutes and it crashed at 17:26, 17:31 and 17:34. One stack, all three times:
The hit-effect pool held its materials in plain C++ pointers, and the garbage collector freed one that was about to be swapped back in.
Changed
The pool’s materials are now held where the collector can see them (commit 8cf7f08). And a new gate: two full packaged runs, deaths and all three holds included, with zero crashes and zero ensures, before a build reaches him.
Sat 14 Nov · Case 7Claim
The protagonist who never spoke
Claimed
The voices are not working. Suspects: a cooldown, the mix, or missing audio files.
Evidence
All three suspects were wrong. Nothing was broken. A keep list was successfully filtering almost every line out, and reporting success each time.
VO skipped × 48 (run 1), 49 (run 2)
reason = "not on the keep list", every one
Zee's own lines: 4 in a 15.6-minute run
Changed
The bar was raised, and every line was tagged by speaker so the count would be a count. Next build: 104 of her own lines, 30 distinct. By the new tags the original four were all radio, so the honest baseline was probably zero.
Sat 14 Nov · Case 9Claim
“Done and pushed, all 7 jobs landed”
Claimed
A lane reported itself finished at 04:55.
Evidence
Ten minutes earlier the integration autotest had found the rebuilt district had no working navmesh: 11 checks red.
master L_Undercity.umap RecastNavMesh ×0
lane L_Undercity.umap RecastNavMesh 4 → 0
Changed
The lane had pushed three separate commits on purpose, so the two good ones shipped while the map was held back. It landed fixed at 06:00 (9d9a5ce). The rule: a lane reporting itself done is making a claim. The autotest is the result.
Sat 14 Nov · Case 11Claim
A true observation, a false conclusion
Claimed
The comic’s voice lines were never imported. The log said so: SkipPackage: /Game/Decom/Intro/VO/mid1_a, “does not exist on disk”.
Evidence
The log line was true. The conclusion was not. The audio had been imported into a different folder, and the comic was asking for the wrong path. The judge had checked only the folder the error named, and the director relayed the conclusion as fact. The story lane went and looked, and found all nine assets already there.
Changed
The load path was fixed, and the nine files were not duplicated. The judge then re-checked its other path-based claim by the same method, and rewrote its gate check so the correct fix could not be scored as a failure. Re-run on the same log, the new check still found 7 of 7 silent, so the rewrite had not loosened it.
Sat 14 Nov · Case 12Claim
The painting that was always there
Claimed
The Warden’s painted ground disc does not draw. Opacity was tested and ruled out.
Evidence
The material was cloned from a glass shell whose opacity is built on Fresnel. A flat quad facing the camera has no grazing angle anywhere.
opacity = alpha × 0.06
the ruling-out test, alpha raised to 0.95:
0.95 × 0.06 = 0.057, still invisible
It had been drawing for two days at three percent.
Changed
One frame with known-good controls beside it under the same light answered what two days of one-suspect-at-a-time tests could not. A test that cannot produce a visible pass cannot produce a meaningful fail.
The frame that ended it. Captured before the HUD rebuild.
Sat 14 Nov · Case 13Claim
The enemy that asked 180 times
Claimed
The Foundry hold will not end because enemies are stuck in the map’s geometry. Four careful map measurements came back clean.
Evidence
All four were correct and aimed at the wrong place. The Dimmers had never moved. Each asked for the same impossible path once a second, and threw the answer away.
AI->MoveToLocation(Lamp, 120.0f); // result discarded
At the end of one such path: two buildings with a 12 cm gap. A pawn is 84 cm across.
Changed
Diagnosed, not fixed, when that build was packaged. What shipped that night was a 12-second recall that cleans up after it. Foundry went from 0 lamps snuffed to 14, and the hold ended.
Sat 14 Nov · Case 14Claim
A sourced number with the wrong label
Claimed
“This build records no frame-rate data.” Written into the submission pack by the author of the dev log.
Evidence
The search had been for fps. The log records frame_ms: 669 samples, in the file already open. And the recovered figure, 187 fps, was measured at 1280×720 where the award text said 1080p.
Changed
Every frame rate on this page carries its resolution. A sourced number with the wrong label is worse than an unsourced one, because it looks checked. This was the seventh of eight instruments that could not see that night.
Sun 15 Nov · Case 15Claim
The restart that was three clocks
Claimed
The Canal hold failed and started again. “Are you kidding me? We have to do this again?”
Evidence
It never failed. It was three stages chained end to end, and each drew its own clock. “Vault opens in 8” was true of stage two only.
defend 125 s + dimmers_relight 250 s + surge 187 s = 563 s
Changed
One clock for the whole hold, and shorter stages (commit 2d2b2d2). By the test bot in candidate 4: 42, 124 and 192 seconds. Not known: whether two and three minutes still feel hard.
Sun 15 Nov · Case 16Claim
The white boss, fixed twice
Claimed
07:04: “Boss seen textured in packaged frames.”
Evidence
True of the frames looked at, which were close-ups. Frames taken from where the player fights showed it still white in candidate 2. The same night, the raised pistol looked right from the side and was hidden behind Zee’s own back from the game camera.
Changed
A darker diffuse and an emissive kept to the core (69e6426), checked on the same four cameras before and after. The slam ring and boss bar went from orange to cold cyan-white. Judge it from the player’s camera or you have not judged it.
Sun 15 Nov · Case 17Claim
Four checks stopped running, and nothing failed
Claimed
Candidate 3 passed its packaged autotest: 210 checks, 0 failed.
Evidence
The judge compared check names against Saturday’s and found four missing. They sat late in a probe chain that needed thirteen more seconds of hold, and case 15 had just made the holds shorter. They never ran, so nothing failed.
The judgeits own scorecard“I gave 161733 a 27.5 on Saturday. Thendo then played and found a white boss, a 9-minute hold and overlapping voices that my gate hadn’t caught. As he played it, Saturday’s build was a 25.0, not 27.5. I’m re-basing to that.”
Changed
The guard now fails every unrun check by name. Candidate 4: 214 checks, 0 failed, all four back. The judge also found its own script had under-counted hold time, wrote “my script is wrong” in the scorecard, and corrected it. Nobody asked it to mark itself down.
Sun 15 Nov · Case 18Claim
Finished, and never run
Claimed
Cursor’s interface batch: a status file describing each fix as done. Antigravity’s late art: delivered.
Evidence
Cursor’s eighteen files were saved between 05:36 and 05:41 and then sat uncommitted, uncompiled and unrun for four hours. One claim was false as written: the view still flashed gameplay after the ending. In Antigravity’s art, one sign is misspelled, the arrows are orange (the colour that means lamps), and two found notes named Zee as handler #09 when her jacket says 17.
Changed
The world lane took Cursor’s diff read-only, applied it, and checked every claim in a frame or by driven input. The art was reviewed image by image: the sky, district plates and a child’s drawing went in; the rest went back in writing.
As delivered. The second sign reads “LOCK EASIN”. These looked finished at thumbnail size.
Sun 15 Nov · Case 19Claim
Passed in the editor, failed in the package
Claimed
The mouse wheel reaches the last settings row. The test passed at 1080p and 1440p.
Evidence
The same test in the packaged build failed. Each scroll slid a new row under the resting pointer, and the row’s hover took the selection back. The editor run had passed because its window was hidden. The test had never had a pointer on the list.
Hover is locked while the wheel or keys drive the list. The test now puts the real pointer on the list, and a switch restores the old behaviour so the failure can be reproduced on demand.
Sun 15 Nov · Case 20Claim
A boss that died in 29 seconds
Claimed
07:46: soak passed, “boss beaten in 29 s”. Reported as a pass.
Evidence
Twenty-nine seconds is not a climax. Three creature stuns landed back to back, each restarting the boss’s recovery, so its first attack came 14.5 seconds in. And the slam only triggered within 13 metres. The bot stands at 23. It had never seen the slam.
Changed
Repeated stuns shorten and then stop working for a while, and health cannot drop past each quarter until the boss has finished a set number of attacks. Candidate 4: beaten unaided in 67 seconds. Candidate 5 adds a check that the stun chain cannot kill it before 90.
Sun 15 Nov · Case 21Claim
Two freezes, one hard drive
Claimed
Candidate 2 has a hitch: a 15.2-second freeze in its autotest and a 27.7-second one in its soak.
Evidence
The integrator read the Windows System log before changing anything.
storahci 129: Reset to device (Disk 0 = D:)
07:19:27 autotest freeze, 15.2 s
07:30:21 soak hitch, 27.7 s
same build, copied to the SSD: 0 hitches
Changed
Nothing in the game. Every gate since runs from the SSD. A freeze charged to the build would have cost a morning of looking for a bug that was not there.
Sun 15 Nov · Case 22Claim
Townspeople: switched off, then made properly
Claimed
The code that brings people back to a cleared district was merged before 07:00.
Evidence
It shipped switched off in candidates 1 to 4, because the only figures to hand were box-and-cylinder dolls. The lane that placed them wrote: “six of them under the new light are worse than none.”
Changed
Six people were made in Rodin from text prompts. Five were accepted and one was dropped. They were regrouped as a trio and an adult with a child, and ship in candidate 5. After playing it, Thendo asked for more variety among them; that is in the brief for candidate 7.
Built and switched off: the first figures.
Sun 15 Nov · Case 23Claim
Three Zees, and a fix held for the human
Claimed
Zee’s look can be fixed to match the comic. The branch is built and passes the autotest.
Evidence
Zee was three people: an afro and a cream jacket in the game, a braided bun and green jacket in the comic, a third on the draft cards. But the afro was the director’s own pick, and the green is measurably harder to see on an unlit street (contrast 67 down to 37 on the measure used).
Changed
Nothing, until he chose. The agent that could finish the job stopped where the job became a choice, and made him one comparison from one camera. He approved the new look himself on Sunday morning: green jacket, face stripe, braided bun. It is in candidate 6.
The comparison made for the director. Same camera, same spot, same light.
Sun 15 Nov · Case 24Claim
Thrown out of the game, twice
Claimed
Thendo was playing candidate 5 when the game dropped out of fullscreen, twice in eight minutes. It looked like a fault in the build.
Evidence
His session log gave the two moments to the second. Each one matched a test launch by the integrator: a packaged autotest and an unzip check, both started with a visible console window. A new window takes focus, and exclusive fullscreen lets go when it loses focus.
12:30:37 out of fullscreen · a test launch opens a console
12:38:36 out of fullscreen · a test launch opens a console
Changed
Nothing in that build. Test launches now start hidden, and nothing launches at all while Thendo is playing or recording. Candidate 7 switches fullscreen to borderless, which does not drop when another window opens.
Sun 15 Nov · Case 25Claim
Half the frame rate, and the build was not why
Claimed
Candidate 6’s soak passed, but its frame rate was about half of candidate 5’s. The new interface batch was the obvious suspect.
Evidence
The first two minutes of the run were at the usual rate. The drop began at 13:12. The directors’ room was transcribing a recording on the same PC from 13:12 to 13:27, and said so when asked.
Changed
The figure is void and is not printed here. Candidate 6’s row reads “not measured on a quiet machine”. Candidate 7’s soak runs in a quiet window, with four minutes of candidate 5 alongside as a yardstick.
Sun 15 Nov · Case 26Claim
The menu test that quit the game
Claimed
14:35: nobody has seen candidate 6’s Settings page. The packaged menu test quits the game straight after the title screen, and Cursor’s menu rework is suspected.
Evidence
The test chose its row by position: move the selection, press. Once a checkpoint file exists the title screen gains a CONTINUE row, the rows shift, and the same move landed on QUIT. The log shows the game handling an exit command. The test had pressed the button it was told to.
Changed
The test now finds a row by its label. Run again on the same menu at 15:10, it opened Settings and passed the wheel, click and slider checks. The menu was not changed.
The Final Cut “Handler, meet the Final Cut.” The Editor, on the radio. Candidate 7, packaged build, played by the test bot.
Every build
Each row is a packaged build and what the gate recorded for it, including the checks that were not run. Open one for what it carried and what it missed.
Carried
The first build held to the two-run soak gate.
Zee speaks: 104 of her own lines in a run.
Enemy health bars, after a material fix was rejected on evidence.
Missed, in the judge’s words
Zee vanishes in one Market sightline at about 83 m.
The Foundry route is too dark: 48% of the frame crushed.
Minutes 10 to 15 add almost nothing new.
Carried
The rebuilt HUD and the Cut Features draft.
The Dimmer recall that lets the Foundry hold end.
Missed
Scored 27.5 by the judge. Then the director played it and found a white boss, a nine-minute hold and overlapping voices. The judge re-based its own score to 25.0.
“It’s still really lacking.”
Carried
One clock per hold, shorter stages.
The boss texture, the raised pistol, the smaller HUD.
Zip 1,067.8 MB.
Missed
The boss was “seen textured” in close-ups only (case 16).
Packaged without a soak.
Carried
The first Sunday build with a soak.
Missed
Two freezes that were the D: drive resetting, not the game (case 21).
The boss still read white from fight distance, and died in 29 seconds (cases 16 and 20).
Carried
The boss fixed a second time, checked from the fight camera. Cold ring and bar.
The arena dressed with 74 kit pieces.
Missed
Four checks had stopped running and nothing failed (case 17).
The bot did not beat the boss unaided: the soak ended the fight itself at 7% health after 80 seconds.
Carried
All four lost checks back, and a guard that fails any unrun check by name.
Cursor’s interface batch, rescued and checked claim by claim.
The boss beaten unaided by the bot in 67 seconds.
Missed
The packaged mouse-wheel test failed at 2560×1440 (case 19).
The credits showed a literal “[NAME]”.
0 of 6 holds pass the judge’s contact-and-pressure test.
Carried
Townspeople, the wheel fix, raised boss health gates, a deep-violet way-finding pulse.
Zip 1,105.2 MB; the townspeople add 22.5 MB.
Missed
No judge scorecard on file.
The integrator could not verify townspeople or the cheer in a packaged frame of its own.
Thendo played it, 12:25 to 12:49: the systems work; Zee’s animation, the interface and the intro do not hold up yet.
Carried
The painted night sky, enamel district signs, and Zee’s approved look.
Cursor’s second interface batch. It passed the autotest on its third run, on a quiet machine.
Unzipped to a fresh folder and run from there: 215 / 0.
Zip 1,167,110,616 bytes. On the launcher from 14:15.
Soak frame rate: not measured on a quiet machine. Another job was running on the same PC (case 25).
A first package at 12:33 (122509) left Cursor’s batch out: one timing check read 141 ms against a 100 ms bar while Thendo was playing on the same PC. A second run failed during a D: drive reset.
No frame of the Settings page from this build: the menu test quit the game (case 26).
The remaining frames and a windowed launch were skipped and move to candidate 7. No judge scorecard on file.
Carried
All four lanes merged with no conflicts.
No ground arrows, the T chip, lamp cones at the default quality.
Missed
Thendo played it: Zee’s animation still the weakest part.
The trailer cut from it scored 34 out of 50, below the pass mark.
Carried
Only fixes from Thendo’s candidate 7 notes.
Zip 929 MB, under itch’s 1 GB limit. The title reads DECOMMISSIONED.
Missed
Thendo: “Everything is good. We’re still just struggling with Zee’s animation.”
Carried
Candidate 8 plus Zee’s gun holds: rifle and shotgun stay level after shots and through reloads.
Seen from the front, Zee is still off her painted look: skin tone, a smooth bun, the face stripe. Next after the jam.
Scores are the judge’s, out of 35; a dash means the judge did not score that build. Autotest is checks passed / failed. Soak frame rates are median / 10th percentile / minimum at 1280×720, played by a test bot; a capture run of candidate 3 at 1920×1080 with a screen recorder running measured 156 / 144 / 73. Hold times are the bot’s unless the row says who played. Candidate 6’s soak frame rate was not measured on a quiet machine, so none is given.
The crew
Eight lanes plus a judge, each its own session on its own branch. The judge has no write access to the game.
Thendo decided
Agents decided inside the spec, and logged it
Cut the port game after playing it
Rig five characters on one human skeleton
All 14 direction choices, by phone
fal instead of OpenArt for sheets and panels, to save shared credits
“Looks first, except the controls”
Pick score takes by measurement, because nobody could listen overnight
No purchases without his OK
The free post-process route; the paid plugin left to him
Zee’s look, from one comparison frame
Re-voice four lines after a Whisper check; remove blood from comic panel 4
The crew’s room. The lanes at their monitors, and the director’s chair: he decides what makes the cut. Painted by the art lane for this record. The style key from the first night set the light, the rain and the streets; Zee’s own look changed on Sunday (case 23).
Who and what, by name
ClaudeOpus and Sonnet through Saturday; Fable 5.2 on every Claude lane from Sunday 05:00. Integration, effects, world, story, characters, submission, and the judge.
Hyper3D RodinThe cast, the street kit, props and landmarks, and on Sunday the five townspeople. Generated and rigged.
ElevenLabsVoices for the cast and the Editor. Every line checked back against its text with Whisper.
ACE-StepThe score, run locally. Takes picked by measurement because nobody could listen overnight.
Antigravity + falThe art lane: street meshes, HUD icons, the district map, the painted sky and signs.
CursorThe interface lane.
OpenArtThe style key.
Unreal Engine 5.8With DLSS. Fonts in the game: Saira Condensed and IBM Plex, under the SIL Open Font Licence.
Thendo MukhavhuliSolo developer. Every decision about what makes the cut.
Rules statement
All game content was made during the jam; the first game commit is 12 Nov 11:38 SAST. Only tools, agent configurations, scripts and prompt templates were prepared earlier. AI-generated art, models, music and voices count as our own work under the rules. Brought in from outside: the Saira Condensed and IBM Plex fonts and Unreal Engine template content.
Still open
What is not done, not proven, or not ours to decide, as of Sunday 15 November, 15:30.
Zee’s animation. How she holds a weapon, runs, jumps and goes down. The director’s top note, and the first job for candidate 7.
The intro and cutscenes rush, and are being rebuilt so the player sets the pace.
Hold pressure is unproven. 0 of 6 holds pass the judge’s contact-and-pressure test in candidate 4.
The trailer scores 35 out of 50 against a pass mark of 40. It was cut from bot-played footage and has no shot of Zee’s face.
Candidate 6 has no frame rate and no scorecard. Its soak passed, but beside another job on the same PC (case 25).
The zip is 1.17 GB. The jam’s “keep it under 1 GB” is advice with a named remedy, not a cap. An earlier version of the dev log called it a cap, and that was wrong.
The D: hard drive is resetting. No clean-PC test yet, and no person has played a full run on a gamepad.
The last panel of the ending. Some files stay sealed.
Sources
DEVLOG.md · git, 536 commits on the integration branch by Sun 11:25 · SPEC-NIGHT.md · the approved direction page · lane logs and handovers (integration, world, effects, characters, story) · Judge: SCORECARD-RC1, -cand3-paper, -cand4 · builds 20261113-071204, 20261114-051505, 20261114-210448, 20261115-065816, -071455, -082922, -100902, -112452, -122509, -130034 and their soak logs · commits 8cf7f08, 9d9a5ce, 2d2b2d2, 69e6426, 0eeb69f · Thendo’s recordings: 13 Nov 09:12, 14 Nov 11:19, 15 Nov 00:37 and 12:25 · the candidate 7 brief · the integrator’s handover and Thendo’s session log, 15 Nov. Frames are from packaged builds and the director’s own recordings unless the caption says otherwise. Where a record is missing, this page says so.
Read the whole record
The PDF has all 26 numbered cases with their logs, and Saturday’s arguments in full. 28 pages, version 0.9.