Skip to content

Bound composable Dev preview to one-use authority #5416

Open

Description

@auser

Scope

Bound draft PR #5326 to a separately approved, Dev-only preview of one-command run --compose and hidden named machine create --pack / start. This ticket does not complete the production artifact, immutable warm claim, or launch-speed requirements. Governing program #5415 and architecture #5413; preserve #5341 and explicit bundle enrollment from merged #5301.

Acceptance

  • Obtain owner approval for the revised preview scope and record remaining warm/speed acceptance in separately owned issues, without deleting or checking off unfinished criteria on feat(pack): stage portable composition from current main #5326.
  • A composed archive and cache remain data; each cold or repeat invocation re-verifies inputs and mints a one-use, invocation-private Dev proof bound to exact bytes, signer, user and expiry. Cached bytes do not reuse authorization.
  • Refuse the proof at installed/reusable bundles, export, production/fleet origin, rematerialization, warm claim, stale/foreign/replayed proofs and changed archive or selected base. Preserve the normal signed-plan and backend admission path.
  • Rebase/merge current main into feat(pack): stage portable composition from current main #5326 only with its branch owners, resolve conflicts and measured footprint, run current-head CI and reviewed CLI guest-output/refusal checks. Report the existing x86_64, arm64 Linux and macOS evidence as Dev-only; no production or speed claim.

Context and validation

The current PR is draft and conflicted; latest head has no check runs, while older heads have live Dev guest output. Read its body, the composable-pack build contract, ADR-001, ADR-037, and draft ADR-059 before changing a branch. Focus tests in crates/mvm-cli/src/commands/vm/exec.rs, crates/mvm-hostd/src/plan_admission/composition.rs, and tests/cli.rs. Run cargo test -p mvm-cli, cargo clippy --workspace -- -D warnings, cargo check --workspace, cargo run -p xtask -- check-all, and the hermetic BDD lane; name any unrun live backend witness. The branch is owned by its current contributors; this issue does not authorize an unrelated agent to push it.

Depends on: owner preview-scope decision. Independent of: the production schema and warm API tickets. Plan the code change from #5326's actual head, not from a stale local checkout.

Activity

  1. auser commented on Nov 13, 2026

    @auser
    CollaboratorAuthor

    Scope review packet — Dev preview, not production

    Draft #5326 currently has named and transient Dev guest-output witnesses, but its latest head has no reported checks, conflicts with main, and still describes immutable warm custody plus cold <300 ms / warm <50 ms as blocking acceptance. #5341 already chose a one-command transient, one-use Dev proof that does not enroll the local signer. Neither PR-only signing nor an authenticated cache-hit repeat is production authority.

    Recommendation for owner approval

    If the owner wants the development workflow independently reviewable now, split or explicitly narrow #5326 to its already bounded Dev capability, and keep the unused warm primitive inert/disabled until #5419/#5422/#5427 are implemented and witnessed. Document the slower observed starts honestly; make no warm, speed, fleet or official publisher claim. The original product performance requirements remain in #5415/#5418/#5429—do not mark their checkboxes complete to make this PR mergeable. If owner approval is not given, leave #5326 draft under its current acceptance terms.

    Preview acceptance matrix

    • Positive: one command run --compose and hidden named create/start/stop/restart on authenticated Dev inputs, freshly admitted at each boot; verify guest output and audit/receipt on the exact head for the backend claimed.
    • Negative: direct install/run of reusable local schema-8 bundle without explicit enrollment, export, prod/fleet origin, later claim/rematerialization, replay/expiry, foreign host/user/signature, changed archive/base/policy and stale revocations. A cache hit only reuses verified bytes and mints a new one-use proof.
    • Process: current branch owners coordinate a non-destructive update against main, resolve conflicts and measured footprint, obtain exact-head CI and a separate review. No other contributor should force-push this shared draft branch or publish PR-only release assets.

    Owner call needed: approve this bounded preview scope as a separate merge candidate, or retain #5326's full warm/speed blockers. This comment does not grant permission to merge or change its branch.

  2. auser commented on Nov 13, 2026

    @auser
    CollaboratorAuthor

    Owner approved the recommended Dev-only preview scope direction in #5413. This does not edit, approve merging, or close the hard warm/speed criteria on draft PR #5326. Its current branch owners must make the scoped change and exact-head validation reviewable; all unchecked acceptance here remains open until evidenced.

  3. auser commented on Nov 15, 2026

    @auser
    CollaboratorAuthor

    Design-relevance note (2026-11-15 audit for #5415): this issue's vehicle #5326 was closed unmerged per the #5415 triage; the live Dev composition capability is #5263's schema-8 local_composition + --compose (transient-only, signed-input admission per invocation). Checkboxes referencing "#5326's head / rebase #5326" are moot as written. Remaining question for the owner: does #5263's Dev-local composition satisfy the preview intent, or is a fresh narrowed PR wanted? Tracked in the #5415 epic map.

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