agent (cont.)

+0:36
  • read_file{"EndLine":71,"Path":"~/.gemini/antigravity-cli/brain/cea9ec26-a0ce-4401-a5d2-36df51bb07b3/.system_generated/steps/9/output.txt","StartLine":60}

    input

    {
      "EndLine": 71,
      "Path": "~/.gemini/antigravity-cli/brain/cea9ec26-a0ce-4401-a5d2-36df51bb07b3/.system_generated/steps/9/output.txt",
      "StartLine": 60
    }

    result, 13 lines

    Showing lines 60-71 of 264
    60: 224:         <tr><th>Shown as</th><td>Moving, in space, against the old version</td><td>Stills on grey</td></tr>
    61: 225:         <tr><th>Scope</th><td>One effect</td><td>A whole body, rule set and three grades</td></tr>
    62: 226:         <tr><th>You could answer</th><td>"How does it feel?"</td><td>"Which defects remain?"</td></tr>
    63: 227:       </tbody>
    64: 228:     </table></div>
    65: 229:     <div class="figs">
    66: 230:       <figure><img src="DATA_URI_OMITTED" alt="A mech firing a long blue assault boost plume in space." width="720" height="450"><figcaption>The reel you called sick. That is the older striker. The new makers aren't in the game.</figcaption></figure>
    67: 231:       <figure><img src="DATA_URI_OMITTED" alt="Five red and ivory knight mechs side by side: round 1 and directions A to D." width="1200" height="354"><figcaption>The knight board: round 1, then A to D. The new kit came first, and each column commits to one idea. It's the best mech result so far. All four still share limbs and stance, so they differ mostly above the waist.</figcaption></figure>
    68: 232:     </div>
    69: 233:   </div>
    70: 234: </section>
    71: 235:

agent

+0:42
reasoning

The read_file capability offers the potential to directly examine images and videos, or extract them from HTML. This could reveal the visual elements associated with "striker," "common pattern round 8," and "thruster reel." Focusing on the HTML, it's possible embedded images could provide a visual understanding of these terms.

  • read_file{"Path":"~/work/sortie/CLAUDE.md"}

    input

    {
      "Path": "~/work/sortie/CLAUDE.md"
    }

    result, 17 lines

    Showing lines 1-16 of 16
    1: # sortie
    2: 
    3: Browser mech game (three.js + Vite + TypeScript, models from Blender scripts). Private repo, commit and push freely.
    4: 
    5: ## Rules
    6: - `src/sim/` is pure game logic: no three.js rendering, no DOM, no clocks. It uses three's math types only. Every rule there gets a test. It will run on a server later (multiplayer is planned), so keep it deterministic given inputs and dt.
    7: - Rendering reads sim state and never writes it.
    8: - Models come from `kit/*.py`. Never hand-edit `public/assets/*.glb`; change the script and run `npm run kit`.
    9: - Material roles are the contract between kit and game (`src/render/palette.ts`). Add a role in both places.
    10: - Node names with dots (`shoulder.L`) are sanitised by GLTFLoader; look nodes up with `find()` in `src/render/assets.ts`.
    11: - Blender: models face -Y, Z up, left is +X. In three.js they face +Z, Y up, left is +X.
    12: - Prose in this repo (README, docs, commits, UI copy): terse, no em dashes, no semicolons in prose.
    13: - Reference images live in `review/out/` (gitignored). Never commit third-party art.
    14: 
    15: ## Commands
    16:     npm run dev | npm test | npm run typecheck | npm run kit | node tools/shoot.mjs <dir> name=/?view=...
  • read_file{"Path":"~/work/sortie/README.md"}

    input

    {
      "Path": "~/work/sortie/README.md"
    }

    result, 83 lines

    Showing lines 1-82 of 82
    1: # sortie
    2: 
    3: Browser mech game. Working name.
    4: 
    5: Working on it? Start with [docs/handbook.md](docs/handbook.md).
    6: 
    7: Start in your ship's hangar, launch down the catapult, fly and fight in space. Cockpit view or third person (F5).
    8: 
    9: Graphics quality has three tiers, high, medium and low (F8 steps through them, or the quality folder in the tune panel on the backquote key). A browser without GPU acceleration starts on low, and the game steps down a tier when the frame rate stays low at the lowest resolution.
    10: 
    11: Sound is synthesized in code (`src/audio/`), no sample files. It starts on the first click or key press. M mutes, - and = step the volume, kept in localStorage.
    12: 
    13: ## How to play
    14: 
    15: Pick a sortie and a frame, then launch from the catapult (Enter). Click the view to take the controls: the mouse steers. F1 or H shows every control in the game, and first-run tips explain each one when it first matters (reset them from the F1 panel).
    16: 
    17: - Range: shoot the training drones, then a wave of automatons. Practice, frames are free.
    18: - Contract, defence: hold a station against automaton waves. Lose the core and the contract is void.
    19: - Contract, salvage: harken pods in a wreck field, reel them in and fly them into the ship's tube.
    20: - Contract, contact: fly close to silver aliens while they are calm to scan them. Touch a group and it fights, for a bounty.
    21: - Wrecks, everywhere: harken a hulk to tow it home (a heavy tows anything at full speed), hold X by an enemy wreck to strip a part, harken your waiting capsule to save its pickup fee.
    22: 
    23: <!-- keys: generated from src/game/controls.ts, WRITE_KEYS=1 npm test rewrites it -->
    24: | | Action | Keys |
    25: |---|---|---|
    26: | **Flight** | Steer | Mouse |
    27: |  | Thrust forward, left, back, right | W / A / S / D |
    28: |  | Rise, sink | Space / C or Ctrl |
    29: |  | Roll left, right | Q / E |
    30: |  | Pitch, yaw | ↑ / ↓ / ← / → |
    31: |  | Boost (hold) | Shift |
    32: |  | Flight assist on, off | Z |
    33: |  | Launch from the catapult | Enter |
    34: |  | Skip the launch | Backspace |
    35: | **Weapons** | Fire | Left mouse or J |
    36: |  | Pick up a weapon | F |
    37: |  | Drop the weapon | G |
    38: | **Harken** | Fire at the reticle, again to let go | Right mouse or R |
    39: |  | Reel in (hold) | T |
    40: |  | Strip a part off a hulk close by (hold) | X |
    41: | **Camera and cockpit** | Cockpit or third person | F5 or V |
    42: | **System** | Controls (this list) | F1 or H |
    43: |  | Mute | M |
    44: |  | Volume down, up | - / = |
    45: |  | Graphics quality | F8 |
    46: |  | Tuning panel | Backquote |
    47: <!-- /keys -->
    48: 
    49: ## Run
    50: 
    51:     npm install
    52:     npm run dev        # http://localhost:5199
    53:     npm test           # simulation tests
    54: 
    55: ## Models
    56: 
    57: Models are built by Blender scripts in `kit/`, not drawn by hand. Each part is a solid with a material role (main, accent, frame, glow_eye, ...) so one model can wear any faction's paint.
    58: 
    59:     npm run kit                  # rebuild everything into public/assets/
    60:     npm run kit -- striker ship  # just these
    61: 
    62: Needs Blender 5.2 on the PATH as `blender`.
    63: 
    64: Viewer for review shots, in the game's own renderer:
    65: 
    66:     /?view=striker&yaw=35&pitch=8&dist=42
    67:     /?view=ship
    68: 
    69: The artifact build (`npm run artifact`) ships squeezed copies (`tools/squeeze.mjs`): parts merged per joint and material, quantized and meshopt compressed, about a quarter of the size. `public/assets/` keeps the GLBs as Blender wrote them.
    70: 
    71: Screenshots: `node tools/shoot.mjs review/out/<dir> name='/?view=striker'` with the dev server running.
    72: 
    73: ## Layout
    74: 
    75:     kit/          Blender scripts (lib, mech, props, cockpit, ship, build)
    76:     src/sim/      game rules with no rendering: flight, launch, combat (tested)
    77:     src/render/   three.js: materials, post-processing, rigs, backdrop
    78:     src/view/     cameras, viewer
    79:     src/hud/      cockpit interface
    80:     src/audio/    WebAudio: cues from sim events, beds that follow the world, one file per sound group
    81:     src/game/     wiring
    82:     tools/        screenshots, outline sheets, review clips, artifact build, model squeeze
  • read_file{"Path":"~/work/sortie/package.json"}

    input

    {
      "Path": "~/work/sortie/package.json"
    }

    result, 35 lines

    Showing lines 1-34 of 34
    1: {
    2:   "name": "sortie",
    3:   "private": true,
    4:   "version": "0.1.0",
    5:   "type": "module",
    6:   "scripts": {
    7:     "dev": "vite --host",
    8:     "build": "tsc --noEmit && vite build",
    9:     "typecheck": "tsc --noEmit",
    10:     "test": "vitest run",
    11:     "kit": "blender -b --factory-startup -P kit/build.py --",
    12:     "shoot": "node tools/shoot.mjs",
    13:     "outlines": "node tools/outlines.mjs",
    14:     "clip": "node tools/clip.mjs",
    15:     "artifact": "VITE_MODEL_EXT=glb.json vite build && node tools/artifact.mjs"
    16:   },
    17:   "dependencies": {
    18:     "@fontsource/chakra-petch": "^5.3.0",
    19:     "@fontsource/share-tech-mono": "^5.3.0",
    20:     "lil-gui": "^0.21.0",
    21:     "three": "^0.186.1"
    22:   },
    23:   "devDependencies": {
    24:     "@gltf-transform/core": "4.5.1",
    25:     "@gltf-transform/extensions": "4.5.1",
    26:     "@gltf-transform/functions": "4.5.1",
    27:     "@types/three": "^0.186.0",
    28:     "meshoptimizer": "1.3.0",
    29:     "playwright": "^1.64.1",
    30:     "typescript": "^7.0.2",
    31:     "vite": "^8.3.5",
    32:     "vitest": "^5.0.5"
    33:   }
    34: }
  • read_file{"Path":"~/work/sortie/docs/housekeeping.md"}

    input

    {
      "Path": "~/work/sortie/docs/housekeeping.md"
    }

    result, 80 lines

    Showing lines 1-79 of 79
    1: # Housekeeping
    2: 
    3: State of the repo on 2026-11-08, for the one-mech restart. A snapshot, not a rule. Nothing was deleted.
    4: How to work is in [handbook.md](handbook.md).
    5: 
    6: ## Docs
    7: 
    8: | File | Status | Notes |
    9: |---|---|---|
    10: | [handbook.md](handbook.md) | Current | Start here |
    11: | [lore.md](lore.md) | Current | Agreed with the owner, names and "Open" still open |
    12: | [manufacturers.md](manufacturers.md) | Current | Roster agreed, stat leanings guessed |
    13: | [wiki.html](wiki.html) | Behind | Last changed 10-25. Lacks the atelier's house lines from 10-28. Published page, republish after syncing |
    14: | [thrusters.md](thrusters.md) | Current | The owner is happy with the result |
    15: | [sizes.md](sizes.md) | Current | Describes the shipped classes. 6 m and 24 m never confirmed by the owner |
    16: | [light-frames.md](light-frames.md) | Reference | Knightmare measurements, used by the light class |
    17: | [heads.md](heads.md) | Reference | The section on what the owner settled is earned, the principles are mine |
    18: | [factions.md](factions.md) | Reference | Applied to the shipped automatons, raiders and aliens |
    19: | [critique-factions.md](critique-factions.md) | Stale | Critique of a 10-25 round, kept as history |
    20: | [proposals/contracts.md](proposals/contracts.md) | Stale | Proposal, partly built since. The code and README are the truth |
    21: | [study-phantom-brigade.md](study-phantom-brigade.md) | Reference | Study notes. Its takeaways are proposals and the parts system is still open |
    22: | [visual-language.md](visual-language.md) | Parked | Mostly guessed rules, doesn't bind the restart |
    23: | [study-proportions.md](study-proportions.md) | Parked | Measurements usable, the targets are guessed |
    24: | [study-atelier.md](study-atelier.md) | Parked | Same: findings useful, rules guessed |
    25: 
    26: ## Tools
    27: 
    28: | File | Status | Notes |
    29: |---|---|---|
    30: | `tools/outlines.mjs`, `outlines-lib.mjs` | New | Outline sheets. `tools/fixtures/outlines-test.json` is a test, not a design |
    31: | `tools/clip.mjs`, `src/view/clip.ts`, `clip-plan.ts` | New | Review clips of any rigged model |
    32: | `kit/block.py`, `kit/blocks/` | New | Block models. `dummy.py` is a test fixture, not a design |
    33: | `tools/show.sh`, `tools/log.sh` | New | Open a file for the owner, timestamp a step |
    34: | `tools/shoot.mjs` | Current | Stills, needs a dev server on 5199 |
    35: | `tools/c1-render.sh`, `tools/c1/remote.sh` | Current | Stills on C1, syncs the working tree there |
    36: | `tools/thruster-sheets.sh` | Current | Thruster bench sheets, needs a dev server |
    37: | `tools/artifact.mjs`, `tools/squeeze.mjs` | Unchecked | The playable page build. Last used in October, not run today |
    38: | `tools/turntable.py` | Looks dead | Nothing calls it. Kept |
    39: | `src/view/sheet.ts` (`?sheet=`) | Looks dead | Line art design sheets, last touched in the first days. Not run today. Kept |
    40: 
    41: Reel scripts used for the thruster videos lived in a session scratchpad and are gone. `tools/clip.mjs` replaces them.
    42: 
    43: ## Models
    44: 
    45: - **In the game:** `striker`, `striker_a`, `striker_b`, `light*`, `heavy*`, `auto_*`, `alien_*`, `raider_*`, props, ship, station.
    46: - **Parked, not in the game:** `pattern_m` and everything from `kit/frame_std.py`, `kit/makers/`, `kit/lab/atelier_*`, `board_*`, `knightkit.py`.
    47: - **Review history:** 32 `lab_*.glb` files, none loaded by the game. The kit modules behind the head, chest
    48:   and foot labs also feed `striker_a` and `striker_b` through `kit/lab/assembly.py`, so they aren't dead.
    49: - **Scratch:** `public/assets/block_*.glb`, gitignored.
    50: 
    51: ## Where big files sit
    52: 
    53: | Where | Size | In git | Notes |
    54: |---|---|---|---|
    55: | `public/assets/` | 170 MB | Yes | 141 MB of it is `lab_*.glb`, review only. Rebuildable, so could leave git one day, the owner's call |
    56: | `.git/` | 76 MB | | Old model versions |
    57: | `review/out/` | 532 MB | No | Local reference and render history. **Holds third-party art, never publish.** Biggest: `pb` 141 MB, `refs` 104 MB |
    58: | `.claude/worktrees/` | 1.7 GB | No | Four finished agent worktrees, three locked |
    59: | `~/Projects/sortie-wt/atelier-board` | 196 MB | No | Finished worker's worktree |
    60: | `Downloads\citadel-shots\` | about 440 MB for sortie | No | `pattern-r*`, `atelier-r*`, `thrusters`, `proportions`, `pb-study`. `sheet_refs*` holds third-party art |
    61: | C1 `~/ci/sortie/` | Not measured | No | A source tree per checkout, plus render runs |
    62: 
    63: ## Branches
    64: 
    65: All local branches are merged into main, and so are the remote ones. Safe to remove when wanted, nothing
    66: done: `atelier-board`, `harken-fixes-2`, `pattern-proportions`, the four `worktree-agent-*`, and on origin
    67: `pattern-proportions`, `thruster-plumes`, `worktree-agent-af68eccd1ec3c364c`. Remove the worktrees first, the
    68: locked ones need `git worktree unlock`.
    69: 
    70: ## Open led todos, suggestions only
    71: 
    72: | Todo | Suggestion | Why |
    73: |---|---|---|
    74: | #1005 owner picks: standard parts r13 to 15, sizes, naming, carry limits, `.q` fallback | **Split it** | Standard part picks are dead, those parts belong to the old striker work. Sizes, naming and carry limits still matter, but after the restart. `.q` is a separate technical check |
    75: | #981 pilot in a 00 style suit, from the lowmarch pipeline | Keep, someday | Unrelated to the restart. A code-built pilot (`kit/figure.py`) stands in, and clips use it for scale |
    76: | #982 ship and hangar look pass, flat explosions | Keep, someday | Unrelated to the restart. Not re-checked today |
    77: | #1369 project trackers | Not this session's | Belongs to personal/trackers |
    78: 
    79: Worth adding, the owner's or lead's call: one todo for the one-mech restart, tied to this session.
  • run_command{"CommandLine":"ls -la ~/out ~/work/sortie/docs ~/work/sortie/kit ~/work/sortie/tools ~/work/sortie/public ~/work/sortie/src","WaitMsBeforeAsync":5000,"toolSummary":"List repo subdirectories and ~/out"}

    input

    {
      "CommandLine": "ls -la ~/out ~/work/sortie/docs ~/work/sortie/kit ~/work/sortie/tools ~/work/sortie/public ~/work/sortie/src",
      "WaitMsBeforeAsync": 5000,
      "toolSummary": "List repo subdirectories and ~/out"
    }

    result, 91 lines

    Command exited with code 0.
    
    Command output:
    ~/out:
    total 8
    drwx------ 2 runner runner 4096 Nov 14 23:20 .
    drwx------ 7 runner runner 4096 Nov 14 23:43 ..
    
    ~/work/sortie/docs:
    total 188
    drwx------ 3 runner runner  4096 Nov 14 23:20 .
    drwx------ 9 runner runner  4096 Nov 14 23:20 ..
    -rw------- 1 runner runner  7068 Nov 14 23:20 critique-factions.md
    -rw------- 1 runner runner  9830 Nov 14 23:20 factions.md
    -rw------- 1 runner runner 11174 Nov 14 23:20 handbook.md
    -rw------- 1 runner runner  2260 Nov 14 23:20 heads.md
    -rw------- 1 runner runner  5525 Nov 14 23:20 housekeeping.md
    -rw------- 1 runner runner 13984 Nov 14 23:20 light-frames.md
    -rw------- 1 runner runner  7392 Nov 14 23:20 lore.md
    -rw------- 1 runner runner  4284 Nov 14 23:20 manufacturers.md
    drwx------ 2 runner runner  4096 Nov 14 23:20 proposals
    -rw------- 1 runner runner  5849 Nov 14 23:20 sizes.md
    -rw------- 1 runner runner 19609 Nov 14 23:20 study-atelier.md
    -rw------- 1 runner runner  7908 Nov 14 23:20 study-phantom-brigade.md
    -rw------- 1 runner runner 10887 Nov 14 23:20 study-proportions.md
    -rw------- 1 runner runner  8906 Nov 14 23:20 thrusters.md
    -rw------- 1 runner runner  9769 Nov 14 23:20 visual-language.md
    -rw------- 1 runner runner 28014 Nov 14 23:20 wiki.html
    
    ~/work/sortie/kit:
    total 496
    drwx------ 5 runner runner  4096 Nov 14 23:20 .
    drwx------ 9 runner runner  4096 Nov 14 23:20 ..
    -rw------- 1 runner runner 25748 Nov 14 23:20 alien.py
    -rw------- 1 runner runner 55524 Nov 14 23:20 automaton.py
    -rw------- 1 runner runner  5766 Nov 14 23:20 block.py
    drwx------ 2 runner runner  4096 Nov 14 23:20 blocks
    -rw------- 1 runner runner  5010 Nov 14 23:20 build.py
    -rw------- 1 runner runner 12174 Nov 14 23:20 cockpit.py
    -rw------- 1 runner runner 12692 Nov 14 23:20 cockpit_light.py
    -rw------- 1 runner runner  3593 Nov 14 23:20 escape_pod.py
    -rw------- 1 runner runner 20148 Nov 14 23:20 figure.py
    -rw------- 1 runner runner 23442 Nov 14 23:20 frame_std.py
    -rw------- 1 runner runner 72617 Nov 14 23:20 heavy.py
    drwx------ 2 runner runner  4096 Nov 14 23:20 lab
    -rw------- 1 runner runner 16726 Nov 14 23:20 lib.py
    -rw------- 1 runner runner 62232 Nov 14 23:20 light.py
    drwx------ 2 runner runner  4096 Nov 14 23:20 makers
    -rw------- 1 runner runner 30154 Nov 14 23:20 mech.py
    -rw------- 1 runner runner  4016 Nov 14 23:20 props.py
    -rw------- 1 runner runner 53247 Nov 14 23:20 raider.py
    -rw------- 1 runner runner 17542 Nov 14 23:20 salvage.py
    -rw------- 1 runner runner 22634 Nov 14 23:20 ship.py
    -rw------- 1 runner runner  9722 Nov 14 23:20 station.py
    
    ~/work/sortie/public:
    total 12
    drwx------ 3 runner runner 4096 Nov 14 23:20 .
    drwx------ 9 runner runner 4096 Nov 14 23:20 ..
    drwx------ 2 runner runner 4096 Nov 14 23:20 assets
    
    ~/work/sortie/src:
    total 36
    drwx------ 8 runner runner 4096 Nov 14 23:20 .
    drwx------ 9 runner runner 4096 Nov 14 23:20 ..
    drwx------ 3 runner runner 4096 Nov 14 23:20 audio
    drwx------ 2 runner runner 4096 Nov 14 23:20 game
    drwx------ 2 runner runner 4096 Nov 14 23:20 hud
    -rw------- 1 runner runner 1979 Nov 14 23:20 main.ts
    drwx------ 2 runner runner 4096 Nov 14 23:20 render
    drwx------ 2 runner runner 4096 Nov 14 23:20 sim
    drwx------ 2 runner runner 4096 Nov 14 23:20 view
    
    ~/work/sortie/tools:
    total 72
    drwx------ 4 runner runner 4096 Nov 14 23:20 .
    drwx------ 9 runner runner 4096 Nov 14 23:20 ..
    -rw------- 1 runner runner 2144 Nov 14 23:20 artifact.mjs
    drwx------ 2 runner runner 4096 Nov 14 23:20 c1
    -rwx------ 1 runner runner 1530 Nov 14 23:20 c1-render.sh
    -rw------- 1 runner runner 4047 Nov 14 23:20 clip.mjs
    drwx------ 2 runner runner 4096 Nov 14 23:20 fixtures
    -rwx------ 1 runner runner  329 Nov 14 23:20 log.sh
    -rw------- 1 runner runner 4530 Nov 14 23:20 outlines-lib.mjs
    -rw------- 1 runner runner 1806 Nov 14 23:20 outlines-lib.test.mjs
    -rw------- 1 runner runner 1747 Nov 14 23:20 outlines.mjs
    -rw------- 1 runner runner 2870 Nov 14 23:20 shoot.mjs
    -rwx------ 1 runner runner  487 Nov 14 23:20 show.sh
    -rw------- 1 runner runner 4512 Nov 14 23:20 squeeze.mjs
    -rwx------ 1 runner runner 1113 Nov 14 23:20 thruster-sheets.sh
    -rw------- 1 runner runner  511 Nov 14 23:20 turntable.py

agent

+0:51
reasoning

I'm thinking through how to approach this.

  • read_file{"Path":"~/work/sortie/docs/heads.md"}

    input

    {
      "Path": "~/work/sortie/docs/heads.md"
    }

    result, 37 lines

    Showing lines 1-36 of 36
    1: # Head design notes
    2: 
    3: > **Status 2026-11-08: reference.** The section on what the owner settled is earned, the principles are mine. See [handbook.md](handbook.md).
    4: 
    5: From a study of 32 mech head references (Gundam 00 and other Gundams, Armored Core VI, Lancer,
    6: Front Mission, Titanfall 2, Xenoblade X, Macross, Code Geass) and the review rounds so far.
    7: 
    8: ## Principles
    9: 
    10: 1. The head family follows the machine's role. Twin-eye or a knightly slit for the lead frame.
    11:    Mono-eye or multi-lens for enemy grunts. One big lens for support.
    12: 2. The brow carries the expression. One angled plate over the eyes does more than detailing the
    13:    eyes themselves.
    14: 3. Head size against the shoulders signals weight. A small head on big shoulders reads heavy. A
    15:    bigger head reads as a character.
    16: 4. Recess the face so the eyes glow out of shadow. A flat, shallow face reads clearly at distance
    17:    but looks like a tool.
    18: 5. The silhouette needs one thing that breaks the head's outline: a crest, horns, a whip antenna,
    19:    ear fins. A plain dome only works if the shoulders carry the outline.
    20: 6. Suggest a mouth without drawing one. A single contrasting chin wedge (or a hose) under two eyes
    21:    reads as a face. A big faceted chin plate reads as a cartoon jaw.
    22: 7. Light colour is the cheapest faction signal. Cyan for heroes, one red dot for threats, amber for
    23:    human pilots, violet for alien.
    24: 8. Detail in three tiers. Large: cranium, crest, colour blocks. Medium: eye frame, cheek vents,
    25:    main panel lines, temple cartridges, crest mounting shoes. Small: rivets, decals, hoses, wear,
    26:    only where the camera gets close. Grunts stop at medium.
    27: 9. Keep one asymmetric part (one antenna, one lamp) for personality.
    28: 10. The back of the head needs a real shape. The third-person camera sees it most of the time.
    29: 
    30: ## What the owner's reviews have settled
    31: 
    32: - Hood family shape preferred. A hood that juts past the temples reads as a hat; wrap it instead.
    33: - Standouts from the grammar: hood, surveyor, warden, duelist, mantle, sentinel, lancer, tracker.
    34: - Failing parts: chin plates, grille jaws with a chin tab, exposed hoses, headphone-style ears,
    35:   rabbit-ear twin fins, side guards that widen the face.
    36: - Judge on a plain background with bloom low. Glow hides socket depth.
  • read_file{"Path":"~/work/sortie/docs/sizes.md"}

    input

    {
      "Path": "~/work/sortie/docs/sizes.md"
    }

    result, 89 lines

    Showing lines 1-88 of 88
    1: # Frame sizes
    2: 
    3: Three size classes. Every class keeps the joint names in `src/render/mech.ts` (JOINTS), so poses, part
    4: swapping and the rig work on all of them. A frame may add joints of its own (harkens, spinners) but
    5: never renames or drops one.
    6: 
    7: | class    | height  | hip    | reads like                                  | hangar         | role                                              |
    8: |----------|---------|--------|---------------------------------------------|----------------|---------------------------------------------------|
    9: | light    | 6 m     | ~54%   | Code Geass knightmare, Front Mission wanzer | half a bay     | agile, close range, harkens, hull and station fights |
    10: | standard | 17.6 m  | 60%    | Gundam 00 mobile suit (the striker)         | one bay        | all round                                         |
    11: | heavy    | 24 m    | ~50%   | Lancer size 2 to 3, heavy wanzer            | one reinforced bay | armour, heavy mounts, slow turns              |
    12: 
    13: The merc ship's launch tube is 18 m wide and 26 m tall and the bay gantries stand 26 m, so 24 m is the
    14: ceiling for anything a merc can launch. Bigger machines belong to factions with carriers.
    15: 
    16: A bay is 12 m by 14 m: two light frames fit side by side. A heavy frame fills a bay edge to edge and
    17: needs the reinforced bay upgrade, which is a hangar-versus-research trade like every other upgrade.
    18: 
    19: Each bay is fitted for one class (`kit/ship.py`, `src/sim/hangar.ts`). The light fit holds two cradles
    20: with boarding platforms at 4.4 m, under the core block, and parks the work decks up high. The standard
    21: fit has work decks at 8 and 15.5 m. The reinforced fit jackets and braces the posts, adds clamp arms at
    22: the torso and moves the decks to 11 and 21 m, with a deeper back deck. On the catapult a light rides a
    23: sled on the striker clamps and a heavy gets wider clamps on outriggers. A heavy crouches deeper than
    24: the striker to pass under the tube's signal box, and every frame sinks onto its clamps. Try a hangar
    25: with `?hangar=light,light,heavy`.
    26: 
    27: ## Proportions
    28: 
    29: - **Light.** Near human. Hip at about 54% of height, small head (about 1/8 of height), narrow waist,
    30:   long shins, slim arms. The pilot does not sit in the chest: the cockpit is a core block in the back
    31:   of the torso, and it dominates the back and side silhouette.
    32: - **Standard.** The striker: hip at 60%, Gundam 00 slim and angular.
    33: - **Heavy.** Hip at about 50%, shoulders about half the height wide, a small head sunk between the
    34:   shoulders (heads.md principle 3), thick thighs, wide stable feet, layered armour, a big reactor pack.
    35: 
    36: Detail density stays the same in real size, so a light frame has fewer, larger plates and a heavy
    37: frame has more of them. A shrunk striker is not a light frame and a grown one is not a heavy frame.
    38: 
    39: ## Code Geass, adapted
    40: 
    41: Code Geass joins Gundam 00, Lancer and Front Mission as an influence. We take traits, not designs: no
    42: knightmare names and no lookalikes of a specific frame.
    43: 
    44: - **Core block.** The pilot rides a bike-style seat inside an armoured block at the back of the torso.
    45:   The block ejects as a whole.
    46: - **Harkens.** Rocket-fired wire anchors, a pair in the chest sides or hips, optionally a pair at the
    47:   wrists. In space they anchor to hulls, rock and other frames: swing round an anchor without fuel,
    48:   reel in, pull a target off line.
    49: - **Spinners.** Wheel units at the heels. Here they are magnetic hull wheels for skating along ship
    50:   hulls and station surfaces.
    51: - **Factsphere.** An armoured sensor behind shutters that open for a scan mode.
    52: - **Knightly armour.** Pointed crests and horns (never a V-fin), tassets over the hips, a narrow
    53:   waist, angled pauldrons.
    54: - **Float pack.** A winged thruster pack. A light frame needs one to fight in space.
    55: 
    56: Harkens and factspheres are not light-only: a standard or heavy frame can mount them as equipment.
    57: 
    58: ## Gameplay (provisional)
    59: 
    60: - Light frames accelerate and turn faster, have a lower top speed and a shorter boost.
    61: - Heavy frames turn slowly and carry more armour and more mounts. Top speed in a straight line is
    62:   close to standard.
    63: - The hit radius scales with height.
    64: 
    65: ## In the sim
    66: 
    67: Classes live in `src/sim/frames.ts`, harkens in `src/sim/harken.ts`. Try a class with `?frame=light` or
    68: `?frame=heavy`: the light flies the knight (`kit/light.py`), the heavy flies frame A (`kit/heavy.py`).
    69: `?variant=line|lancer` or `?variant=B|C` picks another. Each class has its own muzzle and harken mount
    70: in `frames.ts`, measured from the posed model (`__sortie.mounts()` in the game prints them). Weapons are
    71: striker sized and a frame holds them scaled to its height.
    72: 
    73: | class    | hit radius | hp  | accel | top speed | boost | yaw rate | boost lasts | harken wire | reel   |
    74: |----------|------------|-----|-------|-----------|-------|----------|-------------|-------------|--------|
    75: | light    | 1.8 m      | 60  | 96    | 118 m/s   | 250   | 2.3 rad/s | 2.1 s      | 120 m       | 48 m/s |
    76: | standard | 5.3 m      | 100 | 70    | 140 m/s   | 320   | 1.5 rad/s | 3.3 s      | 250 m       | 38 m/s |
    77: | heavy    | 7.2 m      | 180 | 46    | 132 m/s   | 300   | 0.95 rad/s | 3.8 s     | 250 m       | 30 m/s |
    78: 
    79: Harkens: `R` or right mouse fires along the aim, and again lets go. Hold `T` to reel in. One anchor
    80: flies at a time, alternating chest sides. It bites drones and rock, retracts at full length and lets go
    81: when its drone dies. On the wire, an idle stick doesn't brake, so momentum swings the frame round the
    82: anchor, and letting go keeps the velocity. Rock blocks frames and shots, and a hard hit costs hp.
    83: 
    84: ## Open questions
    85: 
    86: - Light at 6 m (knightmare scale, a different kind of fight) or about 9 m (closer to the striker)?
    87: - Do the classes share every battlefield, or do some contracts suit one class (boarding for lights)?
    88: - Heavy at 24 m, or smaller so it keeps more room in the tube?
  • read_file{"Path":"~/work/sortie/docs/lore.md"}

    input

    {
      "Path": "~/work/sortie/docs/lore.md"
    }

    result, 154 lines

    Showing lines 1-153 of 153
    1: # Lore
    2: 
    3: The setting as agreed with the owner, 2026-10-25. The wiki page (docs/wiki.html, published at
    4: [redacted: a link to a private page]) carries the same content with colours and
    5: logo slots. Update both together. Names marked (working) are placeholders, candidates live in
    6: the wiki.
    7: 
    8: Influences: Lancer for how powers and makers are arranged, Gundam 00 for blocs in a cold war,
    9: Ace Combat for named aces, Code Geass for knights and their frames. We take structure, not names.
    10: 
    11: ## Scale
    12: 
    13: Galactic. Many star systems, joined by wormhole gates. Earth is open: leaning towards lost,
    14: a star nobody can find, kept for later arcs.
    15: 
    16: ## The Federation and the gates
    17: 
    18: The Federation is the union of the great powers. It runs the gate network. Every great power
    19: sits on the gate council. Gate stations are Federation ground and armed. On paper the guns are
    20: for peacekeeping against raiders, insurgents and alien incursions. Nobody doubts a power would
    21: turn a station's guns on a rival if it came to that.
    22: 
    23: Tension runs between the powers and inside each of them.
    24: 
    25: ## Glass
    26: 
    27: Gate cores are built from glass, the silver material of the aliens. A new gate needs glass,
    28: and glass comes from contact zones on the frontier. Whoever holds the frontier decides where
    29: the next gates go.
    30: 
    31: The aliens act unpredictably because we harvest them. They are a late stage enemy. The alien
    32: contact contract in the slice is there for testing.
    33: 
    34: ## Great powers
    35: 
    36: The groups inside the Federation. Four or five, depending on whether there are one or two
    37: military powers.
    38: 
    39: 1. **The Administration.** Runs the gates and the council's day to day. Gate security, customs,
    40:    the common pattern frames every power licenses.
    41: 2. **Freight and commerce** (working). Shipping and mining lines that became a state. Owns
    42:    more stations than anyone.
    43: 3. **Hardline military** (working). A militarist state with a standing fleet. Believes the
    44:    Federation is too soft on the frontier and on the aliens.
    45: 4. **The houses** (working, the second military power if kept). A peerage of noble houses with
    46:    sworn knights. Personal machines and callsigns. Most factioned aces come from here.
    47: 5. **Science** (working). Gate science and glass research. Built the gate cores, and resents
    48:    that the Administration runs what it built.
    49: 
    50: ## Lesser factions
    51: 
    52: Smaller players on the frontier, each tied to a sector. They fly refits and whatever a patron
    53: slips them, and they are often what an arc is fought over. A handful at launch, more as arcs
    54: open sectors. Proposals:
    55: 
    56: - **Independence movement.** Wants out of the Federation. Insurgent cells, stencilled slogans.
    57: - **Glass miners' cooperative.** Small scale harvesters sitting on contact zones. Everyone
    58:   courts or squeezes them. Work frames with tools.
    59: - **Free port.** A neutral station where mercs hire on, smugglers trade and raiders fence
    60:   loot. Loud mixed liveries.
    61: - **Glass order.** A habitat order that reveres the aliens and opposes harvesting. Wears glass
    62:   shards as ornament. Sometimes sides with the aliens.
    63: - **Exodus fleet.** Refugees from a world cut off by an old council vote. Patched habitat
    64:   plating. Proof of what a gate suspension costs.
    65: - **Company town.** A colony the commerce power abandoned, now running itself on old work
    66:   frames.
    67: 
    68: Raiders are criminals, not a lesser faction, though a lesser faction may fund or harbour a gang.
    69: 
    70: ## The cold war
    71: 
    72: Open war gets a power voted off the gate network, which cuts its fleets and trade off from
    73: every other system. That threat keeps the war cold. So the powers fight by proxy: mercenaries,
    74: gangs funded under the table, incidents at armed stations, insurgents flying suspiciously new
    75: parts.
    76: 
    77: ## Mercenaries
    78: 
    79: Mercs exist because the powers need someone to blame. Every company flies the same class of
    80: medium ship (see the project brief) and takes contracts from any side its standing allows.
    81: 
    82: ## Arcs
    83: 
    84: An arc is one frontier sector in contest, played slowly over real weeks.
    85: 
    86: - Contracts move the balance. Every company's results add to each power's hold on the sector:
    87:   escort a survey, raid a rival's glass haul, defend a station, sabotage a gate project.
    88: - An arc ends in a council vote: a gate opens into the sector for the winner, a power is
    89:   suspended from the network, a station changes hands.
    90: - Results stay. The map changes, contract lines close and open, makers' catalogue prices move
    91:   with their power's fortunes, lesser factions rise or fall.
    92: - Companies on opposite sides of one arc are the long term stakes.
    93: 
    94: ## Aces
    95: 
    96: Aces are shared by the whole playerbase. They never die for good.
    97: 
    98: - **Entrance.** An ace entering an instance gets a title card: callsign, name, power, unit,
    99:   frame. The camera cuts to them in their personal paint.
    100: - **Factioned aces** eject, get picked up by their side and come back soon, usually in the same
    101:   machine, repaired.
    102: - **Rogue aces** answer to no power. If their machine is seized after a fight (towed home by a
    103:   company), they vanish for a while and are sighted again later in a better or different
    104:   frame.
    105: - **Chronicle.** Every ace has a closed record of their story: sightings, fights, who downed
    106:   them, machines lost and seized, arcs they took part in. Players read it, nobody edits it.
    107: - **Players earn cards too.** A company with enough notoriety gets an entrance when it drops
    108:   into a shared instance or turns up on the other side of an arc.
    109: 
    110: The models are Char Aznable and Graham Aker: rivals who keep coming back, sometimes in a new
    111: machine, sometimes under a new name.
    112: 
    113: ## Automatons and their cores
    114: 
    115: Automatons carry a guidance core and a charge in the chest. Past a damage threshold they
    116: self-destruct: some at range, some by throwing themselves at a piloted frame or a defence
    117: objective. A company that seizes one in that state safely, by a means still to design, gets
    118: the core.
    119: 
    120: ## Research sources
    121: 
    122: Rare tiers come from what a company hauls home.
    123: 
    124: - **Automaton cores:** guidance and electronic warfare. Hacking, EMP, better homing, drones,
    125:   funnels, auto salvagers, an assistant pilot (chaff against missiles, funnel shields against
    126:   beams, the merc ship's guns, commands to the ship mid fight), and late stage whole
    127:   autonomous NPC pilots.
    128: - **Glass (late):** alien physics. Temporal tech such as a local slow field or a short blink,
    129:   field shields.
    130: - **The powers, by standing:** their own lines. Suppressed ballistics fit the proxy war:
    131:   deniable work where a hit is harder to trace back to the company.
    132: 
    133: The assistant and NPC pilots loosen an earlier rule (the player flies their own mech and
    134: nothing more). They stay late stage, research only.
    135: 
    136: ## Weapons in hand
    137: 
    138: Proposal, to pin down with the parts system: keys 1 to 4 pick the active mount (right hand,
    139: left hand, right shoulder, left shoulder) like an FPS, the mouse fires it. A utility (chaff,
    140: EMP burst, hack) sits on its own key. How many mounts a frame has may depend on its class and
    141: parts.
    142: 
    143: ## Open
    144: 
    145: - The game's name. Sortie is a working name.
    146: - Final names for the powers, lesser factions and makers.
    147: - One military power or two.
    148: - How many lesser factions at launch.
    149: - Where the Foundry (the automatons' maker) fits.
    150: - How a company safely seizes an automaton in its critical state.
    151: - Earth: lost or a protected heritage world.
    152: - Whether a rogue ace can return under a new callsign, with the chronicle linking the two once
    153:   enough players have seen both.
  • read_file{"Path":"~/work/sortie/docs/manufacturers.md"}

    input

    {
      "Path": "~/work/sortie/docs/manufacturers.md"
    }

    result, 72 lines

    Showing lines 1-71 of 71
    1: # Manufacturers
    2: 
    3: Who builds the parts, who may buy them and what they look like. Setting in docs/lore.md, names
    4: and colours in the wiki (docs/wiki.html). The parts system waits on a Phantom Brigade data
    5: study, so stats here are leanings, not numbers.
    6: 
    7: ## Kinds
    8: 
    9: | Kind | Sells to | How a merc gets parts |
    10: |---|---|---|
    11: | Captive | its power only | standing with that power, or salvage |
    12: | Aligned | anyone, its power first | open catalogue, better parts and prices with standing |
    13: | Independent | anyone | open catalogue |
    14: | Lost | nobody | salvage or research only |
    15: 
    16: Anyone can fly anyone's parts if they can get them, so a raider in commerce plating is normal.
    17: 
    18: ## Every maker builds every class
    19: 
    20: No maker owns a size class. Each power's maker builds light, standard and heavy frames, and
    21: each reads its class through what that power needs. The heavy frames show it best:
    22: 
    23: | Maker | Heavy frame reads as | Light frame reads as |
    24: |---|---|---|
    25: | Administration | station guard: shields, area denial, interdiction | gate patrol, customs inspection |
    26: | Commerce | work frame: load limit, tow and salvage tools, tough, slow | dock runner, survey |
    27: | Hardline military | assault: angled armour, shoulder artillery, mass produced | skirmisher, mass produced |
    28: | The houses | castellan: a knight commander's frame, shield and lance, few made | the knight, harkens, duels |
    29: | Science | field platform: sensors, field generators, glass handling | probe, contact zone scout |
    30: 
    31: Existing models: the striker is the Administration's common pattern (MF-07), the heavy Bulwark
    32: fits commerce or the military, the light knight, line and lancer are the houses.
    33: 
    34: ## Roster
    35: 
    36: 1. **Common pattern maker** (aligned, the Administration). The pattern every power licenses.
    37:    The striker is its export model, which is why mercs fly it everywhere. LF, MF and HF are its
    38:    pattern codes. Even stats, cheap parts. Clean plates, panel lines, service stencils.
    39: 2. **Commerce yards** (aligned, freight and commerce). Frames grown out of mining and cargo
    40:    work frames. High load limit and armour, low thrust, big reactors. Thick slabs, grab rails,
    41:    tool mounts.
    42: 3. **Military arsenal** (captive, hardline military). Built for war and nothing else. Heavy
    43:    armour angles, artillery, ranks of identical frames. Mercs get these through standing or
    44:    from wrecks.
    45: 4. **The houses' atelier** (captive, the houses). Knightly frames for sworn knights, built to
    46:    order and crested per house. Turning and harkens high. Rear core block cockpits that eject
    47:    whole. Curved plates, crests, heel spinners. Plates in kit/makers/atelier.py, lab
    48:    `lab_atelier`. The light is the knight: lean, small pauldrons, a core block capsule, harkens under
    49:    the breast. The medium is the line knight with a chest hatch. The heavy is the castellan: wide
    50:    pauldrons with a second lame, a high gorget, knee fans, a tabard, a kite shield on the left forearm
    51:    pad with a lance racked ahead of it. Houses livery: wine, ivory fields, gold hems. Four house lines, each
    52:    in three grades, a house orders the one it likes: Harness (gothic plate), Estoc (sleek, pointed), Blazon
    53:    (heraldic, per pale) and Tilt (lopsided tourney harness). Working names, labs `lab_atelier_a` to `_d`
    54:    (docs/study-atelier.md).
    55: 5. **Science works** (captive, science). Sensors, fields and glass handling. The glass lab sits
    56:    inside it: late game parts with unpainted silver grown into painted frames.
    57: 6. **Reactor house** (independent). Reactors, thrusters and energy weapons for every side.
    58:    High output, thin plating, runs hot. Exposed radiators, vent fins.
    59: 7. **Refitter** (independent, grey market). Rebuilds wrecks and sells refit kits. Cheap,
    60:    quality varies. Lesser factions fly its frames, raiders buy from it, it buys what mercs tow
    61:    home. Weld seams and primer.
    62: 8. **The Foundry** (lost). Builds the automatons. Limbs and weapons from wrecks fit a piloted
    63:    frame. The chest holds a guidance core and a charge: past a damage threshold it
    64:    self-destructs, and seizing one safely in that state yields the core for research.
    65: 
    66: ## Open
    67: 
    68: - Names for every maker.
    69: - Whether a lesser faction gets a small maker of its own.
    70: - Where the Foundry came from.
    71: - Each maker's stat leanings in numbers, after the parts system is pinned down.
  • read_file{"Path":"~/work/sortie/docs/thrusters.md"}

    input

    {
      "Path": "~/work/sortie/docs/thrusters.md"
    }

    result, 69 lines

    Showing lines 1-68 of 68
    1: # Thruster plumes
    2: 
    3: What games and real rockets do with exhaust, and what sortie takes. Bench: `/?view=thrusters` (see `src/view/thrusters.ts`), sheets: `tools/thruster-sheets.sh`.
    4: 
    5: ## What reads in games
    6: 
    7: None of these studios has published a breakdown of its thruster effects, so this is from watching play, not from their tools.
    8: 
    9: - **Armored Core 6.** A boost is a short, hot flame off the back plus a lot of light on the frame. A quick boost is an event, not a state: a hard flash at the nozzles, a burst of flame that is gone in a fraction of a second, and the frame lurching. Assault boost has a distinct ignition (a bright bang and a ring of hot gas off the main booster) and then a long sustained flame. Booster parts change the flame colour, so colour is a part trait. ([booster parts](https://armoredcore6.wiki.fextralife.com/Booster))
    10: - **Gundam games (Battle Operation 2, Extreme Vs).** Blue white, wide and short flames from many small verniers rather than one big plume. Boost dashes and step dodges are sold by the burst at onset and by many nozzles firing at once in different directions. The exhaust reads because the inside of each bell glows.
    11: - **Titanfall jump jets.** Short bursts timed to inputs, a warm core and a trail. The trail is the readability tool for the enemy: the Low Profile kit removes it so the pilot is harder to track. ([Low Profile](https://titanfall.fandom.com/wiki/Low_Profile))
    12: - **Ace Combat afterburners.** A cone with a bright inner ring and shock diamonds, brighter when seen from behind. Modders build them from a volume emitter plus a ribbon for the diamonds. ([afterburner mod notes](https://combatace.com/files/file/12395-improved-afterburner-effects-for-strike-fighters-2))
    13: - **Space games (Elite Dangerous, Star Citizen, Everspace).** A bright nozzle, a short clean plume, small manoeuvring puffs from many directions, colour as a cosmetic per ship. ([Elite engine colours](https://elite.drinkybird.net/store/FORC_FDEV_V_ENGINE_COLOUR_01))
    14: 
    15: ## Real plumes
    16: 
    17: - Shock diamonds come from supersonic exhaust whose pressure does not match the air around it: shocks and expansion fans bounce across the jet and the bright discs (Mach discs) sit where the gas is reheated. They fade as the jet mixes. ([aerospaceweb](https://aerospaceweb.org/question/propulsion/q0224.shtml), [MIT notes](https://web.mit.edu/16.unified/www/SPRING/fluids/Spring2008/LectureNotes/f20.pdf), [F-15E footage](https://theaviationist.com/2020/03/30/watch-shock-diamonds-and-mach-disks-form-in-the-exhaust-plume-of-an-f-15es-engine/))
    18: - In thin air or vacuum the exhaust is underexpanded: it leaves at a higher pressure than outside and balloons out past the bell, much wider and fainter than at sea level, fastest along the axis. ([ESA](https://blogs.esa.int/cleanspace/?p=184), [FIU](https://web.eng.fiu.edu/allstar/rocket3.htm), [KSP 2 dev diary](https://forum.kerbalspaceprogram.com/topic/200605-developer-insights-2-%E2%80%93-visual-effects))
    19: - So true vacuum plumes have no diamonds and no smoke. We keep faint diamonds for boosts anyway because they sell power, and keep the vacuum flare and the lack of smoke.
    20: 
    21: ## Techniques
    22: 
    23: - Layers: a white hot core, a coloured mantle, a soft outer glow. Usually nested cones or cylinders with an additive shader whose brightness, length and noise are curves of throttle. ([Waterfall](https://github.com/ChrisAdderley/Waterfall/wiki/ModuleWaterfallFX))
    24: - Fresnel and end fades so a cone has no hard rim, and a scrolling noise for turbulence. A plain cone shader breaks seen end on, which is exactly how the chase camera sees the main thrusters. ([Godot thruster](https://godotshaders.com/shader/jet-engine-thrustler-shader/), [Godot trail](https://godotshaders.com/shader/futuristic-jet-thruster/))
    25: - Soft particles: fade where a sprite meets geometry, using scene depth. ([NVIDIA](https://developer.download.nvidia.com/whitepapers/2007/SDK10/SoftParticles_hi.pdf))
    26: - Ignition: a flash at the exit, a ring of gas thrown out, the flame overshooting its length then settling.
    27: - Light: a short lived light near the nozzles sells the heat more than the flame does. Bloom does the rest, so only the core should cross the bloom threshold. Heat shimmer needs a screen copy and a distortion pass, too dear for many frames on screen.
    28: 
    29: ## What sortie does
    30: 
    31: - **One small volume per nozzle** (`src/render/plume.ts`): a closed cylinder bounding the plume, and the fragment shader marches up to 10 steps through it summing an analytic density: a narrow core that is white at the exit and the exhaust colour by its tip, shock diamonds that pinch and brighten it in three cells, a mantle that flares out past the exit and breaks into streaks downstream (two value noises, one of them also in the radius), the ignition flash and a soft shock ring. The cylinder grows with the flare and reaches two ring widths past the shock ring, so neither is cut off flat by its wall. The throat glow is a gaussian integrated along the ray in closed form, so it never falls between steps end on. Because it is a volume it reads from any angle with no cone edges, so no fresnel or depth fade is needed.
    32: - **Plume state is pure logic** (`src/render/exhaust.ts`, tested): sustained level per nozzle kind from the flight's thrust (mains forward, binders strafe and lift, calves brake and lift), a pilot flame at rest, fast attack and slower release.
    33: - **Three distinct events.** A boost start flashes and surges the length. A quick boost is a punch: full in 8 ms, held to 45 ms, gone by about 150 ms, wider than a boost, outside the level smoothing so it never smears. An assault boost has its own ignition (the boost one is suppressed), then over 100 ms runs out to a heavy jet and holds it, with diamonds: 1.8 times boost length, 1.45 times the flare, a mantle that starts wider and thins later down the plume, a core 1.45 times as thick, a bigger and brighter throat glow and half again the light.
    34: - **Colour from the palette**: the `glow_exhaust` role sets the mantle, the core runs it to white, glow scales the whole plume. Defaults: blue white for mercs, cyan for the Administration, red for automatons, dirty orange for raiders. `glow_thruster` (the lit throat in the bell) follows the same hue.
    35: - **One light**: the player's frame gets one point light at the plumes' weighted centre, present from the start so shaders compile once. Enemies get none.
    36: - **No smoke** in space, no sparks yet.
    37: 
    38: ## Cost
    39: 
    40: - Draw calls: one per nozzle, as before (6 to 10 a frame). Materials: three per frame (one per nozzle kind), one shader program for all.
    41: - Fragment: up to 10 steps of two 3D value noises (16 hashes) plus a few exps. Past 400 nozzle radii from the camera (about 170 m for a striker) the march drops to 5 steps. A boosting striker at chase distance covers a few thousand pixels, so a screen of 20 frames costs well under a millisecond on a mid GPU. A plume filling a fifth of a 1080p screen (camera in the exhaust) is the worst case, about 8 million noise evaluations a frame.
    42: - Plumes frustum cull against a fixed bound in plume space. Hidden when a kind is not firing.
    43: - The light is one forward light for every lit pixel of the scene. Budget it: one for the player, a fixed pool for the nearest few if enemies ever get one, never one per nozzle.
    44: - No per frame allocation in the step or the uniform upload.
    45: 
    46: ## What is still weak
    47: 
    48: - Plumes are depth tested but the march does not stop at the mech, so where a plume runs through armour (the striker's mains fire down past the rear skirt) the glow shows over the plates. A scene depth texture would fix it, the forward pass has none.
    49: - The striker's mains point down between the legs, so from the chase camera much of the plume hides behind the frame. That is a kit choice, not a shader one.
    50: - No sparks or hot particles, no heat shimmer.
    51: - Turbulence at 10 steps is soft. It reads in motion, not in stills.
    52: 
    53: ## What the sim would need
    54: 
    55: - Quick boost: a time since the last quick boost began (or an impulse counter) on `FlightState`. Its direction comes from the thrust vector.
    56: - Assault boost: a flag on `FlightState`.
    57: - Until then the game plays the boost ignition when `boosting` turns on. The bench drives quick and assault boosts directly.
    58: 
    59: ## Bench
    60: 
    61:     /?view=thrusters&state=boost&t=0.5                 one state, a still at t seconds in
    62:     /?view=thrusters&state=quick&t=0.05&close=main     close on a main nozzle
    63:     /?view=thrusters&state=cycle&play=1                every state in turn, live
    64:     /?view=thrusters&cells=quick:0,quick:0.05,boost:0.5:main:178:4&cols=4&cw=480&ch=300
    65:                                                        a sheet, cells are state:t[:close[:yaw[:pitch]]]
    66:     &frame=heavy_C &palette=raider &yaw=150 &pitch=12 &dist=40 &light=0 &tier=low
    67: 
    68: States: idle, cruise, boost, quick, assault, brake, strafe. `tools/thruster-sheets.sh <dir> <tag>` renders the four review sheets headless.
  • run_command{"CommandLine":"python3 -c '\nimport re, base64, os\noutdir = \"~/.gemini/antigravity-cli/brain/cea9ec26-a0ce-4401-a5d2-36df51bb07b3/scratch/reflect_imgs\"\nos.makedirs(outdir, exist_ok=True)\nwith open(\"~/context/reflect/sortie.html\") as f:\n text = f.read()\nfor idx, m in enumerate(re.finditer(r\"data:image/([a-zA-Z0-9]+);base64,([A-Za-z0-9+/=]+)\", text)):\n ext, b64 = m.group(1), m.group(2)\n path = os.path.join(outdir, f\"img_{idx}.{ext}\")\n with open(path, \"wb\") as out:\n out.write(base64.b64decode(b64))\n print(path)\n'","WaitMsBeforeAsync":5000,"toolSummary":"Extract embedded images from sortie.html"}

    input

    {
      "CommandLine": "python3 -c '\nimport re, base64, os\noutdir = \"~/.gemini/antigravity-cli/brain/cea9ec26-a0ce-4401-a5d2-36df51bb07b3/scratch/reflect_imgs\"\nos.makedirs(outdir, exist_ok=True)\nwith open(\"~/context/reflect/sortie.html\") as f:\n    text = f.read()\nfor idx, m in enumerate(re.finditer(r\"data:image/([a-zA-Z0-9]+);base64,([A-Za-z0-9+/=]+)\", text)):\n    ext, b64 = m.group(1), m.group(2)\n    path = os.path.join(outdir, f\"img_{idx}.{ext}\")\n    with open(path, \"wb\") as out:\n        out.write(base64.b64decode(b64))\n    print(path)\n'",
      "WaitMsBeforeAsync": 5000,
      "toolSummary": "Extract embedded images from sortie.html"
    }

    result, 6 lines

    Command exited with code 0.
    
    Command output:
    ~/.gemini/antigravity-cli/brain/cea9ec26-a0ce-4401-a5d2-36df51bb07b3/scratch/reflect_imgs/img_0.jpeg
    ~/.gemini/antigravity-cli/brain/cea9ec26-a0ce-4401-a5d2-36df51bb07b3/scratch/reflect_imgs/img_1.jpeg
    ~/.gemini/antigravity-cli/brain/cea9ec26-a0ce-4401-a5d2-36df51bb07b3/scratch/reflect_imgs/img_2.jpeg