ADR-013: GitHub Container Registry (GHCR) as Container Registry
Use GHCR for all Docker image storage and distribution
Use GHCR for all Docker image storage and distribution
Accept docker-group deploy-user risk (audit #392) until we migrate to a managed container platform; remove the brittle sudoers-allowlist mitigation introduced in sv0-platform PR #401.
Controls GitHub Actions minute consumption by cutting per-run cost, not PR count. The org's 50k included-minute pool is effectively a single-repo pool that follows active development; in May 2026 sv0-platform's ci.yml alone was ~80% of it (~36k measured minutes), dominated by a tail of multi-arch (amd64+arm64-via-QEMU) image builds that HUNG for hours on PR pushes (67 runs over 300 min, worst 18h). Decision: amd64-only image builds on PRs (multi-arch stays on main/release tags), cancel superseded PR runs, path-gate the non-required image build, and cap heavy jobs with timeout-minutes. Keeps the PR-per-change workflow intact. Shipped in sv0-platform#1301 (issue #1300); timeout follow-up pending.
Comprehensive CI/CD strategy for sv0-platform deployment and sv0-connectors scan pipelines, including secrets management evaluation (GitHub Secrets, SOPS+age, Tailscale, Vault, Doppler, self-hosted...
Records the git tag 'pre-w1.1-architecture' across all three repos, marking the stable baseline before W1.1 implementation begins
SecurityV0 infrastructure strategy: AWS credits, connector automation, AWS Organization account structure, budget protection, demo lab environments, and phased migration plan from Hetzner.