Skip to content

Source status: no status is stated in the source document, so none is assigned here. Do not treat this page as a finalized specification. The normative rules are in the Technical Specification.

First-Version Scope (MVP)

Objective

Build a working prototype that demonstrates the language can catch AI-generated programming mistakes through compiler-enforced rules.

1. Features Included

Language Fundamentals

  • Custom source-code syntax.
  • Variables and strict static types.
  • Functions with explicit inputs and outputs.
  • Basic structs and enums.
  • Explicit return values.

Contracts

  • Preconditions.
  • Postconditions.
  • Invariants.
  • Basic numeric constraints.
  • Runtime enforcement of contracts where static proof is unavailable.

Error Handling

  • Explicit Result types.
  • Declared failure conditions.
  • Required handling of possible failures.

Compiler

  • Lexer and parser.
  • Abstract syntax tree.
  • Type checker.
  • Semantic analyzer.
  • Contract checker.
  • Structured compiler diagnostics.
  • Python code generation.

Testing

  • Basic unit testing.
  • Contract testing.
  • Boundary testing.
  • Verification reports.

2. Deferred Features

The following will not be implemented in the first version:

  • Native machine-code generation.
  • Advanced formal verification.
  • Complex concurrency.
  • Distributed computing.
  • Advanced memory ownership.
  • Package registry.
  • Full networking and database libraries.
  • AI-assisted debugging automation.
  • Advanced security analysis.

These remain part of the long-term vision.

3. First Demonstration Program

The first version must successfully compile and execute the BankAccount example.

It must also reject deliberately incorrect implementations, including:

  • Incorrect types.
  • Missing required declarations.
  • Violated preconditions.
  • Broken postconditions.
  • Invalid state changes.
  • Unhandled failure outcomes.

4. Acceptance Criteria

The prototype is successful when:

  1. Valid source code compiles.
  2. Invalid source code is rejected with useful diagnostics.
  3. Contracts are actually enforced.
  4. Generated Python preserves the language's defined behavior.
  5. Verification reports accurately describe what was checked.
  6. The same source and compiler version produce reproducible results.

Design Goal

Build a small but functioning language that proves its central philosophy before expanding into a complete programming ecosystem.

Source and authority

This page migrates MVP.md in full. It is an explanatory / implementation document, not the normative specification. Where it simplifies a rule, the Technical Specification governs. The original file is preserved in source-original/LANG/.