You are looking at a fresh install. The charter is seeded; the archive and creed are yours to fill. Your first move →

ORDOVA

ORDOVA

An AI operating system with a constitution.

Ordova is the operating system a software studio runs its AI workforce on. A constitution, an enforcement layer, and a permanent record. Built and run in production at Async Digital.

The philosophy

Let nothing be destroyed that cannot be recovered. Let nothing be claimed that was not verified. Let the record outlive the session, and the law outlive the day’s convenience. What drifts from the truth is corrected at its source, never papered over.

The drift barrier

The law is enforced

Derived views drift silently while reading confidently. Ordova halts the irreversible moment instead.

drift gate
terminal replay

The same halt, read room by room

The rule · charter

Derived views must not drift from what they derive from. The rule the gate enforced is written law, filed in the canon.

 The gate · executive

The check that refused to proceed is enforcement machinery, wired to the session’s wrap-up boundary.

 The record · archive

The handoff the session was not allowed to write belongs to the records room, and it waits until the drift is resolved.

The rooms

Room I · the constitutional room

Canon

the law

The law the gate enforces and the record is kept against.

Exhibit · the derived-view pipeline

markdown canon, the law, prose
The render step emits content, never markup.
JSON content model, stamped with a hash of its source
template The build is deterministic: no judgment, no drift.
HTML the published face
re-hash on every build: stale pages cannot hide
Enter

Room II · the blueprint room

Executor

the enforcement

The machinery that holds each session to the law.

Exhibit · three tiers of drift enforcement

each layer catching what the one below cannot see

Tier 3 Gated

Checks run at moments of consequence (merge, deploy, session wrap-up) and refuse to proceed past findings.

Tier 2 Computed

Hashes recomputed against sources. Declarations can go stale; a hash comparison cannot lie.

Tier 1 Declared

The artefact carries its own claims. Markers in frontmatter: what it derives from, when it was last verified, when to look again.

Enter

Room III · the records room

Archive

the record

The record each session must leave behind.

Exhibit · the markers a record carries

---
review-by: when this record demands attention again
status: active, parked, complete, archived
derived_from:
derived_hash: what this view was generated from, and the fingerprint that betrays silent change
invalidated: this view is known to be false, and here is why, until it is regenerated
concurrency_class: only one writer may mutate this tree at a time
---
[ Enter ]

Rooms IV and V · sealed

Room IV

creed

the personal layer

Private

Room V

interface

the MCP surface

Shelved