Eclexia is an Economics-as-Code programming language. It treats energy, time, memory, and carbon as first-class constraints so software can optimize for performance and sustainability together.
Eclexia introduces economics directly into language semantics:
Resource-aware constraints in code (
@requires,@provides)Adaptive solution selection under changing runtime conditions
Shadow-price-based tradeoff decisions
Carbon-aware execution and scheduling
Multi-objective optimization declared at source level
Example shape of an adaptive function:
adaptive def matrix_multiply(A: Matrix, B: Matrix) -> Matrix
@requires: energy < 100J, latency < 500ms
@optimize: minimize energy, minimize carbon
{
@solution "gpu_accelerated":
@when: gpu_available && matrix_size > 1000
@provides: energy: 50J, latency: 100ms, carbon: 5gCO2e
{
gpu::multiply(A, B)
}
@solution "parallel_cpu":
@when: cpu_cores >= 4
@provides: energy: 80J, latency: 300ms, carbon: 8gCO2e
{
parallel::multiply(A, B)
}
}
# Build from source (Rust 1.75+)
cargo build --release
# Run tests
cargo test --workspace
# Run a sample program
cargo run -- run examples/hello.eclCompiler binary:
target/release/eclexia
For a fuller walkthrough, use GETTING_STARTED.
| Document | Purpose | Audience |
|---|---|---|
| Getting Started | Installation, first run, and CLI usage | New users |
| Quick Status | Snapshot of what works and what does not | Users and contributors |
| Specification | Language syntax and semantics | Language implementers |
| Whitepaper | High-level design and motivation | General and research audience |
| Proofs | Formal statements and theorem development | Researchers |
| Formal Verification | Coq/Agda proof status and verification notes | Researchers and maintainers |
| Implementation Roadmap | Medium/long-term engineering roadmap | Contributors and maintainers |
| Toolchain Status | Status of compiler/runtime/tooling components | Contributors |
| Algorithms | Algorithmic details and implementation notes | Contributors and researchers |
| Bibliography | Research references used by the project | Researchers |
As of QUICK_STATUS (updated 2026-02-12):
Alpha stage
Core compiler pipeline functional
Runtime components available with active development
Conformance and workspace tests are in regular use
This repository has many deep-dive documents. The README now stays focused on orientation, while detailed operational and research content lives in dedicated docs and wiki pages.
eclexia/
├── README.adoc
├── compiler/ # compiler crates and CLI front-end
├── runtime/ # runtime crates (scheduler, profiling, carbon, shadow)
├── libraries/ # ecosystem libraries
├── stdlib/ # standard library sources
├── examples/ # sample .ecl programs
├── tests/ # conformance and integration tests
├── formal/ # Coq/Agda artifacts
└── docs/ # reference docs, tutorials, and generated docs
The README should remain a concise project entry point. Long-lived narrative and frequently evolving content is better placed in the wiki.
Recommended wiki destinations:
Architecture walkthroughs and subsystem maps
Backlog triage and milestone notes
Design discussions and ADR-style rationale
Research notes and reading guides
Contributor onboarding playbooks
Proposed wiki structure and migration map: docs/wiki/README.md
Eclexia is licensed under MPL-2.0. See LICENSE and LICENSE.
General: [info@eclexia.org](info@eclexia.org)
Research: [research@eclexia.org](research@eclexia.org)
Security: [security@eclexia.org](security@eclexia.org)
Repository: https://gitlab.com/eclexia-lang/eclexia
Make resource-efficient, carbon-aware software the default, not the exception.