AI Flow

⋯ 1 unchanged line ⋯

@@ -16,3 +16,11 @@ The evidence of a run is its video, and the video is built from the steps, not r ## Disk  Window capture writes H.264 from the box's GPU encoder as it records (no raw frames on disk, no screenshot polling) and only when the window changes, so a static board while the AI thinks costs almost nothing: the ESC replay was 128 MB for 17 minutes with routing landing the whole time, about 8 MB per minute of change. A monitor capture at 4K is about 115 MB per minute and is not used. The budget per step is the flow's expected minutes at 10 MB per minute, doubled for the pull and the 10x cut; `capture open` reports the whole run's budget against the run drive and the test box, and a step refuses to start its clip when either has less than the budget plus a 1 GB floor. Raw clips are kept as evidence next to their 10x cuts; the raw ones are the space, delete them from old runs first.++## The output spec++The final video is 1920 x 1080, 16:9, 30 fps, H.264 (yuv420p) with AAC audio, whatever the recorded window was. A clip is scaled to fit with its aspect kept and letterboxed or pillarboxed on the dark ground (0x0B1420); it is never stretched. The per-step cuts keep the window's own shape (they are evidence); `compose` normalises them.++## Plan usage is per account++The plan-usage snapshots are the provider's per-account numbers. Every AI thread signed in as the same user draws on them, so a run made while other threads were working shows their usage too. The run page says so under the table; read the delta as an upper bound unless the run was the only thread active.

@@ -1,7 +1,7 @@ {   "slug": "adom-aiflow",   "type": "app",-  "version": "0.1.9",+  "version": "0.1.10",   "title": "AI Flow",   "description": "Adom's AI Flow: a tool to help the AI follow all of the steps it takes to build a board. One Rust binary with a crate per step (placement helpers, a grid router with Kelvin taps, pours with keepouts, KiCad's DRC gate, live landing through the KiCad Bridge, copper measurement, current and thermal analysis) and a finish line that refuses an unfinished board. Every command answers with hints for the AI; every turn, its thinking time and every rework loop go into run.jsonl, so Claude, Codex and any other engine are compared on the same flow. KiCad today; Altium, Fusion and Adom's own web apps next.",   "summary": "Adom's AI Flow: a tool to help the AI follow all of the steps it takes to build a board. The AI thinks its way from placement through routing, pours, current and thermal analysis to a delivered video; the binary does the fast, deterministic parts of every step, hands back hints, and keeps a ledger of every turn, every return to an earlier step, and the clock from the prompt to done.",

@@ -1,7 +1,7 @@ {   "slug": "adom-aiflow",   "type": "app",-  "version": "0.1.9",+  "version": "0.1.10",   "title": "AI Flow",   "description": "Adom's AI Flow: a tool to help the AI follow all of the steps it takes to build a board. One Rust binary with a crate per step (placement helpers, a grid router with Kelvin taps, pours with keepouts, KiCad's DRC gate, live landing through the KiCad Bridge, copper measurement, current and thermal analysis) and a finish line that refuses an unfinished board. Every command answers with hints for the AI; every turn, its thinking time and every rework loop go into run.jsonl, so Claude, Codex and any other engine are compared on the same flow. KiCad today; Altium, Fusion and Adom's own web apps next.",   "summary": "Adom's AI Flow: a tool to help the AI follow all of the steps it takes to build a board. The AI thinks its way from placement through routing, pours, current and thermal analysis to a delivered video; the binary does the fast, deterministic parts of every step, hands back hints, and keeps a ledger of every turn, every return to an earlier step, and the clock from the prompt to done.",

@@ -40,7 +40,7 @@ Get it right with one engine first, on a fresh prompt, from `start` to `deliver`  ## Plan usage, the second cost line -Neither engine can see its own token bill reliably, so the binary reads what the provider shows the human: the percent used of every plan limit (Claude: the 5-hour window, the week, and each model-scoped weekly limit such as Fable; Codex: its primary and secondary rate-limit windows), from the Claude Code and Codex sign-ins in the container, with the same calls the Hydrogen usage widgets make. It snapshots at `start`, at every `step`, at `finish` and at `deliver` (`adom-aiflow usage` any time), writes each snapshot to run.jsonl, and the summary and the run page show "Fable 13 % to 16 %" per limit. That is the cost line to compare when tokens and dollars are nulls.+Neither engine can see its own token bill reliably, so the binary reads what the provider shows the human: the percent used of every plan limit (Claude: the 5-hour window, the week, and each model-scoped weekly limit such as Fable; Codex: its primary and secondary rate-limit windows), from the Claude Code and Codex sign-ins in the container, with the same calls the Hydrogen usage widgets make. It snapshots at `start`, at every `step`, at `finish` and at `deliver` (`adom-aiflow usage` any time), writes each snapshot to run.jsonl, and the summary and the run page show "Fable 13 % to 16 %" per limit. That is the cost line to compare when tokens and dollars are nulls. Footnote it every time: the limits are per account, so other AI threads signed in as the same user move the same numbers; the delta is an upper bound unless the run was the only thread active.  ## Cost, two ways