Allternit Model and Plan Redesign

We already collect most of what Hermes shows. Our telemetry stops at web Settings, the picker is a small provider table, and plans look like price lists. This redesign moves the telemetry into the model sheet, gives each plan a member card, and sells plans as tickets. The art uses our A-block mark and HUD blocks, so it does not copy Nous. Nothing is built yet. Four decisions are open.

What Hermes has that we do not

table

| Feature | Hermes and others | Our web and PWA | Our iPhone app | Work || Model sheet with one control per setting | Yes | no | no | Redesign the sheet || Thinking slider | 7 levels | 4-part switch | 4-part switch | New block slider, 4 real levels || Fast tile | Yes | no | no | Left out: we have no fast mode to switch || Approval tile | Yes | ok: a separate pill | warn: not checked in the picker | Move into the sheet || Limits per account, with resets | Yes | ok: Settings only | no: Cloud total only | Add quota calls to iPhone, show in the sheet || Tokens, cost and daily trend | Yes | ok: Settings only | no | Reuse the usage ledger, add an iPhone read || Rings per provider | Yes | no: flat bars | no | New Usage cards || Member card | Yes | no | no | New card, 4 tiers || Buying as tickets | Yes | no: plain boxes | no: link rows | New tickets || Sketch to attach | Yes | no | no: PDF signing only | PencilKit in the composer || Notification ask with examples | Yes | not checked | warn: plain sheet | New look |

The name change, and what it breaks

On October 30, Anthropic renamed Max 5x to Max and Max 20x to Ultra. Prices stay at $100 and $200. Verified Ultra accounts lose the 5-hour limit. Max keeps it.

table

| Price | Claude | Nous Portal | Allternit today || $20 | Pro | Plus | Plus || $100 | Max | Super | Super || $200 | Ultra | Ultra | Ultra |

Our Claude label is out of date

claudePlanLabel shows "Max (20x)" for an Ultra account. The new Usage cards must show "Ultra". I fix this in the build. I also checked that the windows come from the server, so a missing 5-hour window needs no special case in the web code.

Our iPhone app uses a plan name we do not sell

PayLinkRows says "Get Pro". We have no Pro plan. I fix this in the build.

Our names match Nous word for word. The prices are also the same, except where the secondary sources disagree on Super. Only the labels change if you rename. Plan ids and Stripe prices stay, so existing subscribers keep their plans. The names on the live Stripe products are a Stripe write. They need your sign-off.

What should our $20, $100 and $200 plans be called?Keep Plus, Super, Ultra suggestedno migration, but the same as NousPro, Max, Ultrasame as Claude, easy to understand, but "Max" can look like the Claude planOur own namesmost distinct, needs a naming round

Model sheet

One sheet for chat, code and bots. The header shows the current model and its tightest limit. The block meter is the slider. Tiles hold thinking, approvals and context. A second page holds all models. We do not show a Fast tile until a real fast mode exists.

React · Model sheet

Which model sheet should I build?A, Control sheet suggestedsettings first, one limit in the headerB, Limits firstring and telemetry on top, more to read

Usage

Each connected account gets one card. The rings use the 80% and 95% lines we already enforce. An account that does not report limits says so. It shows no fake bar. Claude Ultra shows no session row, because it has no 5-hour limit.

React · Usage

Member card and plan tickets

You own a card. You buy a ticket. The card shows tier, member name and renewal date. Only Ultra has the color-shifting border, so the top tier looks different. All plan facts on the tickets come from our real catalog. The card also has states for Free and failed payment.

React · Plan card and tickets

What art should the member cards use?Halftone A mark, drawn in code suggestedsharp at any size, same on all surfacesASCII A mark, drawn in codematches our ASCII backgroundsIllustrated Gizzi scenes, one per tiermost character, needs generated art and your review

Other things in your screenshots

The sketch sheet in your screenshot is Apple's PencilKit with its standard tool picker. We can use the same tools in the composer. Claude's notification ask also shows real examples, and the mockup below does that with bot events. It leaves out promotions, which Claude's sheet bundles in.

React · Notification ask

Which extras go in this build?New notification ask suggestedSketch to attach on iPhone suggested

What the build changes

Web, PWA and Desktop share one code path. The iPhone app needs its own SwiftUI views. All surfaces and the docs ship together.

table

| Part | Web, PWA, Desktop | iPhone || Model sheet | Replace phone branch of `ModelPickerPopover`. Keep the desktop popover layout, add the same telemetry | Replace `ModelPickerSheet` || Thinking slider | New shared component, with keyboard and reduced motion support | SwiftUI port || Usage | Cards over `useManyProviderLimits` and the ledger, in Settings | New quota and ledger reads in `UsageStore` || Card and tickets | Rebuild the plan list in `BillingPlansSection`. Keep checkout, portal and top-up logic | `PlanUsageViews`, `ComputeBillingView`, keep `StorefrontGate` || Plan labels | `claudePlanLabel` in gizzi, plus a plan rename if you pick one | Remove "Get Pro" || Docs | Update billing, usage and model guides, then run `check_links.py` | Same docs |

What I did not check:

I rebuilt the "Today" screens from code and tokens. They are not captures from a running app.
I did not confirm that the ledger splits subscription accounts by provider. Cost may be Cloud only. A subscription card shows tokens only when we have them, and no cost.
The catalog may not list which thinking levels each model supports.
Nous pricing comes from secondary sources: Standard Compute, Toolradar. The Claude rename comes from The Next Web and 36Kr.