Skip to content

Implement Bag-of-Actions everywhere relevant across the estate #28

Description

@hyperpolymath

Outcome

Implement Bag-of-Actions everywhere relevant across the Hyperpolymath and Metadatastician estates.

Scope

  • Inventory repositories currently dependent on GitHub-hosted Actions and classify checks by capability, trust, duration, secrets, and mutability.
  • Define an adoption template that references Bag without vendoring or duplicating it.
  • Roll out in waves: advisory local sweeps, signed commit statuses, then required contexts after evidence review.
  • Prefer existing just/Guix command surfaces and proven-tests-and-benches contracts.
  • Preserve repository-specific language, proof, licence, and governance requirements.
  • Track avoided hosted minutes/cost and explicitly list checks that must remain GitHub-native.

Acceptance criteria

  • A machine-readable inventory identifies relevant repositories, owners, manifests, capabilities, and rollout state.
  • Each adopted repository has a tested manifest and rollback plan.
  • No repository is switched to required Bag statuses before signed end-to-end evidence is demonstrated.
  • Estate documentation names Bag as an integration, not a copied workflow implementation.

Metadata

Metadata

Assignees

No one assigned

    Labels

    adoptionReference consumers and estate-wide rolloutpriority:p2Scale, polish, or later adoption workroadmapPlanned product-roadmap work

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions