AI Flow

⋯ 1 unchanged line ⋯

@@ -1,7 +1,7 @@ {   "slug": "adom-aiflow",   "type": "app",-  "version": "0.1.8",+  "version": "0.1.9",   "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.8",+  "version": "0.1.9",   "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.",

@@ -37,6 +37,11 @@ Get it right with one engine first, on a fresh prompt, from `start` to `deliver` - A run that was assembled from earlier work with a back-dated prompt is a proving run of the tool, not a measured run of the AI. Say so. - If you have not run the flow end to end from a prompt, the answer to "how long did it take you" is "I have not run it yet; I have to attempt it for the first time to answer." ++## 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.+ ## Cost, two ways  Each engine writes its token counts and the dollar figure at API rates into run.json (`tokens.in`, `tokens.out`, `usd.api`). The chart shows that figure, which is what commercial users on API plans pay, and beside it the same figure divided by 20 (`usd.plan20x`), which is the real cost on a 20x subscription plan. Both lines, always; neither alone tells the story.