Major versions

Minor versions mint themselves at each deployment. Majors move only here, by hand: the website's takes effect at its next Development deploy (as N.0); the catalog's renames the working Development catalog to N.0 at once, and that is what its next deployment ships.

Deploy

One action, one hop. Pick what moves — anything not ticked stays exactly where it is. Software and data release on their own schedules; this is where they meet.

Development staging can also be thrown away: Revert Development to Production's catalog

History

Releases — pushed Conrad Tool, Services Tool and Desktop Viewer builds

Push a build from the dev box with deploy\publish-release.ps1 — every push lands in Development with its version and (for the Tool) the ability manifest it was compiled with. The radio picks the one build per kind the website's Downloads page serves — the Conrad Tool to creators, the Desktop Viewer to everyone on a plan with viewers, the Services Tool where a feature grants it. Deploying a kind moves the selected build to the next ring, where it becomes the only copy.

Conrad Tool

Services Tool

Desktop Viewer

Plans — one price, and the features it includes

Drag a row by its grip to reorder it — the order here is the order of the columns on the pricing page. Deleted plans keep the place they had.

Groups — the headings features are gathered under

The order here is the order on the pricing page's comparison chart. Drag a row by its grip to change it; a new heading lands at the end.

Features — what a plan includes, and what it grants

One thing, not two: a feature is the row a customer reads on the pricing page and the abilities they get. Put it on a plan and the plan grants it. Services aren't granted here: the tool governs them through the abilities. Drag a row by its grip to reorder it — within its own group, since the chart reads group by group; to move a feature to another group, edit it.

Promo codes — a percent off for a configured number of months

AI Providers — the models Ask Conrad may use

Wherever a model is picked, only the ones allowed here are offered: User settings in the Conrad Tool, a company's AI shared keys and AI User Keys on the website, and the Services Tool when it installs an AI Service. Dev allowed, between Model and Id, offers a model to this ring's test accounts alone — the Test Accounts tab's addresses — so we try it before a customer sees it. Refresh models asks the provider what it has now, with an API key you paste for that one request — it is not kept anywhere. A model listed for the first time arrives unticked. One the provider stops listing stays while it is allowed, marked, and goes at the next refresh once it isn't. Allowed models travel with the catalog: a change here reaches Early Release and Production when the catalog deploys.

Click a column's heading to sort by it; the newest release comes first until you do. Hide puts a model you offer nobody out of the way — either tick brings it back — and Show hidden models lists them again.

Llama isn't listed here. A company's AI Service fronts its own Llama server, and whoever installs it names the models that server runs.

Commerce settings — turned here, felt at each customer's next sign-in

Grace days travel inside each signed grant, so a change reaches a customer the next time they sign in — no app update.

Abilities — what each code does, and which Tool builds carry it

The codes a feature grants and the Conrad Tool checks. Code Description says what the code does with each one today, and First introduced is the build that first carried it — both kept in the code's ability history, and changed in the same commit whenever a Tool upgrade adds, renames or removes an ability. Latest included and Active come from the builds pushed to this ring's release registry.

Retired abilities

No longer granted or checked. Kept so a catalog or a cached grant that still names one reads as the ability it became — never as nothing.

Rules — what decides a customer's experience besides the abilities on their plan

Every rule that changes what a customer may see or do and isn't an ability: what a customer type carries, how far a role reaches, the state an account is in, the plan's own numbers, how Ask Conrad picks a route, our own accounts, and the door at signup. An ability is something a plan grants you; a rule is something true about your account whatever you bought. Kept in the code's rule catalog and changed in the same commit as the rule itself — read-only here, because changing a rule is a code change. Where is what actually enforces it: a rule the website merely hides, or one the tool applies on the customer's own machine, is marked soft with the way round it.

Companies — every account, and the support levers

Log out everyone ends every live session the company's users have — the tool, the website, everywhere. They simply sign in again.

The Slack channel only reaches a company's tool when its plan carries the Slack Channel Support ability; without it the address is stored but never handed out.

Research data — open a request, read out the code, read what comes back

Give the customer the code. Their tool submits its state against it once — a used code can't be submitted again, which is what stops the same problem arriving over and over.

Beta bugs — what beta users reported from the tool's Report Beta Bug button

Each ring keeps its own: these are the selected ring's. A new report is Open; write a note, mark it Reviewed, and Save. Who, when and which build come from the user's session, not from what they typed.

Student requests — signups asking for free student access

Each ring keeps its own: these are the selected ring's. A new request is Requested, and the account shows "pending approval". Approved gives the student their plan at no cost and emails them the code that activates the account; Denied emails a kind no, with support's address in case it was a mistake. An approved request stays approved. The note is ours — the student never sees it.

Test accounts — the addresses we sign up as, to see what a customer sees

Ten reserved sign-ins on this ring. Nobody reads their mailboxes: every code one of them would be sent — the activation code, a sign-in code, an email change — is delivered to the Conrad email beside it instead. Signing up with one takes no card and no billing address, and its invoices are paid like everybody else's.

One of these is as useful added to somebody's organization as a viewer or a creator as it is signing up for itself — the codes come to the Conrad email either way. What it is being used for is read off the account rather than written down: the company, the plan it is living under and every role it carries.

Use takes a free address. Reset hands it back empty — where the address owns the account that deletes the account, everyone on it, its billing history, its sign-in history and its sessions; where it is only somebody on another company, just that person goes and the company is left alone.

Account directory — which ring a username signs in on (empty = this ring)

Migrating an account: move its data to the other ring, add its row here, and its next sign-in lands there — the customer does nothing.