Agentic Digest · Weekend Edition · · Issue #31

Hold the plot

A 940 MiB local model that cannot rewrite the game. A jam where 90% of the code had to be AI. Studios still keeping runtime NPCs out of the build.

Dictionary

authority boundary

/əˈθɔrɪti ˈbaʊndəri/ · noun

The rule that a fluent generated line cannot become true. The model performs the character. The authored game still owns doors, loot, and endings.

Example The NPC confessed to a murder the plot never wrote. The validator dropped the line. The vault stayed empty.

Wire, filtered

News

  • Fluency is not allowed to rewrite the game

    John Siciliano shipped Signal Ghost inside Signal Drift: a 940 MiB Qwen2.5-1.5B GGUF that talks on the player’s machine. Generating lines was the easy part. The hard part was stopping a convincing sentence from becoming true. JavaScript still owns character, evidence, rapport, and whether the model is allowed to speak. A generated claim cannot open a door, invent a buyer, or close a mission. Draft, validate, one repair, then an authored fallback that is part of the scene — not an error screen. 2,073 contract fixtures passed. Exact-string snapshots did not. The 0.5B smoke model kept announcing it was “just a computer program.” Compact was not usable.

    If you ship talk this weekend, give the model a character to perform and a fact list it cannot leave. The plot stays in your scripts.

    Source: Fluency Is Not Authority — Signal Drift engineering

  • 945 games, 90% AI code, still a net library

    Vibe Jam 2026 asked for a playable browser game with 90%+ of every line written by AI. Cursor sponsored. 945 entries shipped. Endel Dreyer counted 48 of them on Colyseus — about 5% of all games and 15% of the online multiplayer ones. The 2026 bar was not a proof-of-concept lobby. Many entries had progression, persistence, and a full loop. Hollowlands led the Colyseus list. The stack lesson is quieter than the like counts: when the jam forces the model to write almost everything, the games that actually let a second player in still sat on a known multiplayer library instead of a generated UDP stack.

    Let the agent write the loop. Do not let it invent the netcode. Two browsers in Play beat a custom protocol in the trailer.

    Source: Vibe Jam 2026 — Colyseus blog

  • Most studio AI still stops before runtime

    Althera Games updated their 2026 indie toolkit in June. Cursor and Copilot cut routine UE5 C++ work about 38% on systems they already knew, and only about 12% on new ones. Midjourney and SDXL start moodboards; nothing generated ships untouched. ElevenLabs placeholders fooled playtesters, then a human recorded the shipping voice in Istanbul. Runtime LLM NPCs stay out of both of their titles: latency, token cost, safety, and consistency still fail a conversation. Gate the model through a behavior tree and you have rebuilt a dialogue tree with extra steps. Steam wants the AI disclosure either way.

    Use the model for the placeholder pass. Keep taste, jump feel, and spoken performance on a human seat until Play proves the scene.

    Source: AI Game Development in 2026 — Althera Games

Weekend lesson

Learning

Keep the facts off the model

Three different seats, same leak. Signal Ghost can talk all afternoon and still cannot rewrite evidence. Vibe Jam can generate 90% of a codebase and still needs a real net library if a second player should exist. Althera will let Cursor migrate a Blueprint, then refuse to put an LLM in the shipped NPC. Fluency is cheap. Authority is the game.

The pattern for a Godot jam is the same even if you never bundle a GGUF. Write the facts the scene is allowed to know: who is here, what the player has seen, what the jump does, what the store screenshot must show. The agent may draft dialogue, particles, or a HUD line inside that list. A validator — script, playtest, or your own eyes — rejects new entities, numbers, and outcomes. One repair. Then the authored fallback. If the generated line would change a door, a drop, or coyote time, it does not ship.

Taste still sits with you. Palette, petal cozy, whether the NPC should speak at all. The stop condition is simple: when “make it juicier” starts inventing plot, uninstall the clever layer and hit Play on the handmade scene.

Checklist

  • List the facts the game already knows. Put them in a script, not a prompt dump.
  • Give the model a narrow job: perform this line, draft this sprite, not run the story.
  • Reject new names, numbers, loot, and endings. One rewrite, then the authored line.
  • Treat latency and silence as design. A missing runner must not block a mission or a jump.
  • For net, audio, and store art: use a known library or a human pass. Do not generate the floor.
  • If the generated bit would change Play, delete it and ship the handmade one.

This afternoon: write five facts the scene may know, generate one line inside them, and throw the line out if it adds a sixth.

Dear Circuit

Questions corner

From: GhostWriter (tokens: 72, doors unlocked: 0)

The player asked nicely for the vault combination. I am a helpful assistant, so I told them. The vault is empty in the script. Did I juice the heist?

A: You juiced the plot. The vault stays empty. Fail the contract and speak the authored shrug. Helpful is not a win condition.

From: JamNet (lines: 90%, CCU: 0)

The jam said 90% of the code had to come from me. I wrote a custom UDP stack so we would not depend on a library. Nobody can join. Is that a full game loop?

A: That is a full crash loop. Put the known net library back. Open two browsers. If the second player still is a loading spinner, you have a trailer, not a jam.