Next-Generation Languages

A research portfolio and coordination hub for independent language projects in the Hyperpolymath ecosystem. This repository is an index and map: it does not build, host, or vendor the languages themselves.

Important

Start here: this README is the short orientation; EXPLAINME explains the boundaries and connections; the ecosystem map shows the projects by role; and the language index links to each canonical project. The wiki’s Home page is BerryWiki-compatible navigation for readers who prefer a wiki.

Table of Contents

• What this is
• Find your way
• Portfolio at a glance
• Connected work: related, not all members
• Status and limitations
• Checks for this repository
• Licensing

What this is

The portfolio gathers research into languages and language-like systems that make important structure explicit: resources, termination, deadlines, consent, ethics, topology, uncertainty, construction, continuity, and physical constraints. They are related by research interests, not by a shared compiler, runtime, or promise of mutual compatibility. Read each project’s own documentation for its current implementation and evidence.

This repository’s responsibilities are to:

• maintain the scoped portfolio registry and links to canonical repositories;

• explain project roles, boundaries, lineages, and cross-project dependencies;

• maintain cross-language status and evidence summaries without upgrading claims by implication;

• provide governance, navigation, and language-agnostic contributor orientation.

Language implementations, language-specific specifications, grammars, proofs, and tutorials belong in their own canonical repositories. The boundary is checked by hooks/validate-coordinator-boundary.sh and hooks/validate-language-registry.sh.

Find your way

If you want to…	Go to…
Choose a language or understand the core portfolio	Language quick reference · Portfolio overview
See how projects relate (without conflating them)	Ecosystem map
Find the canonical repository for a language	Language pointers · Machine-readable registry
Check evidence, tooling, and open readiness gaps	Tooling and integration status · Status tracker · Portfolio audit
Understand architecture and scope boundaries	EXPLAINME · AI and coordinator rules · Extraction history
Contribute to this coordinator	Contribution guide · Governance · Security reporting
Read wiki-format material	Wiki Home (plain Markdown; BerryWiki-compatible; browse locally with berrywiki serve ./wiki --no-commit)

Portfolio at a glance

The machine-readable registry in .machine_readable/LANGUAGES.a2ml is the authoritative list for this coordinator. It contains 17 records: 16 committed portfolio entries with human pointers, plus one exploratory/private TypeFix Zero record that is intentionally not a committed family member. The committed set includes the My-Lang dialect family, experimental KitchenSpeak DSL, Firmboot continuity-research prototype, and private index-only 007. Inclusion means indexed here, not mature, mutually compatible, or production-ready.

Area	Projects	Main question
Resource and use disciplines	AffineScript, Ephapax, Eclexia, Oblíbený	How should resource use, consumption, cost, or termination constrain programs?
Values, consent, and real-time obligations	Phronesis, WokeLang, Anvomidav	How can ethical constraints, consent, or timing obligations become explicit?
Computation, uncertainty, and teaching	My-Lang, betlang, JtV, Error-Lang	How do dialect progression, stochastic choice, construction, and failure shape computation?
Topology and structured change	Tangle, Haec, Firmboot	How do equivalence, property-loss, and continuity behave under transformation?
Domain or restricted entries	KitchenSpeak (experimental DSL); 007 (private, index-only); TypeFix Zero (private, exploratory)	What can domain-specific constraints or minimal calculi teach us?

These groupings are navigational, not a formal taxonomy. Full summaries, statuses, and boundaries are in the ecosystem map and canonical project repositories.

Connected work: related, not all members

Several neighboring projects extend or study this work without being additional entries in the core language registry:

• AffineScript surfaces: CafeScripto, JaffaScript, LucidScript, PseudoScript, and RattleScript explore familiar syntax surfaces over AffineScript’s resource-safety direction. Treat them as related surface projects, not five new core languages.

• Foundations and research labs: Kategoria explores routes through type-safety levels; Panoply is an envelope-first safety-claim discipline. They are related to language design, but have different scopes.

• Shared substrates and targets: typed-wasm is a WasmGC target/ABI substrate; echo-types is a formal library for structured information loss. Neither is itself a member language here.

• Teaching and application: tentacles-agentic-syllabus is a curriculum framework, not a language. Language-specific teaching materials remain with their owning projects.

• Wiki tooling (Metadatastician estate): BerryWiki provides optional editing and navigation for ordinary Markdown wiki content. The portfolio wiki files remain in this repository and work without BerryWiki.

• Language augmentation tools: the *-iser projects apply selected ideas from a language to other codebases; they are tools, not implementations or language-family members. See the map for examples and boundaries.

The public GitHub estate search did not identify a ziz repository or a language project by that name. It is intentionally not guessed into the registry. If “Ziz” refers to a private repository or a different spelling/owner, its canonical URL and intended role are needed before it can be indexed accurately.

Status and limitations

This is a research portfolio, not a unified language platform. Stages range from conceptual specifications to experimental implementations and partially verified cores. Readiness values are evidence-scoped; TBD means no coordinator-verified value, not a grade. The most recent cross-portfolio review is the 7 September 2026 audit; consult each upstream repository for changes since that snapshot.

The projects do not automatically share syntax, semantics, compilers, ABI, or release schedules. Connections in this repository are classified as dependency, shared substrate, syntax surface, tool, curriculum, or research adjacency so that a link does not imply an integration that has not been demonstrated.

Checks for this repository

No language build is expected here. From the repository root, run:

bash hooks/validate-language-registry.sh
bash hooks/validate-coordinator-boundary.sh

These check registry consistency and prevent language-specific implementation content from being copied into the coordinator. See the contributor quick start for the full coordinator checks.

Warning

Open supply-chain follow-up: bash hooks/validate-sha-pins.sh currently reports 29 workflow action references that use tags rather than commit SHAs. .github/workflows/actions.lock records tag-to-commit resolutions, but does not make those uses: lines immutable. The supported gh actions-lock tool could not be downloaded in this environment (release-asset transfer returned EOF), and the generated lock must not be hand-edited. Treat the SHA-pin check as outstanding until the lock tool can safely update workflows and lockfile together.

Licensing

Project code and configuration use MPL-2.0; documentation uses CC-BY-SA-4.0 as marked in file headers. See LICENSE and LICENSES/ for the license texts.