SYSTEM ARCHITECTURE

One system.
Several authority tiers.

Yana separates intelligence, authority, execution, continuity, evidence and interface into independent planes joined by explicit contracts.

See the full stackSee governance
01 · Human surfacesStudio · Terminal · Web · Discord
02 · Giám Thịroot safety authority
03 · Yana control planepolicy · task · memory
04 · Rust TurnEnginetyped turn · stream · cancel
05 · Model + Capabilitylocal/cloud · governed tools
06 · Evidencereceipt · audit · Git

THE STACK

The model is just one replaceable component.

Authority and system state live outside the model, so switching provider or agent never costs you the boundary.

Intelligence plane

Local and cloud providers share one authority model; the newer provider gateway isn't yet the dispatch path for every call.

OpenAI · Anthropic Groq · Gemini Ollama · local

Execution plane

The Rust TurnEngine manages typed turns, streaming, cancellation and canonical capability.

turn → stream → tool loop → cancel → partial output

Authority plane

Giám Thị, YanaAuthorityChain, approval, leases and HALT keep authority outside inference.

human ↓ Giám Thị ↓ Yana control plane

SYSTEM MAP

One control plane.
Several surfaces, not equally powerful.

The human keeps the final decision. Giám Thị is the root safety authority — it can HALT the entire session when it detects an unreviewed change. Studio and the Runtime CLI go through the same Yana control plane into the Rust TurnEngine (yana-rt); Wheelbot is a separate hardware branch with its own WebSocket/MCP device bridge — this site does not claim Wheelbot's path has been verified end-to-end through the same TurnEngine.

See Yana Runtime →
Humanfinal authority
↓
Giám Thịroot safety · fail-closed HALT
↓
Yana control planepolicy · identity · evidence · capability
↓
Rust TurnEngine (yana-rt)stream · cancel · tool loop
↓
Model + provider planeAnthropic · OpenAI · Gemini · Groq · DeepSeek · OpenRouter · Ollama
Canonical capabilityfile · Git · command (shell/process) · system, manifest-scoped
↓
Audit chainhash-chained per tool call, tamper-detectable
Evidence receiptHMAC-signed execution result (Truth Gate)
↓
Studio · Runtime CLIsame TurnEngine, verified
Wheelbotown device bridge — not verified end-to-end

CONTROL + CONTINUITY

Work outlives a single transcript.

Task graph, missions, L1/L2 memory and project memory create durable state; a complete Continuity Engine is still roadmap.

See Continuity
Task graphlive
Missionslive · maturity evolving
L1 / L2 memorylive
Continuity Engineroadmap

CAPABILITY + EVIDENCE

A real action leaves a receipt.

Manifest lookup, risk, approval, atomic file write, TOCTOU re-diff and the audit chain turn a tool call into a verifiable action.

See Governance
Proposalmodel
Decisionauthority
Executioncapability
Evidencereceipt + artifact

INTERFACE BOUNDARIES

Every interface carries a different level of authority.

Yana doesn't assume every harness is equally capable.

Terminal

The only chat path with approval-continuation for mutating capability today.

interactive approval continuation mutating capability

Studio + Packaged Web

Uses the headless stdin/NDJSON contract; headless mode doesn't expose mutation capability today.

typed turn local process no headless mutation

MCP + Adapters

MCP is opt-in and doesn't create approval on its own; harness adapters enforce it unevenly.

MCP experimental approval external adapters unequal

DEEPEST PRINCIPLE

Intelligence can change.
Authority must hold.

That's why Yana is a control plane and a personal agent operating system, not just a model wrapper.