USE · WHAT SHIPS TODAY
What ships today
The constellation is largely substrate-in-progress — but atlas, the structure layer, is real and runnable right now. Here's what you can actually do today.
Inspect the constellation
atlas is a zero-dependency CLI — everything here runs straight from GitHub with npx, no install, no token:
npx github:Bitspark/atlas doctor # run every structural check (what CI runs)
npx github:Bitspark/atlas topology gen # render the family map from constellation.json
npx github:Bitspark/atlas guide newcomer # orient yourself in the constellation
npx github:Bitspark/atlas explain repo ontos
doctor is the same gate CI runs: it assembles the topology, checks every member's manifest, and fails on drift. Nothing here is a mock — this site's systems, stack, and dashboard are all rendered from the very data these commands produce.
Check a member's place in the family
Each member carries an atlas.json manifest — its layer, its typed dependencies (build, runtime, contract), its docs surface. Validate one, or see what every repo is pinned against:
npx github:Bitspark/atlas manifest validate atlas.json
npx github:Bitspark/atlas pin explain --all # the design / atlas / substrate pins each repo runs against
Trace docs across repos
The docs hub is generated from each repo's exported docs manifest. The same machinery runs offline:
npx github:Bitspark/atlas docs export --check # is this repo's docs manifest fresh?
npx github:Bitspark/atlas crosslinks docs # do cross-repo doc links actually resolve?
npx github:Bitspark/atlas docs catalog # assemble the cross-repo docs catalog
See where a change lands
npx github:Bitspark/atlas impact --repo ontos --symbol V
reports the blast radius of a change across the constellation — which members, which edges, what it touches.
What's still developing
The substance systems — ontos, logos, thesmos, horos, stele, arche — are at varying maturity. The dashboard tracks each one honestly, and the examples mark what is real today versus still a sketch. To go deeper on any of them, read its exported docs or the substrate theory.
Working with it
Go further with the runbooks — task-by-task guides (run the checks locally, add an example, trace a dependency, read a dashboard absence) — and the FAQ for the common questions.