Alpha. Here's exactly what that means.

Where these states come from.

One file drives every state on this site: content/status.json. The label on this page and the label beside a claim on features are the same value, read twice. A label that does not exist in that file fails a test before it can reach a page.

Five states are allowed, and each means one thing:

• live — in the build today, and checkable by someone who is not us.
• alpha — in the build, not yet proven on target hardware.
• under validation — being proven on-device right now, under PASS HOLD.
• planned — not shipped. Named so its absence stays visible.
• pending — the state itself is not yet confirmed against the build tree.

A state moves only when a person edits that file and signs the change. No code promotes a state, and no page overrides one. pending is the honest answer for a mechanism we have not confirmed, and it stays until the build tree says otherwise.

Read live narrowly. It means a component is in this build today, inside an alpha operating system. It does not mean the operating system is finished, and this page exists so that the two are never confused.

What this page will not tell you.

Three things are missing from this page on purpose, and their absence is the most useful part of it:

• A date for anything marked planned. A date on unshipped work is a forecast, and a forecast on a security surface reads as a commitment.
• An update cadence. None is committed while on-device validation is held.
• A device-support promise. This site writes target for the Pixel 8 and Pixel 9 families until that changes on devices.

There is also no third-party review of this build, and none is claimed. If any of the three arrives, it arrives here first, dated in the changelog, and then propagates to every page that reads this file.

What PASS HOLD means.

PASS HOLD is the plainest way we can say this: the build has not passed on-device validation, so nothing is released.

Validation runs the image on target hardware and checks the behaviour we document. When a check fails, the release is held rather than shipped with a note. We then bisect: we walk back through the changes between the last good run and the failing one until the change responsible is identified. The hold lifts when the run passes, not when the calendar says it should.

While the hold stands, four things follow, and they are stated on every surface of this site. No release is presented as finished. No update cadence is committed. Every hardening claim keeps the state this board gives it.

And the posture pill in the header keeps the word alpha.

If you are evaluating GuardTalkOS for a newsroom, an NGO or a field team, the honest answer today is "not yet". A held build is not a broken one, and a bisect in progress is ordinary engineering. It is still not something to hand to a person whose safety depends on it. Read the threat model and decide against that, not against this page.

Status changelog.

Every change to a state lands here with the date it was made. A state that moved without an entry would be a state nobody signed. The entry and the change are one edit to content/status.json.

Entries are dated in the past. Where an item is planned, it carries that word and no date. A date on unshipped work is a promise, and this page makes none.