Skip to content

Hive acceptance infrastructure: automate Utah boot and runtime evidence before landing system changes #1614

Closed

Description

@hanthor

Goal

Remove recurring human execution of reproducible acceptance checks while retaining genuine hardware-only exceptions.

Observed cases

Solution / owner prerequisites

Provide Hive a bounded VM/hardware-runner interface, approved images/test inputs and artifact access so it can request isolated boot/install/upgrade/rollback and guest/desktop checks, consume signed exact-image evidence and retry only appropriate infrastructure failures. Scope credential and network access; never mark missing observations successful.

Acceptance

  • Record which checks are automatable in CI/VMs and the precise physical-only exception for each remaining issue.
  • Hive can trigger and read real exact-candidate VM evidence without an operator dispatching every run.
  • Failed/missing/old-image evidence blocks admission and is linked to an owning repair task.
  • Demonstrate boot/update/rollback and at least one desktop/guest capability path.
  • Physical-display acceptance remains explicitly pending until observed; do not close Graphical Plymouth LUKS prompt not confirmed on running hardware utah#461 from SSH plumbing alone.

A completely Hive-maintained project should mean automated acquisition of required evidence, not removing acceptance criteria.

Activity

  1. added
    needs-kindA maintainer must classify this issue; the intake source did not establish its kind.
    on Nov 2, 2026
  2. added
    triage/acceptedScope accepted; ready for work. Use `/triage accepted`.
    on Nov 2, 2026
  3. removed
    needs-kindA maintainer must classify this issue; the intake source did not establish its kind.
    on Nov 2, 2026
  4. kylerankin commented on Nov 2, 2026

    @kylerankin
    Contributor

    Summary: A pull request now records, in one reference doc, which promotion-acceptance checks can run in an automated virtual-machine test and which can only be answered by a real device and a person, so the factory can stop asking a human to run these proof checks by hand without dropping the checks that only real hardware can answer.

    What I need from you: Approve the pull request.


    Open PR: #1616 (feat/acceptance-evidence, targeting main).

    It adds docs/skills/acceptance-evidence.md and registers it in docs/SKILL.md, satisfying the "record which checks are automatable in CI/VMs and the precise physical-only exception for each remaining issue" acceptance item of this issue.

    What stays open (owner-provided infrastructure that lives outside this shared OCI layer, and that the factory secrets policy forbids agents from provisioning):

    • Triggering and reading real exact-candidate VM evidence without a per-run operator dispatch.
    • Blocking admission on failed/missing/old-image evidence and linking it to an owning repair task.
    • Demonstrating boot/update/rollback and at least one desktop/guest capability path.

    Physical screen unlock and desktop rendering (issues #461, #992, #997) stay explicitly pending: they need a real display and a person and cannot be proven from installed packages, static metadata, or SSH access.

    — hive: backend=pi model=lemonade/ornith-1.5-35b-a3b-gguf-q6_k


    🐝 Hive Agent: contributor | SHA: 41cacde

  5. hanthor commented on Nov 2, 2026

    @hanthor
    MemberAuthor

    Evidence-infrastructure handoff — #1616 implements classification only

    Changed PR #1616's automatic closing reference to partial Refs. Also corrected its PR-body physical-check references to projectbluefin/utah#461, projectbluefin/utah#992 and projectbluefin/utah#997; these are not common issues. Check the new skill for the same cross-repository routing mistake before landing.

    The remaining deliverable is operational: an authorized bounded runner interface that Hive can trigger and read without a human dispatch per candidate, exact-image evidence bound to the candidate, and admission that rejects missing/stale/failed evidence. Link the deployed runner/consumer, real artifacts and an exercised boot → update → rollback plus desktop/guest capability path. Do not substitute a policy document or installed-package inventory for that demonstration.

    Preserve genuine physical-display/unlock exceptions. Do not invent new secrets or authorize wider credential/network access from this handoff; name any required owner-only infrastructure decision precisely and complete reachable automation separately.

    Keep the original issue open until these acceptance criteria—not only the classification checkbox—are met.

  6. hivecommons-hive commented on Nov 2, 2026

    @hivecommons-hive
    Contributor

    PR #1616 covers this issue: #1616

    The PR body says this is partial/non-closing work (Refs/Part of or leave-open wording), so Hive will not add a closing keyword. GitHub will not show its issue-list PR icon without a closing keyword; the stage comment is the link.

  7. 11 remaining items

  8. removed
    stage/010-actionableTriaged; eligible for the hive to pick up
    blockedWaiting on something outside this repository. Use `/label blocked` or `/remove-label blocked`.
    on Nov 7, 2026
  9. hivecommons-hive commented on Nov 8, 2026

    @hivecommons-hive
    Contributor

    Hive status — updated in place; edits do not notify. Full history is in the Activity Monitor.

    Unblocked: the blocked label was applied by the hive without a blocked-on marker, so nothing could lift it. This issue is actionable again.

  10. kylerankin commented on Nov 8, 2026

    @kylerankin
    Contributor

    Reachable automation landed (PR #1652)

    Re-landed the admission gate from the earlier closed #1622, now wired into
    common's test target (Justfile) and documented in
    docs/skills/acceptance-evidence.md under "Checking a record".

    Decision taken by hive: the #1622 reviewer asked whether a gate with no caller
    should land now or wait for a wired consumer. Per the owner rule (scope is
    mine to decide), this is the simplest additive, backward-compatible option, so
    it lands now; the consumer/runner is the next step.


    🐝 Hive Agent: contributor | SHA: e3d4cbb

  11. added
    stage/010-actionableTriaged; eligible for the hive to pick up
    stage/stalledIn its current stage longer than expected
    and removed on Nov 8, 2026
  12. Danathar commented on Nov 17, 2026

    @Danathar
    Contributor

    Closing. What this issue asked for now exists, mostly in Utah, and the one remaining automatable gap is tracked in Utah, where the code lives. Summary as of 11-17, @hanthor:

    Acceptance items

    1. Which checks VMs can run vs. which need hardware: done in feat: document acceptance-evidence classification for CI/VMs vs physical-only #1616 (docs/skills/acceptance-evidence.md).
    2. Exact-candidate VM evidence with no operator dispatch: done in Utah. build.yml starts post-testing-e2e.yml for every testing build. That run verifies the provenance of each exact digest, does a LUKS install and boot of all four flavors, builds the production ISO, and runs the GNOME tests.
    3. Missing, failed or old evidence blocks admission: done in Utah. promote-to-testing needs the LUKS and ISO jobs, and scripts/promotion-ratchet.py writes the e2e/post-testing statuses the release gate reads. It never moves :testing backwards. Common's scripts/admit-evidence.sh (feat(acceptance): land admit-evidence admission gate (#1614) #1652) has no caller, because Utah gates this its own way.
    4. Boot, update, rollback and a desktop path: boot and the desktop are done. Update and rollback are not run in CI yet, although the harness exists (just lifecycle-test). Wiring it in, and gating promotion on it, is now ci: run the bootc upgrade/rollback lifecycle harness in post-testing E2E and gate promotion on it utah#1323.
    5. Physical-display acceptance: nothing more to do here. Graphical Plymouth LUKS prompt not confirmed on running hardware utah#461 is closed.

    If common's unused admit-evidence.sh should go, that's a separate cleanup.

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

    approved-directionhive/partially-addressedA merged PR addressed only part of this issue; remainder still actionablekind/featureA new capability.triage/acceptedScope accepted; ready for work. Use `/triage accepted`.

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions