Public changelog status
Runtime is in development. These guides explain design intent; they are not a released API or installation reference. Read the release policy →
No public Runtime release entries
Section titled “No public Runtime release entries”There is no approved public Runtime version or downloadable distribution on this website. Internal milestones are not presented as public releases, and this page does not publish private development history.
The launch of the public website, when approved, is a web release. It does not change Runtime’s development status.
What future entries will record
Section titled “What future entries will record”Each public release entry should name the release identifier, publication date, artifact location, documentation version, supported environment, and verified changes. Entries should distinguish additions, changed behavior, fixes, known limitations, and compatibility impact.
Security information requires review for a useful and responsible level of detail. No unsupported compliance or hardening claim should be inferred from a dependency update.
Evidence belongs with the release
Section titled “Evidence belongs with the release”A changelog entry should link to integrity and authenticity instructions, a compatibility matrix, and any migration guide. Readers should be able to tell whether an example applies to their installed version.
No dates or versions are invented to fill this page. The downloads page remains the source for public artifact availability.
Documentation corrections
Section titled “Documentation corrections”Conceptual docs may improve independently of a product release. Corrections should clarify the design model and retain the conceptual label until implementation-specific claims have passed review.
Read the release lifecycle for the evidence required to publish a release reference.