Kalo

Open-source specification infrastructure

Polyglot code.Zero lock-in.

Define your system in structured specifications. Compile it into the languages, schemas, and implementation artifacts your stack needs.

Own the specification. Portable WASM plugins handle the implementation.

Explore on GitHub Install Kalo
live architectureKA:MO1:YAML1
01 / sourceaccount.mod
name: Account
fields:
  ID:
    type: UUID
  Status:
    type: String
identifiers:
  primary: ID
$ kalo compileresolved · pinned · local
02
.goGo
03
.tsTypeScript
04
.sqlPostgreSQL
one durable contractthree ordinary outputs

Current proof / Morphe

One model. Three parts of the stack.

Morphe is Kalo's first specification ecosystem: a human-readable YAML model can be compiled into concrete Go, TypeScript, and PostgreSQL representations.

01structured source
03verified targets shown
00runtime dependency in output
$ kalo compilereal CLI capture
Kalo CLI compiling a Morphe YAML specification into Go, TypeScript, and PostgreSQL artifacts
Source → portable transformation → files you own

How Kalo works

A small set of composable primitives.

Kalo is the pipeline and plugin infrastructure. Morphe is one specification built on top of it.

SPEC→FORMAT→PLUGIN.WASM→FORMAT
01

Specifications are contracts

Structured, versioned definitions describe what is being implemented independently of one target technology.

02

Formats are representations

A specification can define canonical source formats and explicit target representations without collapsing the two.

03

Plugins compile between them

Portable WASM plugins consume declared inputs and produce declared outputs across a controlled boundary.

04

Pipelines compose the work

Kalo connects transformations into named, repeatable workflows that can branch across your stack.

Go deeper into the architecture

What “zero lock-in” means

Keep the durable part.
Replace the implementation.

Kalo does not promise cost-free migrations. It gives your system an architecture where the specification can outlive any one generator, language, or framework.

01

Own the source of truth

Specifications live with your project, not inside a proprietary runtime.

02

Own the outputs

Generated code and schemas are ordinary implementation assets.

03

Swap implementations

Change generators or target technologies without redefining the model.

04

Run portable plugins

WASM keeps transformations independent of a single plugin language.

Open sourceWASM executionVersioned pluginskalo.lockSHA-256 verifiedDeclarative pipelinesLocal + Git storesCross-platform CLI

Architectural direction

Specifications should be executable infrastructure.

Standards often describe related concepts across schemas, profiles, protocols, and implementation environments. The mapping, validation, and code required to operationalize them is repeatedly rebuilt.

Kalo provides primitives for expressing those relationships as reusable, versioned transformations and validation pipelines.

Kalo is exploring where this architecture can reduce repeated integration work in open-standards ecosystems.

01Specification A → Specification B
02Canonical model → target profile
03Specification → implementation artifacts
04Specification → validation checks
05Version N → version N+1

The Kalo ecosystem

Beyond compilation.

Products, open tools, and research around making system knowledge explicit, portable, and usable by humans and machines.

Product / Governed automationV

Scattered inputs → reviewable cases

Automate case operations. Keep expert decisions.

Velota prepares recurring cases from emails, forms, documents, and existing systems while keeping consequential decisions under human control.

  • Case operations
  • Human review
  • Evidence trails
  • Workflow validation
Explore Velota
Product / Open sourceDS

Development activity → durable intent

Stop losing the thread.

Local-first context for AI-assisted software development. Recover project intent, scope bounded work, preserve evidence, and hand work between humans and coding agents.

  • Local-first
  • No account
  • No LLM calls
  • No code upload
Explore DevSpecs
Tool / FreeADR

Architecture choices → durable rationale

Decisions that stay with the code.

No-sign-up tools and reference material for Architecture Decision Records. Generate canonical formats as ordinary Markdown and keep the rationale in your repository.

  • Plain Markdown
  • Nygard
  • MADR
  • Stateless API
Create an ADR
Research / Experiments underwaySL

Experience + outcomes → learned scoped rules

Learning rules from worlds.

Research into discovering predicates, contextual rules, and useful structure from events and outcomes—then testing what can safely transfer into another bounded context.

  • Symbolic rules
  • Outcome repair
  • Scoped transfer
  • Synthetic worlds
Explore ScopeLabs

These products, tools, and experiments share an architectural thesis; they are not presented as a fully integrated technical stack.

Technical preview

Configure the pipeline. Run the proof.

Kalo reads a project-local kalo.yaml that declares its stores, plugins, and named pipelines. Install the declared plugins, inspect the workflow, then run its compile pipeline.

macOS / Linux ↗Windows ↗Configure kalo.yaml ↗
project rootkalo.yaml required
# stores + plugins + compile pipeline configured
$ kalo install
$ kalo list
$ kalo compile
Available in the current ecosystemBrowse the GitHub organization ↗
SpecificationMorphe / KA:MO1

Versioned application data modelling.

RepresentationsYAML · Go · TS · PSQL

Canonical source and documented targets.

Selected pluginsGo structs · TS types · PSQL types

Real repositories, real generated artifacts.

Source of truth ≠ implementation of the moment

Own the specification.
Generate the implementation.

Explore Kalo on GitHub