Runtime
The runtime around the agents
Diskarte is a constitutional operating environment in which an organization’s commitments, work, and knowledge are governed — and through which it can safely delegate increasing autonomy to AI.
Agents and models operate inside it. The product is everything around them: organizational context, authority, memory, judgment, governance, delegation, and execution.
Anatomy
One seam in, one owner per truth
Every surface speaks to the Runtime through a single Platform API. Nothing reaches the kernel, storage, or cognition directly.
Desktop — custody
ImplementedThe native host. It owns exactly one truth: what is on this disk. It runs the claim ceremony, holds credentials in the keychain, and composes pinned runtime and UI artifacts — failing closed on mismatch.
Platform API — the seam
ImplementedThe single entrance, contract-typed at every boundary. It holds no governance logic of its own.
Kernel — authority
ImplementedSeven primitives. Authority is computed as Role ∩ Boundary at the moment of authorization, never stored. It governs; it never reasons.
Governance — the one door
ImplementedIntake → Proposal → adjudication → promotion. Machine advice and human intent enter through the same door and are judged by the same pipeline. Batch-accept does not exist.
Memory — two planes
ImplementedCanonical memory is the system of record; retrieval memory is derived acceleration, rebuildable at any time. Collapsing them is prohibited.
Judgment — rulings
ImplementedDeterministic standings over candidate beliefs, with confidence-inflation and circular-evidence defenses. Humans rule; the interface never pre-selects.
Cognition — the interior
ImplementedProduce and Judge behind one port. Structurally barred — by import guards, not policy — from storage, authority, identity, and lifecycle.
Substrate — where FLOPs run
ImplementedAbstract requirements, governed bindings, five deployment profiles. Model identity travels only as provenance on produced work.
Operations Platform — outside
Deployed · Internal DevHow Diskarte-the-company provisions, releases, and operates deployments. Structurally incapable of holding authority inside any organization.
Every truth has exactly one owner.
What a layer cannot enforce, it may only reflect — visibly labeled as a reflection.
Boundaries
Every truth has exactly one owner
| Layer | Owns | Must never absorb |
|---|---|---|
| Kernel | authority decisions, invariants | reasoning, substrate names |
| Runtime governance | canon, membership, policies, bindings | anything a model asserted but no human ratified |
| Cognition | proposals, evaluations, learning | authority, canon writes, credentials |
| Desktop | custody — what is on this disk | server truths; it reflects them, labeled |
| Operations Platform | setup codes, installations, releases, appliances | constitutional authority in any organization |
| Identity provider | the external identity itself | any decision about what it may do |
| Substrate layer | providers, resources, health | knowledge — a provider swap never mutates a Practice |
| Nobody | “ceremony complete”, “ready to execute” — derived by asking each plane | a stored composite; there is no orchestrator of record |
Execution
Accountable execution
Every machine-produced artifact durably records what produced it and what judged it — model, provider kind, resource, grounding — as evidence attached to the work, never as a gate. Requests address capabilities, never models; the schema refuses vendor names inside the constitution.
Build with us.
Apply to become a design partner and help shape the runtime against real organizational needs.
Alpha signup opens shortly.
The list is not accepting submissions yet. We would rather show you nothing than a form that quietly drops your address.