Java 17/21/25, Python 3.11–3.14 and Node.js 22/24/26 have public signed stable images on both architectures. See the stable release index and support boundaries.
The v1.0 acceptance report records native qualification, signed language and foundation releases, consumer examples, size and security evidence, and protected updates. The v1.1 debugging decision documents the isolated operator workflow and defers a project-published debug image.
The sequence is scope-based, not a calendar promise. Finish each milestone's exit criteria before promotion. Estimate delivery dates after the prototype establishes real build and maintenance costs.
| Milestone | Deliverables | Exit criteria |
|---|---|---|
| M0 — Repository foundation | Issue forms, labels, milestones, backlog, contribution policy, and PR gates | Completed: configuration committed, workflow documented, and main protected |
| v0.1.0 — AL2023 runtime prototype | Shared runtime contract, Java/Python/Node.js contract, pinned inputs, amd64 static/base foundations, runtime probes | Reviewed file inventory and passing foundation probes; all three language contracts accepted |
| v0.2.0 — Multi-architecture CI | arm64 foundation parity, PR CI, reproducibility report, measured size budgets | Static/base pass on both architectures; extensible CI matrix and foundation baselines exist |
| v0.3.0 — Java, Python, and Node.js runtimes | Separate java/python/nodejs images, version/ABI packaging contracts, language CI and native-dependency probes | All three languages pass on amd64/arm64 with runtime-specific verification and reviewed size/evidence baselines |
| v1.0.0 — Verifiable stable release | SBOM/provenance/licenses, vulnerability gates, signed GHCR artifacts, maintenance policy, and examples for all five variants | Every committed language and foundation variant has verified artifacts, native execution evidence, rollback, and a published support contract |
| v1.1.0 — Runtime extensions | Isolated debugging and operational improvements for the supported runtime matrix | Accepted scope, verification, and maintenance ownership; production images remain shell-free |
The table records the original dependency plan; live issue states and delivery reports show completion. #23 implemented full native foundation and language qualification, including size checks and measured reproducibility.
| Runtime | Required implementation | Key acceptance evidence |
|---|---|---|
| Java | Amazon Corretto headless runtime with explicit paths and a separate application builder | Executable JAR, JVM native dependencies, JAVA_HOME, truststore/TLS, DNS, signals, and hardened non-root execution |
| Python | Versioned AL2023 interpreter/stdlib and documented builder-installed dependency path | Stdlib/import paths, SSL, version-matched native extension, cache/bytecode behavior, and hardened non-root execution |
| Node.js | Versioned AL2023 runtime with production dependencies installed by a matching builder | ESM/CommonJS, HTTP/TLS/DNS, native addon ABI/N-API, CA/Intl behavior, signals, and hardened non-root execution |
The accepted matrix supports Java 17/21/25, Python 3.11–3.14 and Node.js 22/24/26. RFC #51 adds independently versioned official upstream releases for Python and Node.js.
- All five variants (
static,base,java,python, andnodejs) use verified, locked AL2023 inputs and explicit per-variant file inventories. - Both
linux/amd64andlinux/arm64pass the common and language-specific contract suites, including required native libraries/extensions. Record native runtime evidence on both architectures. - Production images use numeric non-root identity and contain no shell, package manager, compiler, RPM database, development toolchain, or build cache. Application runtimes themselves remain available by design.
- Java/Python/Node.js dependencies are prepared in compatible builders. Do not require Maven/Gradle/javac, pip/ensurepip, npm/npx/corepack, or a shell at production startup.
- Each variant/version/architecture has measured size budgets and separate runtime-file/OCI-digest reproducibility results.
- SBOMs, provenance, scans, licenses, and source delivery cover actual shipped runtime files and native components. Every committed language is included in the release gates and signature/evidence verification.
- Published examples, runtime-version support windows, refresh procedures, and rollback match the released artifact matrix.
The standalone C++/cc image is removed. Issue #14 is closed as not planned following the owner-directed decision in #19. This does not ban native C++ libraries that are required dependencies of supported Java/Python/Node.js runtimes; those libraries must be audited and covered by the same evidence and update gates.
Debug images, FIPS claims, additional language versions, additional architectures, and additional registries require their own accepted scope and maintenance capacity. Java, Python, and Node.js are required deliverables rather than optional language explorations.
Current language versions, library/data boundaries, scanner behavior and preview tags are recorded in the delivered contracts. Additional runtime capabilities and stable-release policy changes require their own issue/RFC.
GitHub Issues and Milestones are the live execution record. .github/planning/backlog.json and issue-map.json capture versioned planning snapshots and issue identities; they do not automatically overwrite live issue bodies or states. retired.json retains removed work and its decision history. Update this roadmap through an issue-linked PR when scope changes. Labels and milestone descriptions are maintained by the configuration sync script.
The v1.0 milestone is the target for automated maintenance proposals for the stable lines. Change the proposal target to an open maintenance milestone before closing it.