The numbered release each AI tool runs on, your update policy, and when an old release retires.
Safeguard, Orbit and Ask PCIFIC each run on a numbered release, written major.minor.patch (for example 2.0.0). A release is a frozen snapshot of everything PCIFIC controls about a result: the prompts, the tool definitions, the order PCIFIC tries its models in, and the defaults of the settings. A release is never changed once any business has used it. A change ships as a new release. PixelTrace uses no AI prompt, so it has no release.
Today every account runs 2.0.0 for all three tools. This page explains how releases will move when a newer one is published, so you know what to expect.
Each tool has an update policy that decides where it goes when a newer release is published. You choose it for each tool on the Versions page of the dashboard.
| Policy | Shown as | What it does |
|---|---|---|
latest | Latest (the default) | Follows every new release. |
patches | Patches | Stays on its major.minor line and takes that line's fixes. A bigger change waits for you. |
pinned | Pinned | Stays exactly on one release until an owner or admin chooses another, or until that release retires. |
Going back to an older release pins the tool there. You can also skip a newer release so that no policy moves you to it. Choosing it later still works. Owners and admins make these changes on the Versions page (/dashboard/versions). Employees can read it. Every change is in the audit history on the Privacy page.
A request that has already started keeps the release it started on, even across a retirement, including questions waiting for a seller's answers and failed work you retry. Nothing ever changes an answer that is being written.
A result names the release that produced it in a release field: at the top of an Ask PCIFIC answer, and inside the pcific object of an Orbit listing and a Safeguard review. There is no release header on the response.
GET https://business.pcific.ai/api/v1/releases (a key with the read permission) returns, for each of the three tools, the active release, your policy, every release with its notes, the notices that apply, and a line for each retirement warning. It is read only: you change releases on the Versions page.
curl https://business.pcific.ai/api/v1/releases \
-H "Authorization: Bearer $PCIFIC_TEST_KEY"| Field | Type | Required | What it is |
|---|---|---|---|
tool | string | Yes | safeguard, orbit or ask-pcific. |
policy | string | Yes | latest, patches or pinned. |
activeVersion | string | Yes | The release your next request runs on, for example 2.0.0. |
latestPatch | string | Yes | The newest release on the same major.minor line. |
releases | object[] | Yes | Newest first: {version, impact, publishedOn, notes, retiresAt, retired, active, skipped, knownIssues}. |
notices | object[] | Yes | Notices that apply to your active release: {id, kind, kindLabel, impact, affectedVersions, fixedIn, observed, effect, createdAt, acknowledged}. |
needsAcknowledgement | string[] | Yes | The ids of Critical notices on your active release that an owner or admin has not yet answered. |
retirementEvents | object[] | Yes | {message, at}: the warnings and moves that retirement made for you. |
PCIFIC publishes a notice about a release for a known issue, a model retirement or the end of support. It says what was observed, which releases it affects, what it may mean for you and which release fixes it. A notice is Optional, Recommended or Critical. Owners and admins of a business running an affected release are emailed. A Critical notice on the release you run asks an owner or admin to upgrade, or to record an explicit choice to stay. Nothing moves you without that choice until the release retires.
A release note describes a change. It is not evidence that quality changed. A release fixes the order PCIFIC tries its managed models in, not one exact model: if a provider retires or cannot serve one, the next answers. On Bring Your Own a release fixes PCIFIC's prompts and tool definitions, and the model is your own.