Software

Software as a living system — and a pressure test of the Atlas ontology

Registry explorer

Endless-Technologies/Atlas

repo.atlas

Repositories

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

repositoriesoperatingrepositoryatlas

Platform

TypeScript, SQL, CSS, TanStack Start, React 19, Tailwind v4, Vitest, GitHub

Licence

undeclared

Declared date

not declared

Category listing

Read only

Declared record

Fields and provenance

kind

repository

name

Endless-Technologies/Atlas

domain

atlas

productId

product.atlas

lifecycle

operating

purpose

Constitutional orchestration layer: identity, navigation, permissions, events, evidence, interoperability.declared · README.md

provider

GitHubdeclared · project settings

url

https://github.com/Endless-Technologies/Atlasdeclared · stated by steward

languages

  • TypeScript
  • SQL
  • CSS
observed · package.json, supabase/migrations

frameworks

  • TanStack Start
  • React 19
  • Tailwind v4
  • Vitest
observed · package.json

defaultBranch

mainobserved · sync settings

currentBranch

mainobserved · sync settings

latestCommit

Unknown · cannot-locateWhich commit is HEAD on the GitHub remote right now?

openPullRequests

Unknown · cannot-locateAre frozen PRs 8 and 9 on Atlas or on onsite-hero-app?

openIssues

Unknown · cannot-locate

deploymentStatus

Preview live; production not publishedobserved · project URLs

documentationStatus

Doctrine under mem/, architecture under src/modulesobserved · mem/index.md

testStatus

2067 tests passing at Release 1observed · release gate run

dependencyHealth

Pinned after security pass; audit clean at Release 1observed · dependency pass

responsibleParty

Endless Technologies (steward: Jarrod Cobb)declared · org settings

connectedAgentIds

  • agent.alice
  • agent.steward
  • agent.lovable

lastMeaningfulChange

Holonarchy homepage + doctrine compilationobserved · mem/doctrine/compilation-release-1.md

health

availability: strong
correctness: strong
tests: strong
dependency-integrity: fair
maintainability: fair
security: fair
documentation: strong
deployment: fair
provenance-confidence: fair
unresolved-observations: strained
constraint-pressure: strained

usableStateSpace

capacity: Large module surface: 60+ modules, 80+ routes, full registry spine.
consumedBy:
  • Deferred-seed boundary (Saint Nick, Diamond, Skill Garden, extra hubs)
  • Release-gate test floor
  • Atlas↔HomeFlow contract stability
practicalFreedom: workable
evidence:
  • Most new work must extend an existing registry rather than add one.
  • Sync to HomeFlow is deliberately disabled, narrowing runtime experiments.

Relationships

Declared edges

22

Neighbourhood

Related products

Neighbourhood

Related modules

Evidence chain

What this entry rests on

Events

1
  • evt.org-move — 2026-08-22 · repository.transferred · Atlas repository moved from personal account to Endless-Technologies.

Observations

2
  • obs.remote-mismatch — explained · Sandbox origin points at Lovable private transport, which is not evidence that GitHub sync is broken. Two different transports were conflated.
  • obs.test-floor — open · Test count rose to 2067 with no runtime regression; correctness confidence is high but coverage of the gateway path remains untested end to end.

Decisions

0

None declared for this entry.

Constraints

2
  • con.grants — security · Migrations that create tables must grant explicitly in the same migration.
  • con.no-node-only — technical · Server code runs on workerd; Node-only packages are rejected.

Changes

3
  • chg.release-1 — release · Release 1 · Doctrine compilation and release gate
  • chg.homepage — commit · holonarchy homepage · Homepage restated around the holonarchy
  • chg.software-hub — branch · software-hub · Software Hub domain surface

Open questions

3
  • q.repo-identity — open · Do the frozen pull requests belong to Atlas or to onsite-hero-app?
  • q.repo-substrate — open · Is Repository a substrate, or only an implementation container for Modules?
  • q.ownership-stewardship — under-test · Does Ownership differ fundamentally from Stewardship in software?