This roadmap is for nextgen-languages as a pure coordinator. It does not schedule implementation work owned by individual language repositories, promise that every language will reach production, or prescribe a shared ABI/package registry.
-
Keep README, EXPLAINME, the portfolio map, and wiki navigation accurate and usable as front doors.
-
Maintain a scoped core registry and a separate map of related syntax surfaces, libraries/targets, tools, curricula, and research neighbors.
-
Preserve evidence boundaries: date status snapshots; distinguish formal models, implementations, and tested integrations.
-
Resolve known discovery questions only from authoritative owner information: the
jtv/jtv-langrelationship and the requested “Ziz” project pointer. -
Keep the coordinator boundary and registry validation checks passing.
-
Replace legacy tooling tables with evidence-backed, dated snapshots or remove them when no longer useful.
-
Establish a lightweight process for refreshing cross-repository status and recording link/lineage changes.
-
Add shared conformance infrastructure only where participating language owners agree on scope, semantics, and maintenance responsibility.
-
Building or releasing language implementations from this coordinator.
-
Assigning one readiness grade to the whole family.
-
Declaring a common compiler, runtime, ABI, package manager, or production target without implementation and governance evidence.
-
Moving or editing sibling-repository content from this repository’s branch.
Coordinator state lives in .machine_readable/descriptiles/STATE.a2ml. Canonical project details live in their owning repositories. Start with README and the ecosystem map.