You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/superpowers/specs/2026-07-10-portable-ghar-platform-design.md
+12Lines changed: 12 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -26,6 +26,17 @@ The first implementation will:
26
26
27
27
This project is not an official GitHub project. Its scale-set integration depends on a public-preview upstream interface and must be presented as experimental until the compatibility and migration gates in this document pass.
28
28
29
+
### 1.1 Standalone dependency boundary
30
+
31
+
Portable GHAR source, builds, tests, release artifacts, deployment tools, and
32
+
runtime depend only on this repository and its declared public dependencies.
33
+
No consumer repository, collaboration broker, reviewer plugin, or developer
34
+
workspace is a product dependency. Independent review tooling is replaceable
35
+
development infrastructure, and deployment-time consumer workflows remain
36
+
external integrations chosen from authenticated live inventory. Failure or
37
+
absence of either cannot create a new Portable GHAR build, test, release, or
38
+
runtime prerequisite.
39
+
29
40
## 2. Goals
30
41
31
42
1. Replace fixed, always-online runner slots with on-demand ephemeral runners.
@@ -40,6 +51,7 @@ This project is not an official GitHub project. Its scale-set integration depend
40
51
10. Produce reproducible binaries and images with checksums, SBOMs, provenance, and third-party license notices.
41
52
11. Survive GitHub-forced runner version bumps without manual intervention or loss of the GitHub-hosted execution path.
42
53
12. Reclaim every job-scoped cgroup, tmpfs, process, namespace, and workspace by whole-container destruction, with bounded steady-state host memory and no persistent runner work area.
54
+
13. Keep every mandatory source and operational contract consumer-neutral so the platform can be built, tested, deployed, and operated without any unrelated repository or development tool.
0 commit comments