nextgen-languages is a pure coordinator. It references independent canonical project repositories and holds cross-language indexes, evidence notes, governance, and navigation. This diagram shows conceptual relationships, not a shared runtime or an in-tree component layout.
┌──────────────────────────────────┐
│ nextgen-languages (this repo) │
│ pure coordinator │
├──────────────────────────────────┤
│ README / EXPLAINME │
│ LANGUAGES.a2ml + languages/*.adoc│
│ status + audit + ecosystem map │
│ coordinator checks + wiki │
└────────────────┬─────────────────┘
│ links; does not vendor
┌───────────────────────────────┼────────────────────────┐
▼ ▼ ▼
Core language projects Related project roles Learning layer
- My-Lang, JtV, betlang - syntax surfaces - curriculum
- AffineScript, Ephapax (AffineScript family) - evangeliser
- Eclexia, Oblíbený - formal substrates - BerryWiki optional
- Phronesis, WokeLang - targets/libraries wiki editor
- Anvomidav, Error-Lang - -iser tools
- Tangle, Haec, Firmboot - adjacent research
- KitchenSpeak (experimental)
- 007 (private, index-only)
- TypeFix Zero (exploratory,
private; not a committed member)
Each implementation, detailed specification, and proof remains in its own
canonical repository. An edge in the related-project layer is typed and does
not imply technical integration unless the link is explicitly verified.-
README — front door.
-
EXPLAINME — architecture and scope boundaries.
-
Ecosystem map — full project crosswalk with relationship types.
-
Language pointers — canonical links for the committed portfolio entries.
-
LANGUAGES.a2ml — machine-readable registry (17 records: 16 committed entries plus exploratory TypeFix Zero).
-
Tooling status — dated, unverified tables; read its warning before using them.
-
Portfolio audit — evidence snapshot.
The registry’s status field is not a standards readiness grade. The coordinator records no family-wide completion percentage. TBD means no value is verified here; implementations and current readiness evidence live in each owning project.
Separate database and type-theory estates—including the KRL resolution stack, VeriSimDB, Quandledb, TypeLL, and PanLL—are out of this registry’s scope. Tangle is an independent language and is not represented here as a KRL dependency. See the adjacent-project section in the ecosystem map for qualified pointers.
When a committed family member is added, removed, renamed, or extracted, update the registry surfaces together and run bash hooks/validate-language-registry.sh. For adjacent surfaces, tools, libraries, targets, education projects, or research neighbors, update docs/ecosystem-map.adoc and the [portfolio-adjacent] section of ECOSYSTEM.a2ml; do not enlarge the core family by default. Then run bash hooks/validate-coordinator-boundary.sh.