Models & APIs — by function

The console's Models & APIs tab regrouped onto the ledger's eight groups — speech · fp · tool · kit · persona · photo · room · app — in the Usage & cost tab's order and colours, so a figure on Usage ▸ By function and the knob that moves it are one hop apart. Every leaf of the vocabulary gets a row, including the eleven that have no knob today.

1 · Two maps of one thing

A reader of the console holds two different groupings of the same money. Usage stacks spend by the ledger's call kind — the closed group.leaf vocabulary of usage-dashboard §3, eight coloured groups. Models lays the knobs out by which part of the product they sit in — six uncoloured surfaces. So「kit cost $3.10 this week」sends the reader to Models to find… no kit.

The eleven missing leaves — kit.* ×5, persona.* ×4, photo.* ×3 less the eyes' price row, room.translate, speech.interrogate, tool.promised — are not missing by accident: their model is a constant in code, so there was never a knob to draw. But the page is read as an inventory (「every model & search API, by role」 is its own subtitle), and an inventory that omits a third of the ledger is a page that cannot answer「what runs persona.dream?」.

The three rules of the regrouping

1. Same eight, same order, same colours. The groups are U_GROUPS — the usage tab's own list, in the same file. A group rail under the tab title is the usage chart's legend made a navigation: one chip per group, the chart's colour, the leaf count; click to jump, and it follows the scroll.
2. Every leaf has a card, and every card is the same card. The key is the stored kind (room.translate), then the name (Translate on divergence); the rows are the console's radio rows. Where a setting exists the rows are the choices you have today, untouched. Where the model is a constant in code the card has one row, one radio, checked — the fact, in the same format as a choice. Where inherit is the default, the Inherit row is written out, followed by the model it resolves to. Every row marks thinking — thinking off / thinking on as a word, with the switch beside it where it is a choice — so a call that cannot think says so instead of saying nothing. No descriptive text anywhere; the server reports the constants, the page never names a model itself.
3. Prices stay one surface — a ninth, neutral stop at the end. It is not a group; it is what every group above is billed from.

2 · The tab

Markup and classes lifted from lib/admin.html, set in sans; the rail, the group header, the kind-as-key card header and the thinking mark are the new pieces; every row is the console's .mrow.

3 · The map — every leaf, its row

The build follows this table: 28 stored kinds, where each sits today, and what its card holds. choice = an existing setting, moved as-is · one radio = a constant in code, one checked row · inherit = an Inherit row, checked.

4 · What changes (the plan, as built)

• Render order only, on the front. loadModels() emits the groups in U_GROUPS order with the new .fgrp header; every card, every POST endpoint and every change handler is the same code — a card moves, it does not change.
• The one-radio cards come from the server. GET /api/admin/models grows a fixed block — {leaf: {model}}, or {inherit: true} — read from the constants themselves (MEMORY_MODEL, PHOTO_MODEL, PHOTO_DENSE_EYES, ACT_GATE_MODEL, …). The renderer draws it as the same .mrow it draws a choice with — one radio, checked, no handler. The page never hard-codes a model name, so a constant that moves in code moves on the page the same commit.
• The prop master: Off · V4 Pro · V4 Flash — one radio group; Off posts prop-gate on=false, a model posts on=true + the model. Same two endpoints as today, one control instead of two.
• One lint, because the vocabulary is closed. The smoketest checks that every kind the ledger can book (db.KIND_ALIAS values + the §3 table) appears as a .kind key in the Models render — a new leaf with no row fails the gate, the way a new kind with no colour already does.
• The rail's colours are the chart's. --s1…8 already live in theme.css for the usage tab; the rail, the group name and the kind key all wear them (a --fc per group section). No new hue anywhere.
• Sans for all. The tab drops mono — card header, kind key, chips, the thinking mark, the price table — everything is var(--sans); the tab title keeps the console's serif. 「reasoning」becomes「thinking」on the switch label, and the state is written out beside it.
• Two rows go. room.title offers Flash only (the Pro row is removed, the setting collapses to a single checked radio); the prop master's switch folds into its list.
• Usage › on a group header opens the Usage tab scrolled to that group's By-function row — a hash the usage loader already knows how to read is enough; no new endpoint.
• Docs: this page flips to BUILT in the ship commit; usage-dashboard §3 gains a one-line pointer here; the console-redesign Models section gets a「superseded by」note.

5 · What shipped beyond the mock — the owner's build rules

• fp is split in the ledger — fp.open (the opening staging, _open_stage) · fp.mid (the per-turn director, _f_engine + the two drain sites). staging aliases to fp.mid; a row booked as plain fp before the split stays fp — open or mid was never recorded, so it is never guessed. The mid-chat lead row reads Code, not Mechanical.
• Sonnet 5 replaces Sonnet 4.6 on the panel (claude-sonnet-5; better and cheaper on the intro price). MODEL_RETIRED + model_now() read a room saved on 4.6 onto the Sonnet 5 seat at resume and at switch, so a Sonnet chat stays a Sonnet chat. ⚠ On Sonnet 5 an omitted thinking runs adaptive thinking (4.6 ran none) — the panel call now sends thinking: disabled explicitly, so the row's「thinking off」is true.
• Gemini 3.7 Flash replaces 3.5 in the Studio (builder.MODELS, the default audit_b, the moderation fallback); a saved step matrix naming 3.5 reads onto 3.7 (builder.MODEL_RETIRED).
• The price table is curated to what runs: Sonnet 5 · V4 Pro · V4 Flash · V4 Flash Vision (its own row in cost.PRICES now) · Gemini 3.7 Flash · Gemini Embedding. Opus and Haiku are off the table — cost.py still prices them, so the Claude web-search dispatch (Haiku) bills from the built-in sheet, uneditable here. Every figure shows as 1.0000; STT keeps six decimals because $0.000361 at four would read $0.0004.
• Inherit follows the default, live — the three Inherit rows (speech.empty · tool.act · kit.authoring) re-resolve the moment the Panel card's default radio moves, before the save round-trips.
• The dense-picture eyes follow the panel: when the default panel model is Flash Vision the row reads DeepSeek V4 Flash Vision · tiled (a seeing room's own tiles read the picture); any other default reads Gemini 3.7 Flash — the routing table's rule, shown.
• room.title is Flash only — the endpoint offers one option; one checked radio.
• kit.authoring became a setting (owner, after the build): Inherit the chat's panel model (default, unchanged behaviour) or V4 Pro — authoring_model, POST /api/admin/settings/authoring-model, DeepSeek only like the act call; the call bills and tallies under the model it actually ran.
• Every fixed seat is a constant the server names — KIT_CLERK_MODEL was hoisted out of three inline literals for it, and the wake-door check now follows ACT_GATE_MODEL (env-movable) like the quick act gate it is.
• The two hops — a group header's Usage › opens #usage/<group> and flashes that By-function row (or the table, when the window holds no spend for the group); a By-function row's function cell opens #models/<group> and flashes the section.
• Sans for all on the tab, scoped to #sec-models; the usage tab keeps its mono.