Repository navigation
Architecture Packet
sergio velderrain edited this page Nov 12, 2026
·
24 revisions
Satisfies the repo-standards-review ARCH gate with
System-Requirements-Specification and
Software-Requirements-Specification
(VITechnologies/projectbuddy#10): architecture description with all 4
required views (Context, Container, Component, Deployment), named
stakeholders and concerns, and retained decision rationale.
- System:
VITechnologies/projectbuddy - Purpose: a public, project-agnostic engine for provisioning self-hosted build/test infrastructure and running native SBOM reporting pipelines for downstream consumer repositories.
- Scope: VM provisioning (Windows+LabVIEW, Ubuntu+LabVIEW), native and
containerized SBOM build/report pipelines, project registration
(
add-project.yml), and (new) human-escalation and repo-onboarding tooling.
| Stakeholder | Concern | Viewpoint |
|---|---|---|
| Product (operator/fork owner) | The engine must never assume one fork's private identity/infrastructure | Consumption model, Context View |
| Engineering (agent/contributor) | Changes must be traceable to a requirement and reviewable before merge | Software-Requirements-Specification, Component View |
| Operations (consumer repo maintainer) | Upgrades must be deliberate, never silent/floating | Context View, Deployment View |
| Security | Tokens/secrets must be least-privilege and never leak across repos | Component View (Enable-RepoIssueTracking.ps1, standards-compliance-recheck.yml's persist-credentials: false fix) |