We are building the operating model your software is missing.

Every business already has an operating model. It lives in people's heads, in onboarding docs, in a wiki nobody trusts and in the permission checks scattered through its code. DNA Codes exists to write that model down once, in a form both people and software can read, and then run on it.

What we build

DNA is an open description language for business systems. It captures who your business deals with and in what capacity, the things it manages, the operations it performs and the rules that govern them. The language, its schemas and its adapters are published on npm under the @dna-codes scope and developed in the open on GitHub.

Operations is the product built on it. At its core is Operational DNA: the living operating model every surface runs on. Around that core sit surfaces, one for each place your software meets somebody:

• UI Operations: operational controls inside your running app (early access)
• API Operations: who may call your endpoints, and what it records (in design)
• Agent Operations: your agents, under the rules you already wrote (in build)
• CLI Operations: the commands your team runs, governed like everything else (planned)

Why it matters now

The future of work is humans and agents working side by side. An agent given a broad API key has no idea which operations it is allowed to perform or whose authority it is acting under. A model that names every role, every operation and every rule gives agents the same job description and the same limits a person would have, and keeps a record of what each one did.

We write about the thinking behind this on the blog, starting with the series on the abstraction layers between intent and execution that today's software skips.

Where we are

Operations is pre-release. We are working with design partners whose work has nothing to do with software, which is the point: an operating model has to hold up in any domain. If that sounds like your team, join the waitlist or get in touch.