Ecosystem overview¶
As of the 2026-07-31 baseline seed (issue #3). Grounded in the current state of all five source repos.
The Adepthood ecosystem is five repositories orbiting one body of ideas — the APTITUDE program and the Archetypal Wavelength — plus this docs repo, which documents all of them.
The five repos and how they relate¶
| Repo | What it is | Stack |
|---|---|---|
Geoffe-Ga/adepthood |
The flagship app: journal-first PKM with optional depths (habits, practices, course, community) | React Native + Expo frontend, FastAPI + PostgreSQL backend |
Geoffe-Ga/aptitude-course |
The 36-week, 10-stage APTITUDE curriculum as versioned Markdown content | Markdown corpus + Python build scripts + JSON Schema manifest |
Geoffe-Ga/Creek-Vault |
CLI + pipeline that organizes personal data exports into an Obsidian knowledge vault | Python (Typer CLI), local-first NLP, MCP server, Discord bot |
Geoffe-Ga/WavelengthWatch |
watchOS companion for browsing the Archetypal Wavelength from the wrist | SwiftUI watch app + FastAPI/SQLModel backend (SQLite) |
Geoffe-Ga/wavelength-demo |
Scroll-driven promo page making the Wavelength visceral | React 18 + Vite + TypeScript |
The connective tissue:
- Shared ontology. Adepthood's ten Aspects equal Creek's Frequencies equal
the Wavelength phases' parent stages (adepthood
NORTH-STAR.md, section 11; Creek-Vaultdocs/Ontology/). The same ten-stage, six-phase model drives the app, the vault classification, the watch catalog, and the demo page. - Content consumption. The Adepthood app vendors a pinned commit of
aptitude-courseand reads it exclusively through the generatedmanifest.json(aptitude-courseCONSUMPTION.md). See ADR 0011. - Promotion.
wavelength-demolinks out to the philosophy and to WavelengthWatch; it shares the six-phase vocabulary (Rising, Peaking, Withdrawal, Diminishing, Bottoming Out, Restoration) from itssrc/data/modes.ts. - Documentation. This repo (
adepthood-docs) pulls merged-PR activity from all five and folds it into this corpus (epic #1; ADR 0013).
Knowledge-graph federation¶
Every repo carries a queryable code graph built by the pinned graphify
toolchain (PyPI graphifyy), and adepthood federates them.
- Per-repo graphs. aptitude-course, wavelength-demo, and WavelengthWatch
commit their graphs in-tree at
graphify-out/graph.jsononmain. Creek-Vault's graph is ~30 MB and ships as a rolling GitHub Release asset instead of being committed. Adepthood git-ignoresgraphify-out/entirely and distributes via release (see next point). Source: adepthoodscripts/graph/README.md, "Federation (nightly)". - Adepthood's rolling release. The
graph-buildworkflow keeps a rolling release taggedknowledge-graphcarryinggraph.jsonandgraph-meta.json, at most 24h stale. A weeklygraph-semanticworkflow upgrades the graph fromcode-onlytocode+semanticwith an LLM pass over the prose corpus, publishingsemantic-meta.json, a semantic cache, and an agent-crawlablewiki.tar.gz. pan-graph.json. The nightlygraph-federateworkflow (cron 06:10 UTC) merges adepthood's own graph with the four satellite graphs into onepan-graph.json+pan-meta.json, published on the same rolling release. An unfetchable satellite is skipped with a warning; only a missing adepthood-own graph fails the job.pan-meta.jsonrecords exactly which repos made it into each build.- This repo as satellite #6. Epic #1 (decision 6) plans for
adepthood-docsto commit its own graph in-tree (the small-corpus satellite pattern) and join the federation; that lands with issue #6 and an adepthood-side federation change. Not yet implemented as of this baseline.
See Query the knowledge graph for the commands, and ADRs 0008, 0009, and 0010 for the rationale.