Skip to content

Context View

sergio velderrain edited this page Nov 9, 2026 · 1 revision

Context View

  • External actors: the fork owner (operator) dispatching workflows and reviewing escalations; contributors opening PRs against feature/* branches (per ADR-0001's documented GitFlow model; in practice, recent work has also used more specific topic-branch names like round6-semantic-audit-fixes for the same feature/*-equivalent role).
  • Upstream systems: svelderrainruiz/repo-standards-review (the authoritative compliance standard this repo is assessed against); GitHub itself (Actions, Issues, Releases, Wiki).
  • Downstream systems: consumer repositories (e.g. VITechnologies/SandboxSBOMReporting) that pin this engine's reusable workflows/scripts -- a release commit SHA for the one genuinely workflow_call-consumable workflow (toolchain-smoke-test.yml) and directly-invoked scripts, or a vendored copy for workflow_dispatch-only workflows (see README's Consumption model); not always a tagged release specifically -- e.g. SandboxSBOMReporting's separate PROJECTBUDDY_VM_REF pins a descriptively-labeled, untagged commit SHA; self-hosted runner VMs (Windows+LabVIEW, Ubuntu+LabVIEW) this engine provisions; the NI LabVIEW/VIPM toolchain those VMs run.

Clone this wiki locally