This map is a navigation aid, not a claim that the projects form one integrated product. The core member list remains .machine_readable/LANGUAGES.a2ml; projects below it are grouped by role so that related work can be found without conflating it with a language implementation.
|
Note
|
Current as of 2026-09-26. Repository descriptions and public repository existence were checked for the newly added adjacent-project links. Relationship classifications describe portfolio scope, not a fresh code audit of each upstream repository. Follow the canonical links for current content. |
The registry has 17 records: 16 committed entries with human pointers, plus one exploratory/private TypeFix Zero record that is not yet a committed family member. Each public project below owns its implementation and detailed specification in its own repository. The list is grouped for discovery, not ranked by maturity.
| Research area | Project | Coordinator-level description | Canonical home |
|---|---|---|---|
Resources, usage, and execution constraints |
AffineScript |
Affine resource discipline; familiar syntax surfaces are listed separately below. |
|
Resources, usage, and execution constraints |
Ephapax |
Dyadic linear/affine type-system research. |
|
Resources, usage, and execution constraints |
Eclexia |
Resource-aware language research. |
|
Resources, usage, and execution constraints |
Oblíbený |
Phase-separated and constrained deployment language research. |
|
Normative, social, and timing constraints |
Phronesis |
Language research for declared values and ethical reasoning. |
|
Normative, social, and timing constraints |
WokeLang |
Consent and awareness-oriented language research. |
|
Normative, social, and timing constraints |
Anvomidav |
Real-time and choreographic language research. |
|
Computation and learning |
My-Lang |
Nested dialect family Solo ⊂ Duet ⊂ Ensemble. “Me” is a runtime projection, not a fourth dialect. |
|
Computation and learning |
betlang |
Probabilistic language research. |
|
Computation and learning |
JtV |
Computation-as-construction and data/control separation research. |
|
Computation and learning |
Error-Lang |
Pedagogical language focused on systems thinking through errors. |
|
Equivalence, properties, and change |
Tangle |
Topological language research; its KRL adjacency is not a claim of language equivalence. |
|
Equivalence, properties, and change |
Haec |
Trope-particularity and graded property-loss research. |
|
Equivalence, properties, and change |
Firmboot |
Continuity obligations across software transformations; a research prototype. |
|
Domain-specific and restricted entries |
KitchenSpeak |
Experimental kitchen-domain orchestration DSL; now standalone. |
|
Domain-specific and restricted entries |
007 |
Private agent meta-language; index-only. No source or private link is mirrored here. |
The-Metadatastician/007 (private) |
Domain-specific and restricted entries |
TypeFix Zero |
Exploratory/private minimal typed teaching core; viability under review. Not a committed family member. |
Design note staged at |
The registry’s status labels distinguish active, design, experimental, specification, and exploratory projects. They are not the standards readiness grades. Private entries intentionally expose only the minimum pointer permitted by their visibility policy.
These projects explore familiar surface syntaxes in the AffineScript direction. They are separate repositories and should be represented as surface projects, not silently added to the 16-entry core language registry.
| Project | Relationship | Canonical home |
|---|---|---|
CafeScripto |
CoffeeScript-shaped AffineScript surface |
|
JaffaScript |
JavaScript/TypeScript-shaped AffineScript surface |
|
LucidScript |
PureScript/Haskell-shaped AffineScript surface |
|
PseudoScript |
Pseudocode-shaped AffineScript surface and pedagogy-oriented project |
|
RattleScript |
Python-shaped AffineScript surface |
The table describes their stated repository relationship; it does not certify feature parity, shared parser internals, or ABI-level integration. Start with AffineScript’s own documentation and then follow each surface repository.
| Project | Role in the wider ecosystem | Canonical home |
|---|---|---|
typed-wasm |
WasmGC target and shared type-layout/ABI work for projects that explicitly use it. Not a source language. |
|
echo-types |
Constructive formal library for structured information loss/residue. Not a source language. |
|
EchoTypes.jl |
Executable finite-domain companion model; not a proof or a language implementation. |
|
Kategoria |
Multi-route exploration of type-safety levels and language-building approaches. Research adjacency, not a core member. |
|
Panoply |
Envelope-first language/safety discipline: claims are explicit, scoped, inspectable, and accountable. Adjacent discipline, not a core registry entry. |
Some languages document dependencies or shared substrates in their own records. A project-wide topic similarity is not a dependency: follow the language’s canonical dependency manifest and tests before relying on one.
The estate includes tools such as affinescriptiser, anvomidaviser, betlangiser, eclexiaiser, ephapaxiser, mylangiser, phronesiser, and wokelangiser.
These aim to apply selected language-derived ideas to other codebases. An -iser is a separate tool with its own maturity and evidence; it is not a compiler for the parent language and its existence does not imply production readiness.
-
tentacles-agentic-syllabus is a curriculum/agentic teaching framework, not a language implementation. It uses My-Lang dialects as one learning vehicle; “Me” is a generated projection, not a dialect.
-
nextgen-language-evangeliser is an educational toolkit, not a language or shared compiler.
-
BerryWiki (Metadatastician estate) is an optional notebook-style authoring/navigation tool. The portfolio wiki remains plain Markdown in this repository; the tool is not a content dependency or canonical language source.
-
Per-language examples and lessons belong with each language’s canonical repository unless that repository explicitly delegates them elsewhere.
This coordinator is not the registry for the database or type-theory estates. TOOLING-STATUS.adoc names selected adjacent projects (including the KRL resolution stack and TypeLL) where those distinctions matter. Keep estate ownership and canonical project status with their own registries.
JtV is indexed here under canonical hyperpolymath/jtv. A separate public hyperpolymath/jtv-lang repository describes related JtV research. Its exact lineage and canonical status have not been confirmed by this coordinator; treat it as a lineage question, not as a second member or a confirmed alias, until the project owner reconciles the repositories.
The public repositories hyperpolymath/ziz and hyperpolymath/Ziz could not be resolved on 2026-09-26, and public estate search did not identify a matching language project. “Ziz” therefore remains an unresolved name only; no registry entry or wiki project page is fabricated. For a private or differently named project, its owner must provide the canonical URL and visibility-safe description.
-
README — short front door and primary routes.
-
EXPLAINME — architecture and claim boundaries.
-
LANGUAGES.a2ml — scoped registry.
-
Language quick reference — concise project pointers.
-
Portfolio audit — dated evidence and limitations.