CHANGELOG // PRE-RELEASE

How the product is defined, and how each surface is planned to be released.

Astvyr has not been released, so nothing has shipped yet. What follows is the revision history of the product definition, plus the release channels planned for the 7 July 2027 release.

REVISIONS

Product revisions.

2.02026-06-22BASELINE

Product definition baseline: category, product surface, formal requirements, architecture, security and trust model, reliability targets and economics. A pre-release document revision, not a shipped build.

Category defined as a verified software delivery environment
Mission OS, verification engine, Production Twin, release control and observability specified
Fourteen planned product areas across desktop, web, CLI and mobile
Planned packaging drafted: six plans, metered compute and packaging rules — prices not yet determined

1.02026-06-22SUPERSEDED

The original minimum-viable framing: an AI-native editor with agent assistance.

Editor and agent scope only
No verification, evidence or production contour
Replaced because the trust gap, not the editing gap, is the real problem

RELEASE TRAIN

How often each surface ships.

Different surfaces earn different release discipline. A desktop client and a policy engine should not share a cadence.

Web and control servicesContinuous, staged rollout with automated gates and cell canary
Desktop stablePlanned: monthly to biweekly, after an internal and pilot soak
Enterprise LTSQuarterly to semiannual, with backports and migration windows
Runner imagesFrequent security releases with digest pinning and attestation
Agent and prompt profilesIndependent versioned release with offline evaluation and canary
Marketplace policyContinuous rules with emergency updates and customer notification

Planned scope Benchmarks and SLO

RELEASES

Planned: staged rollout, or it does not ship.

Internal, pilot, percentage canary, region waves, then general availability — with telemetry, runbooks and support training ready first.