Written against the actual repos rather than a template. Every number is read out of
the code or computed from prices the code itself records.
THE FINDING THAT SETS THE SEQUENCE. lib/levelcode.rb carries an unresolved note from
the team — the plan caps were sized against an older ~$0.66/$3.41 flagship and want
re-checking. Costed at the current list prices in that same file, one fully-consumed
plan-month:
Pro $20 -> $18.10 +9%
Pro+ $40 -> $41.65 -4%
Max $60 -> $65.20 -9%
Pro+ and Max sell below cost at full burn with no prompt caching; only a high cache
rate pulls them back above water. The structural read matters more than the numbers:
margin comes from UNUSED allowance, not usage — so the heaviest, most vocal users are
the least profitable, which inverts the usual instinct for a developer tool that
selects for exactly those people.
The number that settles it is already recorded: usages.cached_input_tokens, per row.
One query. That is why it is a gate and not a footnote.
TWO CORRECTIONS I MADE TO MY OWN DRAFT.
The IPv6 claim was wrong on first pass. `dig +short AAAA www.levelcode.ai` printed a
CNAME and I read it as "www is dualstack, the apex is not". Re-checked: neither name
has AAAA, and neither does the Elastic Beanstalk load balancer behind them. The whole
stack is IPv4-only. The fix is also ordered — dualstack the load balancer FIRST, then
add the records, because an AAAA resolving to nothing serving is a hard failure rather
than a slow one.
A claim that macOS is "roughly a third of professional developers" is softened to a
directional statement, flagged for confirmation against a current survey before it goes
in a deck. It was recalled, not sourced.
Also corrected a stale memory in passing: credit_wallets.product now separates LevelCode
from thin.ly for reporting, and levelcode_stripe_id is gone. My note said the opposite.
Phases: 0 gates (IPv6, margin, claims-vs-build) -> 1 instrument -> 2 position ->
3 channels in order -> 4 pricing -> 5 scale gates. Deliberate omissions (no Windows, no
enterprise, no launch event) are listed with reasons so they can be argued with.