Introduction

Why MIXT?

We've spent years delivering complex programmes and have seen how unnecessary complexity slows teams down. Glue code sprawls, specs drift from implementations, and documentation goes stale. MIXT exists to remove that friction.

The pain we keep seeing:

• YAML/JSON pipeline sprawl with fragile handoffs
• Specs and code diverge; docs rot
• XSLT/jq power, but sharp edges (quoting, error messages, testability)
• Inconsistent schemas; unclear validation
• Non-deterministic builds that are hard to reproduce

What is MIXT?

A practical, schema-first language that makes transformation explicit, testable, and repeatable.

Core pillars:

• Schema-first: strict, explicit types with metadata and validations
• Deterministic builds: same inputs → same outputs, across environments
• Executable specs: rules and tests live alongside transformations
• Multi-output publishing: website, PDF, and DOCX from one source
• Clarity & performance: designed to be readable, fast, and auditable

How MIXT helps delivery

Model first, then implement. Encode the rules once, generate consistent outputs, and keep teams aligned with executable specifications and living documentation.

• Fewer moving parts; less glue code
• Clear errors with precise context
• Reproducible builds that survive audits
• Shared source of truth for data, transforms, and docs

Status

MIXT is in active development. We're dogfooding it in our own projects, refining the language and the toolchain. When we're confident it's ready, we'll invite others to share the benefits.

Register interest See Delivered Outcomes