Standards → implementations
Where are teams repeatedly translating standards, profiles, and schemas by hand?
This is what the shirt means
Polyglot code.
Zero lock-in.
Kalo is open-source infrastructure for transforming structured specifications across representations, systems, and technologies using portable compiler plugins.
Own the spec. Change the stack. Regenerate.
Demonstrated today in software development. Designed for domains where structured knowledge must be translated, validated, or projected into different forms.
STRUCTUREDSpecification
→TRANSFORMKalo
→TARGETRepresentations
Proven today / software developmentMorphe / YAML → Kalo → Go · TypeScript · PostgreSQL
Exploring next / at GDC26Standards mappings · validation · interoperability · semantic transformations
Brennan NunamakerFounder, Kalo Software · at GDC26 in Geneva
Why I'm here
Where portability meets implementation.
I'm at GDC to explore where reusable specification, transformation, and validation infrastructure can reduce repeated interoperability work across open standards.
Joining the data-portability conversation with the Vana and Linux Foundation communities.
Interoperability → infrastructure
Which mappings, validators, tests, and adapters should exist once?
Evidence → real workflows
What happens after trusted data reaches the relying party?
Kalo in 20 seconds
The contract stays. The projection changes.
Structured, versioned specification
Describe the durable thing independently of a target stack.
Portable WASM plugins + pipelines
Compose declared transformations across explicit format boundaries.
Ordinary Go, TypeScript, SQL, and schemas
Keep the generated artifacts as implementation assets in your project.
Current proof
Watch one source become three targets.
This is the real Kalo CLI compiling a Morphe YAML model across the stack.
Open source Inspect or extend the implementation.Portable plugins Transformations run as WASM.Explicit builds Versions, hashes, and lockfiles stay visible.
$ kalo compilereal CLI
Let's compare notes
We should probably talk if…
you're dealing with any of these problem shapes:
- Mappings between standards or profiles
- Repeated implementation glue
- Schema and specification evolution
- Conformance or validation tooling
- Generated bindings and adapters
- Relying-party workflow integration
Before the next session starts
Say hello now.
Go deeper later.
Adjacent tools + research
More from Kalo
Product / case operationsVelota
Prepare reviewable cases while experts retain the decision.
Explore Velota ↗Tool / local-firstDevSpecsContext and bounded work for coding agents.
Explore ↗Tool / Markdownadr.zonePortable architecture decisions that stay with the code.
Create an ADR ↗Research / experimentalScopeLabsLearning scoped rules and transferable world structure.
Read the notebook →