Usable state-space
Capacity is not freedom. An object can be large and still have very little practically usable room once constraints consume that capacity. Nothing here is scored numerically yet — only observed.
Atlas
workableFull constitutional substrate with ratified C16–C19 doctrine.
Consumed by: Scope boundary against product-layer work; Release-1 freeze
Endless-Technologies/Atlas
workableLarge module surface: 60+ modules, 80+ routes, full registry spine.
Consumed by: Deferred-seed boundary (Saint Nick, Diamond, Skill Garden, extra hubs); Release-gate test floor; Atlas↔HomeFlow contract stability
Registry
Constraints
No sixth spine layer
architecturalusefulNew work extends Identity, Events, Relationships, Evidence or Stewardship. It never becomes a sixth layer.
Constrains
Atlas · Software Hub
Rationale
Atlas is orchestration only
policyusefulProduct-layer features belong to HomeFlow; Atlas exposes contracts instead.
Constrains
Atlas · HomeFlow
Rationale
No PII across the boundary
securityusefulCross-boundary data carries opaque pseudonymous references only.
Constrains
Atlas Gateway
Rationale
Never fabricate to complete a view
policyusefulUnknown values stay unknown and remain inspectable.
Constrains
Software Hub · Recursive Auditability
Rationale
Release 1 doctrine freeze
temporalunknown-purposeDoctrine compiled at Release 1 may not be silently amended.
Constrains
Atlas
Rationale
Deferred seeds stay deferred
authorityoverheadSaint Nick, Diamond, Skill Garden and additional hubs are not authorised for implementation.
Constrains
Atlas
Rationale
Every public table needs RLS plus GRANTs
securityusefulMigrations that create tables must grant explicitly in the same migration.
Constrains
Endless-Technologies/Atlas
Rationale
Worker-compatible dependencies only
technicalusefulServer code runs on workerd; Node-only packages are rejected.
Constrains
Endless-Technologies/Atlas
Rationale
Gateway token absent
dependencyobsoleteNo issued token, so contract round-trips cannot be exercised end to end.
Constrains
Atlas Gateway · HomeFlow
Rationale