Software

The living form of the holonarchy: identity, events, relationships, evidence and stewardship as one navigable substrate. Deferred seeds accumulating faster than they are retired Gateway token absent, so contracts remain unexercised end to end atlas-entity/v1 atlas-event/v1 atlas-knowledge/v1 MCP server /api/public/v1/*

Product-layer construction and maintenance operations. Consumes Atlas services; separate repository, separate lifecycle. HomeFlow's own repository URL is still undeclared (repo.homeflow.url is typed unknown) Superseded claim: onsite-hero-app was once attributed to HomeFlow; corrected 2026-08-28 Atlas gateway client (Phase 2B)

Semantic reframing protocol and reference engine. Platform-neutral by design; incubated inside the Atlas repository but not dependent on it. Host coupling could re-enter through the reference console cropzero-protocol/v0.1 CropZero SDK Conformance suite

Offline-first tamper-evident field observation protocol: immutable originals, separately provenanced derivatives, device-signed chain. Device key custody is unresolved outside the browser origin witness-protocol/v0.1 Witness SDK Installable PWA console

Constitutional orchestration layer: identity, navigation, permissions, events, evidence, interoperability. GitHub Preview live; production not published 2067 tests passing at Release 1

Historical Atlas/HTC project slug for this repository. Retained as lineage; not a HomeFlow product repository. GitHub status-unknown cannot-locate

Residential construction and maintenance product surface. Calls Atlas through documented contracts; never merged into Atlas. not-yet-declared Which provider and URL hosts the HomeFlow repository? status-unknown cannot-locate

Universal Registry Framework: seven duties per registry.

Capability grants, tokens, proposal queue, PII refusal.

Spiral core, event and relationship timelines, typed absence.

Spatial projection of the substrate.

BigQuery read-only guard, budgets, health.

Doctrine evaluators and restraint charter.

This domain: software as a living system.

Governed security validation: attested targets, passive probes, recorded refusals.

Server functions, SSR entry, routing substrate. ^1

Rendering substrate. ^19

Identity, storage and registry persistence. Single identity provider for the whole substrate ^2

Design language implementation. ^4

Contract validation at every boundary. ^3

Release gate test floor. ^3

Street View hero imagery for property objects. Billing exposure if quota unbounded never-existed

Code hosting, review authority and public provenance surface. Organisation move invalidated prior app installs Frozen pull requests unresolved never-existed

not-yet-declared Which Google Cloud services does Atlas actually require at Release 1? Credentials not fully wired Budget ceiling enforcement untested in production not-yet-declared

Release 1 + holonarchy homepage wrangler.jsonc + project env

never-existed Atlas has not been published yet — should Release 1 be published? not-yet-declared

cannot-locate cannot-locate

Release 1 succeeded Steward

Holonarchy homepage succeeded Steward

Should the Software Hub introduce a new ontology or project the existing one? Software development introduces nouns (repository, pull request, deployment) that look primitive but may only be implementations of Identity, Event and Relationship. Projection of the existing substrate with discrepancies surfaced as questions Software Hub is read-mostly and declarative until a real source of software truth is connected.

Should Atlas absorb HomeFlow? Atlas is the orchestration layer; HomeFlow is the product layer. Keep separate with documented contracts Integration happens through atlas-entity/v1, atlas-event/v1 and atlas-knowledge/v1 only.

How should software data that Atlas cannot yet observe be represented? Live GitHub, registry and deployment data is not connected to this surface. Typed absence with explicit unknown reasons Every registry card can show Unknown as an inspectable state and generate a question.

New work extends Identity, Events, Relationships, Evidence or Stewardship. It never becomes a sixth layer. Prevents parallel systems and ontology drift. useful

Product-layer features belong to HomeFlow; Atlas exposes contracts instead. Keeps repositories separable and independently deployable. useful

Cross-boundary data carries opaque pseudonymous references only. Ratified with the Phase 2 knowledge slice. useful

Unknown values stay unknown and remain inspectable. Preserve the Path — absence must be typed. useful

Doctrine compiled at Release 1 may not be silently amended. Unclear how a post-release amendment is meant to be proposed. unknown-purpose

Saint Nick, Diamond, Skill Garden and additional hubs are not authorised for implementation. Correct as governance, but it now consumes a visible share of usable state-space. overhead

Migrations that create tables must grant explicitly in the same migration. Data API returns permission errors otherwise. useful

Server code runs on workerd; Node-only packages are rejected. Native addons and child_process are unavailable. useful

No issued token, so contract round-trips cannot be exercised end to end. Was a safety measure during Phase 2; now blocks verification more than it protects. obsolete

Release 1 compiled; C17 and C18 ratified. release.compiled

Atlas repository moved from personal account to Endless-Technologies. repository.transferred

Lovable GitHub App reinstalled at organisation level with all-repository access. integration.reinstalled

Homepage restated as the living form of the holonarchy. surface.rewritten

Software Hub declared as a new domain projection. domain.opened

Sandbox origin points at Lovable private transport, which is not evidence that GitHub sync is broken. Two different transports were conflated. git remote inspection + Lovable sync settings screenshot

The connected repository is onsite-hero-app while the frozen pull requests were discussed as Atlas. Repository identity is unresolved. sync settings screenshot

onsite-hero-app is the historical Lovable slug of THIS Atlas/HTC repository, not the Home Flow AI product repository. Home Flow AI (project bf557339-512f-4d4a-bd60-035578465ed6) remains its own software identity and owns its own domain truth. HomeFlow's repository URL stays typed unknown until a concrete URL is evidenced. this repository: Atlas route tree, supabase/migrations, src/modules/* — none of which model HomeFlow's domain

Test count rose to 2067 with no runtime regression; correctness confidence is high but coverage of the gateway path remains untested end to end. release gate run

Atlas has large declared capacity but narrow practical freedom: most requests must be refused, deferred or reshaped to fit the scope boundary. mem/features/deferred-atlas-scope.md

Interpretive continuity across Atlas domains; asks what is true here and what should be tested next. read:registries propose:questions propose:decisions Observe Ask questions Propose decisions Flag contradictions Merge changes Deploy Grant permissions Delete provenance

Holds doctrine, restraint and the release boundary. read:all ratify:doctrine authorise:threshold Ratify doctrine Authorise threshold crossings Freeze releases Bypass audit Rewrite history

Implements approved changes inside the Atlas repository. read:repo write:repo run:tests Edit files Run tests Run builds Apply approved migrations Publish without request Reactivate deferred seeds Modify HomeFlow

External contribution agent operating on pull requests. Unreviewed merge

Frozen pull request 8 #8 Declared by the steward; Atlas has not read this PR. Repository attribution unverified.

Frozen pull request 9 #9 Declared by the steward; Atlas has not read this PR.

Doctrine compilation and release gate Release 1

Homepage restated around the holonarchy holonarchy homepage

Software Hub domain surface software-hub

Do the frozen pull requests belong to Atlas or to onsite-hero-app? Two repositories are being treated as one; provenance of the frozen work is unresolved.

Is Repository a substrate, or only an implementation container for Modules? If it is only a container, Repository should not be a first-class registry.

Does software require Place, or is Environment a sufficient substitute? Place survived construction intact; software may distort it.

Is Deployment an Event, a Transition, or both? Determines whether Deployment deserves its own registry.

When does a Dependency stop being a relationship and become an entity? External dependencies with their own lifecycle behave like entities.

Are permissions simply Constraints, or a distinct form of authority? Collapsing them would simplify the model — or lose the authority distinction.

Does Ownership differ fundamentally from Stewardship in software? Construction distinguished them clearly; software conflates them in Git.

Which declared Atlas modules are still actually exercised at runtime? Unexercised modules accumulate maintenance cost without evidence of value.