At a Glance

Always-on

Personal hardware

8

Constitution Articles

4

Hook Pipeline Stages

The Idea

Most personal assistants are someone else's product running in someone else's cloud. Sora is the opposite — a runtime I own, hosted on my own server, with rules I wrote down and enforce in code.

The premise is simple: if one person is going to operate a fleet of services, papers, and devices alone, the assistant has to be sovereign by default — not a feature in someone else's roadmap.

Constitution (8 Articles)

Sora is governed by a written constitution before it is governed by prompts. The owner is sovereign; everything else is a delegation.

Art. 0

Owner Sovereignty. The operator's intent overrides any default behavior, model, or runtime policy.

Art. 1

Disclosure Bundle. Every action returns a structured bundle — what was done, why, what was skipped.

Art. 2

Side-Effect Budget. Tool calls declare their blast radius before they run.

Art. 3

Capability Tokens. Each subagent receives only the permissions it needs.

Art. 4

Dual Ledger. A progress ledger and a side-effect ledger run in parallel — Magentic-One style.

Art. 5

Uncertainty Gate. Below a confidence threshold, Sora asks rather than acts.

Art. 6

Device Tier. Sensitive actions degrade gracefully on shared or company hardware.

Art. 7

Reversibility First. Destructive operations require explicit confirmation, never inferred consent.

Architecture (4 Planes)

Runtime Plane

State machine, checkpoint, retry, rollback. Native Python venv on WSL2 (desktop-home), with Task Scheduler persistence.

Tool Plane

MCP-first gateway. Schema-validated tool calls, permission separation, audit log.

Agent Plane

Explicit handoff between specialists. No recursive multi-agent ping-pong.

UX Plane

AG-UI-style control plane — execution timeline, approval queue, owner override always visible.

Hook Pipeline

Four lifecycle hooks enforce the constitution before, during, and after each turn:

SessionStart — load SSOT, owner profile, current state.
UserPromptSubmit — classify intent, route to the right specialist.
PreToolUse — check capability token, evaluate side-effect budget, gate uncertain actions.
PostToolUse — append to dual ledger, update progress, sync shared brain.

Tech Stack

Python Pydantic FastAPI Redis WSL2 native Windows Task Scheduler MCP Gemini · Claude · Ollama (fallback chain) Telegram Bot Jarvis safety layer (warn-then-obey)