Release lifecycle
Runtime is in development. These guides explain design intent; they are not a released API or installation reference. Read the release policy →
Current documentation track: concepts
Section titled “Current documentation track: concepts”All Runtime material on this site is conceptual. Early milestones are under development, and no public distribution, stable API, support window, or enterprise certification is claimed.
The lifecycle below is a proposed publication discipline, not a contractual support policy.
Require evidence before publication
Section titled “Require evidence before publication”| Review area | Minimum publication evidence |
|---|---|
| Artifact | Approved version, trusted distribution, checksum and authenticity procedure |
| Behavior | Reproducible tests for documented contracts and examples |
| Environment | Verified Java, OS, and dependency compatibility |
| Operations | Startup, shutdown, configuration, failure handling, and rollback |
| Legal and security | Correct holder, licenses, notices, dependency review, known limitations |
| Documentation | Matching release reference, changelog, and migration notes |
Introduce versioned docs deliberately
Section titled “Introduce versioned docs deliberately”Keep conceptual content stable under /docs/. Before the first public Runtime release, choose and test a versioned path strategy such as /docs/runtime/<version>/. This is a future routing plan, not an existing link.
Import only approved public contracts and examples. Never copy private Runtime source into the public web repository without a separate publication review.
Verify examples in the release pipeline
Section titled “Verify examples in the release pipeline”Build samples from a clean environment against the exact artifact. Capture results, review claims, and publish the docs snapshot with the same release identifier. Failing or unverified examples should block the release reference.
State lifecycle promises explicitly
Section titled “State lifecycle promises explicitly”Before any support commitment is made, define maintenance scope, security handling, compatibility, and end-of-support communication. No long-term support duration is currently promised.
Check downloads and changelog status for actual availability.