Ordova is the AI operating system we developed at Async Digital and use to run our work. It turns the working context an agent needs, our rules, our memory, and our tools, into a system we own and carry from project to project.
The context that makes an agent useful, how we work, what we have decided, and the tools we have built, is a new kind of professional capital. Left alone it leaks. It scatters across a chat history here and a config file there, and it resets every time the model, the agent, or the tooling changes.
Ordova is how we keep it. It holds our rules, our memory, and our tools as first-class artefacts we own, so the work compounds instead of draining away.
Ordova is a small system of components, each with a clear role. Together they work like a separation of powers: we legislate, the rules are enforced, the work is recorded, and one layer is specific to the operator.
The methodology we hold. Principles, invariants, and the discipline we work by.
The live config the agent runs under. It puts the charter into practice.
The memory. Handoffs, projects, and the work as it happens.
The one operator-specific layer.
Ordova does not run on someone else's rules. It runs under the rules we write, and enforces them consistently. The opinion it holds is about structure, not content: keep methodology, memory, and tools as first-class, portable artefacts, and they travel with us across agents, machines, and roles.
A thought, a link, a photo, a voice note. Save it into a synced folder from anywhere, and at the next session it is waiting in the inbox. One command classifies it and writes it up, ready for you to say where it lives. The capture takes a second, the command is one line, and neither is on the path of whatever you actually sat down to do.
How the shared, official layer and the operator-specific layer fit together.
Every skill the agent reaches for, each tagged with its home.
How we hold drift-prone pairs shut, from eliminating duplication down to convention.
How a hand-written page is held to its source, so drift surfaces instead of hiding.
How a session runs start to finish: finalise the last one, work, checkpoint, wrap up.
How many sessions run at once on one machine without corrupting shared state.
How a specialist reviewer and a project-lead gate compose within one piece of work.
A one-line status signal, spoken aloud, that reaches you when you look away.
The thinking behind charter, executive, archive, creed, and the name Ordova.