# Beta Charter

> Check an early-access, preview or design-partner API program before the first account enrolls, and decide the betas
> that never ended. Describe the feature and paste the stage contract, the accounts you want in and any live beta; the
> browser ranks the program shape, reads every contract row of every stage, checks the stage is on the wire, the time
> box, freeze and extension rule, holds every account to the entry criteria and the capacity cap, reads the sign-offs
> and decides every perpetual beta. Metered runs write the program charter, and the rescue. Built on the SkillSafe
> skill @samber/api-beta-program, from samber/developer-platform-skills (MIT), by Samuel Berthe.

https://beta-charter.skillsafe.ai/

## What is free
- The shape: private preview by default, design partners when the shape is open or the resource model is new, the hybrid when GA is near, fewer than three qualified accounts falling back to design partners, an additive change skipping the beta, and no owner ruling every shape out.
- The stage contract: the eleven rows (access, availability, support, breaking changes, removal, production use, pricing, data and compliance, limits, marking, discontinuation) for private and public preview, empty rows marked; a personal-data ban that makes the beta unusable, a missing precedence clause, an SLA on a moving public preview and internal SLOs in the terms caught.
- The wire and the exit: a stability suffix, base path, header or per-subscription opt-in against the versioning scheme, SDK pre-release channels, production-use detection; a time box of at most twelve months before the GA target, a freeze at least one partner release cycle before the review, an activation floor, one extension.
- The cohort: every account against the five entry criteria, the cap from partner hours, concentration above a third of traffic, production use with no exception; the five enrollment sign-offs; every beta that never ended decided GA as-is, next version or kill; plus a contract table, a rescue CSV, the checks (.csv) and everything (.json).

## The metered lanes
Two tasks on gpt-terra, metered per run, routed by `task`. Input string fields: `task` (charter or rescue), `program`, `register`, `carry` (rescue only: the charter's decisions) and `facts`.
- `charter` replies with `summary`, `shape`, `contract` (eleven rows per stage), `wire`, `exit`, `cohort` (each account's decision), `signoffs` and `caveats`.
- `rescue` replies with `summary`, `surfaces` (each with its decision, owner, private notice and grandfathering), `retroactive` and `caveats`.
The page holds every reply to its own facts: the ranked shape, every row in order with no SLO in the terms, the page's mechanism, a bounded exit, each account and surface decided as the page reads it, owners never invented, and a kill with months of notice, an export and an alternative.

## Links
- API tutorial: https://beta-charter.skillsafe.ai/api.html
- Source skill: https://skillsafe.ai/skill/@samber/api-beta-program