Skip to content

Latest commit

 

History

History
120 lines (100 loc) · 6.16 KB

File metadata and controls

120 lines (100 loc) · 6.16 KB

The -iser Atlas — find the right -iser

This is the map. If you have a codebase and a need, this page routes you to the -iser that grants it — the "right place" index for the augmentation family. It is the coordination layer for Aspect-Oriented Language Design (see theory/AOLD.adoc) and the Integrated Stack of Stacks (theory/iSOS.adoc).

How to read this

Every -iser injects one specialist language’s superpower into the code you already have, via manifest → Idris2 ABI → Zig FFI → codegen → build/run. You do not learn the language. Find your need in the left column; go to the -iser in the middle.

Route by need

I want to… Use Aspect / language essence

…distribute a single-machine workload across a cluster

chapeliser

Chapel data-parallelism

…push array/number crunching onto the GPU

futharkiser

Futhark kernels

…make a Python/R pipeline ~100× faster

julianiser

Julia

…add fault tolerance / supervision to concurrent code

otpiser

OTP/BEAM

…get data-race freedom for concurrency

ponyiser

Pony reference capabilities

…optimise an image/video pipeline

halideiser

Halide schedules

…rewrite array patterns as optimised primitives

bqniser

BQN

…generate high-performance C libraries

nimiser

Nim metaprogramming

…prove critical functions correct-by-construction

dafniser

Dafny

…model-check a state machine

tlaiser

TLA+/PlusCal

…find counterexamples in an API model

alloyiser

Alloy

…get proven-correct wrappers from interfaces

idrisiser

Idris2 dependent types

…verify real-time embedded logic

lustreiser

Lustre

…add formal type safety to a query language

typedqliser

graded type systems

…wrap C in zero-cost memory safety

atsiser

ATS linear types

…enforce use-exactly-once on resources

ephapaxiser

Ephapax linear semantics

…target WASM with affine + dependent types

affinescriptiser

AffineScript

…augment any database (drift/provenance/temporal)

verisimiser

VeriSimDB octad

…make configs self-validating

k9iser

K9 contracts

…add cryptographic attestation to markup/config

a2mliser

A2ML

…make operations reversible + auditable

oblibeniser

Oblíbený

…add energy/carbon/cost awareness

eclexiaiser

Eclexia

…put provably-safe ethical guardrails on an AI agent

phronesiser

Phronesis

…add consent flows + accessibility

wokelangiser

WokeLang

…model uncertainty over deterministic code

betlangiser

Betlang ternary probability

…expose a complex API progressively

mylangiser

My-Lang

…formalise ISU figure-skating notation

anvomidaviser

Anvomidav

…scaffold a brand-new -iser for another language

iseriser

the meta-framework

Note
Status across the family is scaffold → pre-alpha; chapeliser, verisimiser, and typedqliser are the most developed. Each -iser’s own ROADMAP.adoc is the source of truth for its maturity. (The family READMEs historically over-stated test counts; trust the per-repo cargo test output.)

What -iserisation is — and is not

-iserisation is… …and it is not

augmentation: bolt one specialist language’s power onto a foreign host

aggregate-library: aLib is the dual — the minimal overlap common to all systems. -isers add the exotic edge; aLib distils the shared core.

a coordination atlas: the index that sends you to the right capability

nextgen-language-evangeliser: that advocates adopting whole next-gen languages; the atlas routes you to a capability, no adoption required.

a family of proof-carrying seams (Idris2 ABI + Zig FFI)

the dyadic language/toolchain design of Ephapax, or an AffineScript "face".

The pattern in one diagram

        your app  ──►  <name>.toml  ──►  the -iser CLI
                                            │
                          ┌─────────────────┼─────────────────┐
                          ▼                 ▼                 ▼
                    Idris2 ABI           Zig FFI        target codegen
                  (prove interface)   (C-ABI bridge)   (specialist lang)
                          └─────────────────┴─────────────────┘
                                            ▼
                              your app, now wearing the aspect

Getting started

# install any -iser (standalone Rust binary)
cargo install chapeliser        # …or any name above

# the shared five-command interface
<iser> init        # write a manifest for your project
<iser> validate    # check it against the Idris2 ABI spec
<iser> generate    # emit the specialist-language code
<iser> build       # build the generated output
<iser> run         # run it

To create an aspect for a language that has no -iser yet, use the meta-framework: iseriser generate -m <language>.toml -o ./<name>iser (see examples/newlang/iseriser.toml).

See also

  • theory/AOLD.adoc — the design philosophy (languages as aspects).

  • theory/iSOS.adoc — the architecture (composing aspects).

  • ../README.adoc — family overview, architecture diagram, full install/usage.