Versions

Deprecations

The lifecycle status of each A8 version, how much notice a retirement gets and how to watch for one.

This page as Markdown: https://u22a8.ai/docs/deprecations.md. The index of every docs page: https://u22a8.ai/llms.txt.

Every A8 version carries a lifecycle status. It says whether the version serves, whether its interface can change and when it retires. This page defines each status, states the notice a retirement gets and lists every version with its status.

§1Lifecycle statuses

StatusMeans
PreviewAvailable, with an interface that can change between versions
BetaA feature available to use, with an interface that can change
DeprecatedAvailable, with a retirement date set
RetiredPast its retirement date and out of service
Table 1.

The lifecycle statuses. Every page that names a status means it as defined here.

A status shows as a badge beside a page title or a sidebar entry, with one sentence on what it means for you. A8 is in preview: a pinned version holds what it learned, and a new version can change how a request is read.

A horizon belongs to the version that fitted it, so it shares that version’s status and retires with it. See Model identifiers.

§2Notice

We announce a deprecation at least TBD (notice period) before the retirement date. Each announcement appears in three places on the same day:

  • Release notes, as a Deprecation entry
  • The history on this page
  • GET /models, on every entry of the deprecated version

From the announcement to the retirement date, the version answers as it did, pinned horizons included.

§3Versions

VersionStatusReleasedRetirement dateReplacement
a8-1PreviewTBD (launch date)None setn/a
Table 2.

Every A8 version and its lifecycle status.

§4History

Each deprecation is an entry here, newest first. An entry is a heading with its date and title, one sentence that names the version, its retirement date and its replacement, and a table:

Text
### 2027-01-15: a8-1 deprecated

On 2027-01-15 we deprecated `a8-1`. It retires on 2027-07-15. Use `a8-2`.

| Retirement date | Model | Replacement |
| --- | --- | --- |
| 2027-07-15 | `a8-1` | `a8-2` |

The dates in this template are examples. The history starts with the first deprecation.

§5Watching for a retirement

GET /models carries each version’s lifecycle on every one of its entries, so a script reads the same status this page shows:

Shell
curl https://api.u22a8.ai/eval/v1/models \
  -H "Authorization: Bearer $U22A8_API_KEY"
JSON, annotated
// annotated, trimmed: one entry of the list
{
  "id": "a8-1-1@20260715t140322z",
  "object": "model",
  "status": "ready",
  "active": true,
  "lifecycle": "preview", // a status from Table 1, lowercase
  "shutdown_date": null // an ISO date once the version is deprecated
}
FieldTypeMeaning
lifecycle"preview", "beta", "deprecated" or "retired"The version’s lifecycle status
shutdown_datestring or nullThe retirement date as YYYY-MM-DD, set when the version is deprecated
Table 3.

The lifecycle fields on each GET /models entry.

See Horizons for status and active, the fields that say which horizon is in service.

Next steps