Phase 2.46 / v1.5.65

Roadmap

See the distribution and runtime gates that must close before broader public release claims can be made.

Readiness gates

The future is sequenced, not hand-waved.

LocalEndpoint can be useful for invited users now while broader distribution waits for installer, signing, update, evidence, accessibility, and certification gates.

01 / Now Public clarity is live

Docs, route metadata, schemas, examples, browser validation, and quality gates explain the system without runtime control.

02 / Invited Invited distribution is useful before broad public launch

People you directly know can use checksum-backed artifacts, Desktop review, and evidence packets while distribution gates keep closing.

03 / Distribution Installer signing and updates need evidence

Clean-machine validation, update behavior, accessibility review, and artifact signing must be proven before broad installer claims.

04 / Certification Certification-ready is not certified

Readiness evidence can be organized now without claiming marketplace approval, runtime safety certification, or autonomous execution approval.

StatusRoadmap status

Machine-readable readiness gates and public distribution posture.

QualityQuality gates

Current checks for public boundaries, route clarity, and artifact readiness.

VerifyDeployment verification

Packet validation without deployment authority or external uptime polling.

Pre-betaPre-beta quality

Invited-use readiness separated from public launch and certification claims.

ArtifactsDownload path

Portable ZIPs, toolkit packages, manifests, checksums, and source-build notes.

DesktopLocal approval surface

Human review, receipts, and future endpoint handoff stay on the device.

Roadmap contract Invited use is not broad launch Evidence before claims No certification claim yet No marketplace approval claim

Distribution cockpit

Ready enough to share, honest enough to review.

The website should make the current posture legible at a glance: invited users can download bounded artifacts, reviewers can inspect evidence, and broad public launch waits for signed installers, update proof, accessibility evidence, and certification work.

Available now Checksum-backed artifacts

Portable downloads, manifests, samples, and toolkit packages can be inspected before anyone trusts a local endpoint.

Invited circle Useful for people you directly know

The current posture supports hands-on review without presenting the project as a general-public launch.

Launch gates Signing, updates, and clean-machine proof

Distribution language should change only after installer, update, accessibility, and deployment evidence is captured.

Claim boundary Certification preparation is not certification

The roadmap can organize review evidence now while marketplace approval and runtime safety certification remain unclaimed.

Current distribution stance Downloadable for invited users Checksums before trust Evidence before wider launch Certification claim withheld

Now

Useful without overclaiming

The website can already explain, validate, publish metadata, and distribute bounded artifacts for invited users.

Overview

Close installer gates with proof

Signing, updates, clean-machine validation, and accessibility checks should leave evidence before broad distribution language changes.

Verification

Later

Certification claims wait for certification

The roadmap can prepare evidence for review without saying marketplace approval or runtime safety certification is complete.

Quality gates

Operating boundary

Public clarity, local authority.

This public site is static metadata and does not dispatch desktop commands, probe localhost, upload files, collect telemetry, request credentials, or claim runtime safety certification.