PUBLIC BETA / ORDOLOCAL-FIRST · RUST/TOKIO · DESKTOP UXI

YOUR AI
OPERATIONS
CENTER.

Ordo puts providers, tools, agent teams, memory, retrieval, and automation behind one operator-controlled interface—on your machine.

CURRENT PUBLIC BETAFuture editions stay unpublished until ready.

PRODUCTORDO BETA

RUNTIMEONE LOCAL RUST PROCESS

DESKTOPTAURI · WEBVIEW2 / WEBKITGTK

CONTROLEXPLICIT OPERATOR APPROVAL

CLICK-THROUGH PRODUCT TOUR

Every surface.
One control room.

Explore the current Ordo interface map—from Provider and Assistant through agent rigging, knowledge, security, runtime, and settings. This is an interactive product tour; it does not run local Ordo tools in the webpage.

Daily controlSELECTED SURFACE / 02

LOCAL-FIRST · OPERATOR VISIBLE

ORDO TAB

Assistant

Run the operator conversation with mode, model, tools, and approvals kept visible.

01Streaming turns

02Session controls

03Artifact handoff

OPERATOR INTENTASSISTANTCAPABILITY / POLICYRESULT + AUDIT

WHAT ORDO IS

A private AI
control room.

Local-first does not mean local-only. Ordo can use local and cloud providers, but the model never receives uncontrolled computer access and secrets stay outside model-visible state.

Provider Gateway

Local models and OpenAI-compatible providers enter through one adapter boundary with explicit fallback profiles. This is a provider gateway, not a central replacement for the bus.

The Strainer

Raw web content never reaches the model. Deterministic, intentionally lossy transforms remove structural tricks, normalize text, and wrap what survives as untrusted data.

Mode learning trees

Every mode declares its own memory scope and RAG domains. Learning reinforces chunks and collection routing only inside the active mode’s allowed knowledge boundary.

Cross-mode computation

When one mode needs another domain, Ordo starts a bounded target-mode agent and returns only its answer—never that mode’s private RAG or raw memory.

Secrets custody

Models see short-lived capability handles, not raw keys. Sealed storage, zeroizing buffers, canaries, provider scopes, rotation, revocation, and audit own the material.

Research-derived MCP security

Signed lockfiles, trust graduation, drift re-authorization, quarantine, Wasmtime isolation, extraction workers, taint provenance, and operator review compose one path.

Modes + Agent Teams

Instructions, tools, skills, memory, model choice, and budgets scope to the job. Agent teams split bounded work across visible roles with depth and spend limits.

Planner-first execution

Models propose bounded steps; capability gates, hooks, policy, workspace scope, and review decide what may become a real tool call or state change.

Layered memory

Pinned truths, working memory, event history, mode-private facts, and self-learning retrieval remain distinct instead of collapsing into one global context pile.

Automation + review

Hooks, cron, routines, heartbeats, webhooks, and dreaming proposals remain logged, interruptible, and approval-gated where risk demands it.

Tech Specialist

A local diagnostic mode manages providers, integrations, skills, MCPs, and approved maintenance while keeping core security changes behind engineering review.

Direct-first connections

App and device paths prefer direct local communication, then NAT traversal, then cloud relay fallback. Trust establishment stays separate from provider access.

MODE-ISOLATED INTELLIGENCE

Separate trees.
Shared expertise.

Ordo does not create intelligence by mixing every memory together. Each mode learns inside its own tree, then crosses domains through a bounded computation rather than a context leak.

GENERALmode:generalgeneral_notes

RUST VIBE CODERmode:rust_vibe_coderresearch_rust · rust_patterns

RESEARCHmode:researchresearch_general · research_notes

SECURITY LABmode:security_labexploit_notes · binary_analysis

CROSS-MODE COMPUTATION

CONSULT.
DO NOT
BORROW.

The active mode sends a question and reason to a bounded target-mode agent. Depth, policy, taint, and capability lanes follow the consultation. Only the answer returns.

ACTIVE MODE→TARGET AGENT→BOUNDED ANSWER

DEFAULT RETRIEVALBM25 + FUZZY VOCABULARY + PPMI EXPANSIONSELF-LEARNING SIGNALSCHUNK REINFORCEMENT + COLLECTION ROUTINGOPTIONAL CHANNELEMBEDDINGS WITHOUT BECOMING A HARD DEPENDENCY

SECURITY AS COMPOSED MECHANISMS

Untrusted in.
Bounded out.

No single classifier carries the system. Deterministic transformation, capability narrowing, causal provenance, isolation, secret custody, and operator review each own one part of the boundary.

THE STRAINER / WEB + EXTERNAL CONTENT

A coffee strainer,
not an injectable detector.

Main-content extraction, hidden-content removal, Unicode normalization, Markdown reduction, and mandatory untrusted boundary tags destroy structural tricks before any intelligent layer reads the page.

RAW PAGE→STRAINER→CUP→GROUNDING FLOOR→MODEL CONTEXT

01 / SECRETS VAULT

Raw keys never become context.

The vault seals material under the strongest available platform tier. Plaintext lives only in zeroizing SecureBytes; rotation retires and overwrites old ciphertext.

TPM / TBSSECURE ENCLAVEOS KEYCHAINARGON2 FALLBACK · REPORTED

02 / SECRETS BROKER

Capabilities stand in for secrets.

Short-lived handles, invocation custody, unique canaries, provider scope, one-shot dereference, revocation, and output scans keep the model and ordinary tools away from reusable material.

HANDLECANARYDRIFT CHECKREVOKE

03 / MCP RESEARCH STACK

Trust must graduate.

Installed servers enter through signed identity, declared capabilities, explicit trust states, drift checks, quarantine, filesystem and egress policy, deterministic extraction, and causal taint review.

REGISTRYWASMTIME SANDBOXWORKERPROVENANCE

UNTRUSTED MCPSIGNED LOCKFILETRUST STATESANDBOXWORKER EXTRACTIONCAUSAL PROVENANCEPOLICY / OPERATOR

GATEWAY WITHOUT FLATTENING THE BUS

One provider edge.
Many fabric paths.

The provider Gateway prevents vendor calls from scattering through Ordo. It does not centralize every message: typed subsystem traffic still moves on the bus, and device connections keep their direct-first path.

MODEL / PROVIDER EDGELOCAL MODEL→PROVIDER GATEWAY→OPENAI-COMPATIBLE→EXPLICIT FALLBACK PROFILE

APP / DEVICE EDGEDIRECT LOCAL→P2P→NAT TRAVERSAL→CLOUD RELAY FALLBACK

INTERNAL FABRICCAPABILITY REQUEST→ORDO BUS→PEER→REVIEW / RESULT

CURRENT OPERATOR UXI

Control stays
visible.

These are current screenshots from the Ordo beta—not concept mockups.

Ordo settings surface showing its operator controls — 01 / Studio control surfaces

Ordo mode management interface — 02 / Mode-scoped behavior

Ordo automation interface — 03 / Bounded automation

SPIDERWEB LINEAGE / CURRENT SOURCE

The bus is
the boundary.

Ordo’s Rust crates communicate through typed envelopes on an in-process bus. That is the active local-street layer of the Spiderweb architecture: a shared protocol surface instead of hidden cross-component state.

The complete elevated fabric—emergent threads, intersections, on-ramps, off-ramps, preloading, and vibration-driven routing—remains the broader architecture direction and is not presented here as fully implemented.

PROVIDERS→CAPABILITY GATES→ORDO BUS→PEERS→OPERATOR REVIEW

FRESH VALIDATION / CURRENT CHECKOUT

Beta, with the boundary visible.

PASS Core Rust crates compile
PASS Runtime smoke test
PASS Studio production build
PASS Full runtime harness
OPEN Formatting check

Ordo works and is actively developed. This page covers the current beta only and does not turn one remaining formatting gate into a runtime failure.

ORDO / PUBLIC BETA

Give the model tools. Keep the operator in control.

View Ordo on GitHub ↗Return to Atom ↗