Skip to content

hyperpolymath/nextgen-languages

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

185 Commits
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Next-Gen Languages

Parent repository for tracking and coordinating experimental language development

IMPORTANT: This is a PARENT REPOSITORY ONLY - it contains documentation and tracking but NO implementation code.

Overview

This repository serves as the central tracking hub for the Next-Gen Languages initiative—a coordinated effort to design and develop ten programming languages that collectively cover the full spectrum of modern software challenges, from AI-native development to formally verified real-time systems.

All language implementations are in their respective canonical repositories.

Language Comparison

Language Core Philosophy Primary Paradigms Key Features Target Domain

Solo

Dependable foundation for systems programming

Imperative, Concurrent, Contract-Based

effect, go, where { pre: …​, post: …​ }

General Systems Programming

Duet

AI-assisted development (Neuro-Symbolic) for verifiable software

Imperative, Contract-Based, Neuro-Symbolic

@synth, @verify, intent("…​")

High-Assurance, AI-Assisted Systems

Ensemble

AI as a first-class, native component of the language

Imperative, AI-as-Effect

ai_model {}, prompt {}, AI<T> effect type

AI-Native Applications, AI Agents

Phronesis

Formal, auditable specification of an agent’s ethical framework

Declarative, Logic-Based, Agent-Oriented

Agent., Values:, EVALUATE(…​)

AI Safety, Alignment, and Auditing

Eclexia

Sustainable Software Engineering through resource-first constraints

Declarative, Constraint-Driven

(energy budget …​), (resource …​)

Green Computing, IoT/Embedded, FinOps

Oblíbený

Provably secure, obfuscated code for hostile environments

Turing-Incomplete (Deploy), Metaprogramming

(forbid recursion), (bounded-for …​)

Secure Enclaves (HSMs), Critical Embedded

Anvomidav

Maximalist formal verification for hard real-time systems

Functional, Concurrent, Formal (Linear/Session Types)

task @sched(EDF), Linear<T>, Π (…​) . T

Avionics, Autonomous Vehicles, Robotics

WokeLang

Human-centric programming focused on consent and well-being

Imperative, Natural-Language

only if okay "…​", attempt …​ or reassure

Education, Personal Scripting, Accessibility

Database & Specialized Languages

In addition to the core eight languages, the ecosystem includes specialized languages for database queries and markup:

Language Repository Description Status

GQL-dt

fqldt

FormDB Query Language with Dependent Types

Active

A2ML

a2ml

Attested Markup Language

Active

Satellite Repositories

Each language has its own dedicated repository for implementation:

Language Repository Description Status

betlang

betlang

Bet programming language (foundational experiment)

Active

Solo/Duet/Ensemble

my-lang

Progressive language family (me → solo → duet → ensemble)

Active

Phronesis

phronesis

AI ethics and safety specification

Active

Eclexia

eclexia

Sustainable computing language

Active

Oblíbený

oblibeny

Security-critical embedded language

Active

Anvomidav

anvomidav

Formally verified real-time systems

Active

WokeLang

wokelang

Human-centric programming

Active

AffineScript

affinescript

Affine types for WASM

Active

Ephapax

ephapax

Dyadic linear type system (affine + linear modes) for WebAssembly

Active

Julia-the-Viper

julia-the-viper

Systems programming, Harvard Architecture

Active

Error-Lang

error-lang

Pedagogical language for systems thinking

Active

Languages vs. -iser Tools: What Lives Where

This repository and its satellite repos contain the actual programming languages — full compilers, parsers, type checkers, interpreters, and standard libraries. If you want to write code in Ephapax, WokeLang, Eclexia, or any other nextgen language, you are in the right place.

The -iser repos (in developer-ecosystem) are a different thing entirely. They let you use a language’s unique power without learning the full language, extending what you already do in your own language.

-iser Tool Based On What It Does Location

ephapaxiser

Ephapax

Linear type checking for your existing Rust/ReScript code — use Ephapax’s linear types without writing Ephapax

developer-ecosystem

wokelangiser

WokeLang

Consent annotations and well-being checks for any codebase — use WokeLang’s consent semantics in your language

developer-ecosystem

eclexiaiser

Eclexia

Resource budget analysis for any project — use Eclexia’s energy/resource constraints without rewriting

developer-ecosystem

anvomidaviser

Anvomidav

Formal verification harness for real-time code — use Anvomidav’s verification without its syntax

developer-ecosystem

oblibenyiser

Oblibeny

Security hardening for deployed code — apply Oblibeny’s obfuscation/Turing-incompleteness guarantees externally

developer-ecosystem

affinescriptiser

AffineScript

Affine type linting for WASM projects — AffineScript’s type discipline as a linter

developer-ecosystem

phronesiser

Phronesis

AI ethics audit for any agent codebase — Phronesis safety checks without learning the specification language

developer-ecosystem

Rule of thumb:

  • "I want to write a program in Ephapax" → go to the satellite repo (ephapax)

  • "I want Ephapax’s linear type safety in my Rust project" → use ephapaxiser (developer-ecosystem)

Design Spectrum

The eight languages span a complete spectrum of concerns:

Abstraction Level:     Low ←————————————————→ High
                       Solo                   WokeLang

Verification Rigor:    Minimal ←——————————→ Maximal
                       WokeLang              Anvomidav

AI Integration:        None ←——————————————→ Native
                       Oblíbený              Ensemble

Target Audience:       Expert ←————————————→ Beginner
                       Anvomidav             WokeLang

Documentation

  • LANGUAGES.scm — Detailed language specifications and comparison

  • .machine_readable/6a2/META.a2ml — Architecture decisions and development practices

  • .machine_readable/6a2/STATE.a2ml — Project checkpoint and session history

  • .machine_readable/6a2/ECOSYSTEM.a2ml — Project ecosystem relationships

  • .machine_readable/6a2/PLAYBOOK.a2ml — Operational playbook and workflows

  • .machine_readable/6a2/AGENTIC.a2ml — Agent-oriented language specifications

  • .machine_readable/6a2/NEUROSYM.a2ml — Neuro-symbolic integration specifications

  • MANIFEST.md — Quick reference with status and run commands

  • languages/ — Per-language READMEs with core invariants

Playgrounds

Interactive experimentation sandboxes are now integrated into each language’s canonical repository under a playground/ directory. This consolidation ensures all language-related code (implementation, examples, and experiments) lives in one place.

Quick Start

git clone --recursive https://github.com/hyperpolymath/nextgen-languages.git

Contributing

Each language welcomes contributions. See individual satellite repositories for language-specific contribution guidelines.

License

MIT OR PMPL-1.0-or-later

Architecture

See TOPOLOGY.md for a visual architecture map and completion dashboard.

Sponsor this project

Packages

 
 
 

Contributors