Skip to content

Epic: production-ready composable workloads #5415

Open

Description

@auser

Goal

Deliver a production-ready composable workload: one authored application plus authenticated ordered runtime inputs and a selected signed base becomes a self-contained, independently signed .mvmpkg; only authenticated mvmd may initiate its production launch. Verification, admission, immutable warm custody and measured readiness must be evidenced on the first supported backend, x86_64 Linux/KVM/Firecracker.

Architecture and authority

Architecture direction for this program (owner-approved on 2026-11-13; durable format/ADR review and implementation remain open). Follow accepted ADR-001, ADR-037 and ADR-055 and the current composable-pack build contract. Do not treat closed draft checkpoint #5326, landed preview ADR-059 or #5407 publication guards, a local signer, a PR-only artifact, or a cached bundle as published or warm authority. mvm-packs component formats remain unpublishable until producer and consumer gates are reviewed together.

Acceptance tracks

  • Dev-only candidate: owner explicitly approves a narrow preview scope for the preserved closed-draft checkpoint #5326; its one-use transient proof and hidden named-machine workflow cannot acquire install, export, production, fleet or warm authority. Refresh conflicts and exact-head CI; do not check off the original speed/warm requirements by editing them away.
  • Production artifact: ratify the versioned schema/policy contract; freeze a source and exact signed input lock; independently verify and protected-sign a self-contained schema-9 bundle. Publisher enrollment, current revocations, selected command, host ceilings, and offline verification refuse mismatches. Exact source/signer/descriptor/rights approval and output readback are separate publication gates.
  • Owned warm custody: review the typed ADR-059 owner/descriptor API, then issue generation-bound immutable read leases with bounded RAM/FD/parent budget and VMM-lifetime custody; fresh signed-plan admission is required for every child. Unsupported providers, stale handles, crash/restart, tamper and exhaustion fail closed before a warm claim.
  • Production evidence: on x86_64 Linux/KVM/Firecracker, boot the exact independently signed candidate through authenticated mvmd origin and the normal backend path; test guest output, refusals, cleanup and current revocations. Measure acquisition/publication apart from invocation-to-ready cold <300 ms and warm <50 ms including admission, with the existing minimum sample floor. No ARM/HVF production or warm claim until separately witnessed. Final review, CI and merge-queue checks must pass on exact bytes.

Non-goals

No local mvmctl production launch, automatic guest installation, second policy/network path, new guest NIC/SSH, relabelling legacy published versions, unsupported-platform fallback or publication of an unfinished application/runtime component. This issue does not authorize release signing or merging a PR.

Delivery method

Small reviewable tickets link back to this issue and inherit #5413; plan dependent tickets just-in-time once their prerequisite implementation and owner approvals exist. Work in separate feature worktrees, leave closed draft checkpoint #5326's branch with its current owners, and keep unchecked criteria open until live evidence is linked. The first wave can run Dev boundary review, contract ratification, and warm API spike in parallel; production export, mvmd admission, warm claim and release evidence depend on those results.

Ticket breakdown and execution waves

Every ticket links the architecture decision #5413 and carries its own acceptance and validation. These are planned scopes, not evidence of completion. Plan each dependent ticket against the implemented predecessor, not just this list.

Wave Independently reviewable tickets Dependency
0 #5416 Dev proof boundary, #5417 schema/policy decision, #5418 latency clock, #5419 owner/lease API Owner reviews; parallel work, no branch sharing.
1 #5423 frozen lock, #5421 signed base/runtime, #5420 component consumer, #5424 registry producer #5417; producer and consumer can develop in parallel against one reviewed contract, but cannot publish separately.
1 #5422 Linux immutable provider #5419; parallel with build-input tickets.
2 #5425 protected export #5423 + #5421 + #5420 + #5424.
3 #5426 installed consumer admission #5425 + #5420.
4 #5428 authenticated mvmd origin, #5427 warm claim integration Both need #5426; warm also needs #5422. They can run in parallel after those predecessors.
5 #5429 live security/latency witness #5418 + #5428 + #5427 + exact candidate.
6 #5430 exact release authorization/readback #5429 + #5424 + #5421 and separate exact owner authorization.

Release rule: A verified candidate is not an admitted or ready production workload; neither CI nor a signature alone approves release. Do not mark this epic complete until every applicable acceptance checkbox has an exact source revision, signed artifact identity and witness, and a separate owner approves the actual publication and merge.

Activity

  1. auser commented on Nov 13, 2026

    @auser
    CollaboratorAuthor

    PR triage handoff: close superseded/staging drafts #5284, #5323 and #5326 without merging or deleting their branches. #5284 is superseded by #5326 and still has an unwired v3 graph and failing footprint gate. #5323 has no official Python public key, final health boot, clean install or protected signer/feed witness. #5326 has Dev-only cold/repeat guest evidence, but not immutable VMM-lifetime warm custody, independent protected production signing, or cold <300 ms / warm <50 ms including admission. Preserve these source/evidence checkpoints as historical links; pursue focused #5416–#5430 tickets against current main, and leave all applicable acceptance boxes open. Closing the drafts is PR-inbox cleanup, not a reversal of any security or latency gate.

  2. auser commented on Nov 14, 2026

    @auser
    CollaboratorAuthor

    Coordination from the Python two-arch #4839 lane: I learned after pushing that #5323 had been intentionally closed on Nov 13 and handed off here. Before seeing that handoff, I had merged current origin/main into its retained feature branch (not into main) at 5efe4af9c15c97c9b60ce3e54569897862f8b605, resolving the exporter move by retaining the main-side mvm-client implementation plus the v8 production_composition: None field. Local MVM_EMBED=0 cargo check --locked -p mvm-cli --lib, cargo fmt --all -- --check, actionlint and the targeted schema-8 member test passed. The closed #5323 PR remains closed; this merge is not reviewed, landed, published or an exact-file boot witness. I will not reopen or push more changes to that historical branch. The prior OIDC workflow runs stayed queued with zero jobs because the PR had closed. #5417 owns format/policy review and #5425/#5426 the future producer/recipient gates. The original user goal requests x86_64 and aarch64; #5415 currently accepts x86_64 first and explicitly leaves ARM/HVF unclaimed. Please confirm whether the two-architecture Python release remains a subsequent gate under #4839 (recommended), while #5415 delivers x86_64 first; do not silently treat a single-arch program as completing #4839.

  3. auser commented on Nov 15, 2026

    @auser
    CollaboratorAuthor

    Epic map against main @ 75c9e44 (2026-11-15 audit)

    A full reconciliation of every slice against landed code, so the lanes don't double-count. Verdicts: LANDED-as-decision / PARTIAL / OPEN / BLOCKED-ON-#4764 / SUPERSEDED-in-part.

    Where it stands: Wave-0 decisions approved 11-13; since then the lanes landed precursors — #5263 (Dev schema-8 composition + --compose, transient-only), #5407+#5441 (publication lifecycle guards + BootInputBudget/BootInputReadLease staging with strong hermetic tests), #5516 (schema-9 reservation, docs/contract), #5436 (clock measurement boundary in contract + performance.md), and ADR-112's diagnosis (7× ~640 ms repeat runtime-archive verification = 4.5 s of 5.6 s per launch — the hidden blocker under every <300 ms claim until once-per-launch verify lands). No acceptance checkbox in #5415–#5430 can be fully checked yet — conservative reading, details per slice below.

    Per-slice: #5413 decisions PARTIAL (egress-merge tested rule + clock reconciliation open; ADR-112 now load-bearing). #5416 SUPERSEDED-in-part — its vehicle #5326 was closed unmerged; the live capability is #5263, and any checkbox referencing "#5326's head" is moot as written. #5417 PARTIAL — reservation landed, wire member is draft #5527 only (reader max stays 8, fail-closed), no shared policy vectors (tests/policy-vectors/ absent). #5418 PARTIAL — docs half landed; the hermetic reporter/refusal gate is not (#5517 is density, not this). #5419 PARTIAL, closest to checkable — code+tests exist, but ADR-059 says the claim "exposes no descriptor and is not a complete boot closure or a VMM-lifetime lease," and the owner API review is still pending; hold boxes 1–3 for one citation. #5420/#5421/#5422/#5423 OPEN with precursors (#5263 staging, #5439/#5485 Yocto cousins, #5441 sealed-memfd lease consumed by nothing yet, freeze-time recheck without the versioned v2 lock). #5424 OPEN (mvm-packs#165 in review). #5425 OPEN (all five predecessors). #5426 OPEN — baseline strong (#5263 composition admission, #5485 selected-backend), schema-9 admission is the #5527/#5500 fail-closed reservation; #5411's unanswered questions are a prerequisite for its "one signed-plan gate" claim. #5427 OPEN, needs #5419+#5422+#5426; intersects the deferred fc-lifecycle-owner contract (#5524). #5428 OPEN (control plane private). #5429 BLOCKED. #5430 BLOCKED-ON-#4764 — rc.1–rc.4 tags exist but the release lane is red; do not treat rc.4 as the release witness.

    Remaining-work ranking by unblock leverage: (1) finish #5417 — merge #5527/#5500 + mvm-packs#165 + policy vectors; unblocks the whole Wave-1 quartet and everything downstream (critical path); (2) #5419 owner/API review + VMM-lifetime lease → unblocks the warm branch; (3) ADR-112 review → code (no <300 ms claim is plausible until once-per-launch verify); (4) re-plan #5416 against #5263 (owner decision: does Dev-local composition satisfy the preview intent?); (5) #4764 green + final v0.28.0; (6) answer #5411 (cheap; q4 is a #5426 prerequisite).

    Shape notes: the 11-14 one-app decision means component authentication applies to runtime layers only — acceptance text implying an app-component descriptor is superseded in that detail (#5527 carries "no fabricated original app-component signature"). #5527's fail-closed-first strategy means #5426 lands in two stages (member+refusals, then cap raise with exporter/recipient checks). Adjacent-but-not-counting: #5476/#5412 (CLI compose options), #5518, #5439/#5485, #5517 (density), #5509 (HVF warm de-risk only).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions