Portfolio Vol. I — No. 01 United States

Eric Malamisura


Applied AI Engineer · Programming Language Designer · Creator of OriLang

The Front Page

I build applied AI systems, programming languages, developer tools, and software products. My current work centers on OriLang and its compiler, including tools that help AI models write and reason about code more reliably.

Portrait of Eric Malamisura
Fig. 01 — Eric Malamisura. Hover for an ASCII rendering.
  • THE WIRE — UNITED STATES
  • ORILANG: ACTIVE DEVELOPMENT (2026 — present)
  • ORITERMINAL: ALPHA (2026 — present)
  • CLOUDLAYER.IO: IN PRODUCTION (2020 — present)
  • UPSTAT: IN PRODUCTION (2022 — present)
  • WARPKIT: ALPHA — IN PRODUCTION USE (2023 — present)
  • ORIJS: ALPHA — IN PRODUCTION USE (2023 — present)
  • AI SYSTEMS, PROGRAMMING LANGUAGES, DEVELOPER TOOLS, AND SOFTWARE PRODUCTS.
  • PRESS ` FOR THE TERMINAL
(01) — About

From language
design to
working products.

Eric Malamisura is an applied AI engineer, programming-language designer, and founder. He created OriLang, a statically typed, natively compiled programming language, and is building its compiler and AI-oriented language tooling.

His work on OriLang spans type inference, value semantics, automatic reference counting, capability-based effects, integrated testing, and LLVM code generation. The project reflects his focus on making ambitious systems ideas practical for working developers.

Eric is the founder of Elucidsoft (founded in 2010), an independent software company. He also builds applied AI features, a GPU-accelerated terminal emulator, the cloudlayer.io and Upstat software products, and the WarpKit and OriJS frameworks used in those products. His work moves between AI, low-level systems engineering, and product development.

(02) — The Language

If it compiles,
it's tested.

This is OriLang. Testing is not a library — it is a language keyword, enforced by the compiler. Whole-program type inference, value semantics with automatic reference counting, and native binaries through LLVM.

  • 01 Hindley–Milner inference — whole program
  • 02 ARC + value semantics — no GC, no borrow checker
  • 03 `tests` is a keyword — untested code won't compile
  • 04 LLVM native binaries — Windows, Linux, macOS
Read the OriLang story
shape.ori ori test
// Every function ships with its test — enforced by the compiler.
use std.testing { assert_eq }

type Shape = Circle(radius: float) | Square(side: float);

@area (s: Shape) -> float = match s {
    Circle(radius:) -> radius * radius * 3.14,
    Square(side:) -> side * side,
}

@test_area tests @area () -> void = {
    assert_eq(actual: area(s: Circle(radius: 2.0)), expected: 12.56);
    assert_eq(actual: area(s: Square(side: 3.0)), expected: 9.0)
}
$ ori test shape.ori 1 passed, 0 failed — OK
Fig. 02 — Real Ori, from the compiler’s spec suite — compiled and test passing (1 passed, 0 failed) before publication.
(03) — Selected Work

Selected work,
from systems to SaaS.

A programming language and compiler, a GPU terminal, two software products, and the frameworks that support them. Each case study explains my role, the technical approach, and the project’s current status.

(04) — The Craft
  • 01 Applied AI
  • 02 AI Language Tooling
  • 03 Compiler Engineering
  • 04 Programming Language Design
  • 05 Type Systems
  • 06 LLVM Code Generation
  • 07 GPU Rendering
  • 08 Distributed Systems
  • 09 Developer Tooling
  • 10 API Platforms
  • 11 Frontend Architecture
  • 12 Real-Time Systems
(05) — Colophon

Still
compiling.

I work across applied AI, programming languages, systems, and software products. If that overlaps with a problem you are working on, send me a note.