Proposed transitions
Changes
Frozen pull request 8
#8 · Endless-Technologies/onsite-hero-app
Declared by the steward; Atlas has not read this PR. Repository attribution unverified.
Chain
Consequence observed
- — The connected repository is onsite-hero-app while the frozen pull requests were discussed as Atlas. Repository identity is unresolved.
Frozen pull request 9
#9 · Endless-Technologies/onsite-hero-app
Declared by the steward; Atlas has not read this PR.
Chain
Consequence observed
- — The connected repository is onsite-hero-app while the frozen pull requests were discussed as Atlas. Repository identity is unresolved.
Doctrine compilation and release gate
Release 1 · Endless-Technologies/Atlas
Chain
Authorising decision
Should Atlas absorb HomeFlow?
Deployment
Consequence observed
- — Test count rose to 2067 with no runtime regression; correctness confidence is high but coverage of the gateway path remains untested end to end.
Homepage restated around the holonarchy
holonarchy homepage · Endless-Technologies/Atlas
Chain
Deployment
Software Hub domain surface
software-hub · Endless-Technologies/Atlas
Chain
Authorising decision
Should the Software Hub introduce a new ontology or project the existing one?
Consequence observed
- — Atlas has large declared capacity but narrow practical freedom: most requests must be refused, deferred or reshaped to fit the scope boundary.
Threshold guardians
Boundaries a change can cross
Guarded by: Repository write permission
Every write is committed and attributable.
Guarded by: Pull request review
Frozen PRs sit exactly here — proposed transition, unauthorised.
Guarded by: Release gate (build + tests)
Preview deploys are reversible; production publish is not yet crossed.
Guarded by: Steward approval of a plan
Software Hub was proposed, approved, then built.
Guarded by: Atlas Gateway capability grant
No token issued, so nothing has crossed.
Guarded by: Doctrine compilation
Release 1 crossed this boundary.