This is the longer explanation behind the README. It is written to answer three practical questions: what this repository owns, how to tell portfolio members from neighboring projects, and where to go for authoritative evidence.
Think of the ecosystem as a set of independent projects connected by explicit edges, not one product with one compiler:
nextgen-languages (this repository)
├── indexes the scoped core portfolio and maintains cross-project navigation
├── links to canonical language repositories (implementation/specification owners)
├── records selected relationships to substrates, surfaces, tools, and curriculum
└── does not vendor language code, proofs, grammars, or per-language tutorialsA project appearing in the registry means it belongs on this portfolio’s index. It does not mean the project is complete, production-ready, interchangeable with another entry, or integrated into a common runtime.
| Information | Canonical source | This coordinator’s role |
|---|---|---|
Member list and stable project identifiers |
|
Maintains an indexed list and validates its matching human pointers and cross-references. |
Language implementation, its detailed specification, grammar, proofs, and current roadmap |
The project’s own repository |
Links and brief cross-project orientation only. Do not infer implementation status from this file. |
Cross-language readiness, evidence needs, and portfolio history |
|
Summarizes only evidence with a stated scope and date; does not replace upstream test results. |
Shared infrastructure or theory |
Its own repository (for example |
Records a relationship when useful; does not copy its source or claim every indexed language uses it. |
General curriculum and learner projection |
|
Points to the curriculum. It is not a language repository and must not be audited as one. |
Wiki navigation |
|
Provides portfolio-level orientation. The wiki files carry BerryWiki metadata so they can also be browsed/edited with the separate BerryWiki tool. |
The registry intentionally has a narrow scope. It contains 17 records: 16 committed entries represented by human pointers, plus one exploratory/private TypeFix Zero record that is not yet a committed family member. See .machine_readable/LANGUAGES.a2ml for exact IDs, canonical links, status labels, and privacy notes. Firmboot is a continuity research prototype, KitchenSpeak is an experimental domain-specific DSL, and 007 is private and index-only. These differences are surfaced rather than flattened into a claim that all are comparable implementations.
Neighboring repos are useful to discover but are not silently added as languages:
-
Syntax surfaces related to AffineScript (CafeScripto, JaffaScript, LucidScript, PseudoScript, RattleScript) are separately housed projects that explore how familiar syntax can connect to affine guarantees. Their canonical home is their own repo; they are not five extra core-family entries.
-
Kategoria is a multi-route language/type-safety exploration. Panoply is a safety-claim discipline. Their scope overlaps language research, but neither is represented as a core family member by the registry.
-
typed-wasm is a compilation target and ABI convention substrate, not a source language. echo-types is a formal library, not a language.
-
The
*-iserrepositories expose selected analysis or transformation ideas from parent languages. An adapter or linter is not the language implementation itself. -
The curriculum and evangeliser projects teach or present languages; they are not language implementations.
-
Database and type-theory estates have their own coordinators and registries. They are mentioned only where a real connection helps orientation.
The crosswalk in the ecosystem map uses distinct relationship labels. A documented dependency is different from a shared topic, an alternate surface, an educational tool, or a proposed connection.
The registry’s status indicates a broad project phase, not a grade. TOOLING-STATUS.adoc preserves TBD where a value has not been checked. Do not convert a design note, repository description, old test count, proof file, or planned integration into a current readiness grade.
The portfolio audit dated 2026-09-07 describes repository snapshots and identifies evidence gaps; it explicitly does not assign blanket readiness grades. Open each canonical repository’s current README, roadmap, test workflow, and proof documentation before making a current implementation claim.
A mechanised lemma, a verified checker, a prototype runner, and an end-to-end implementation correspondence are different claims. The audit and PROOF-NEEDS.adoc call out where these boundaries matter. This coordinator intentionally avoids stating that one repository’s formal result proves another project’s implementation unless the connecting argument and CI evidence are present.
The standalone-repository model gives each project a clear source of truth, release cadence, and ownership boundary. It also avoids presenting stale copied code or specifications as canonical. This repo therefore holds registries, cross-project analysis, governance, and navigation—not language implementations.
The boundary is mechanically checked by:
bash hooks/validate-coordinator-boundary.sh
bash hooks/validate-language-registry.shHistorical material that was found in the coordinator and has not yet been verified as landed upstream is documented in EXTRACTION-MANIFEST.adoc and staged under extraction-queue/. Do not treat the queue as canonical language content.
-
Start with README for the front door.
-
Use the language index to open canonical repositories.
-
Use the ecosystem map to follow relations by type.
-
Use tooling status and the dated audit for scoped evidence.
-
Use Wiki Home for the BerryWiki-compatible reading path.
-
For contribution rules, read CONTRIBUTING and GOVERNANCE.
A public repository search in the Hyperpolymath and Metadatastician estates on 2026-09-26 did not identify a language repository called ziz. No project facts or canonical link are invented here. If the intended project is private, differently named, or in a different owner namespace, add it only after its owner, URL, relationship to this portfolio, and visibility policy are confirmed.