RuntimeLive endpoint
OMOS Runtime
Health, manifest, provider discovery, Council orchestration, governed run records, human disposition, and persistence status are exposed through the shared runtime API.
OMOS UI v2 · Operational Workspace
From question to auditable decision.
Run one difficult question through governed input, Layer 1 distillation, alignment, multi-model Council Review, synthesis, human authorization, a persistent Decision Record, and retrievable history.
Layer 1Distillation
Preserve signal, isolate noise
OMOS identifies the objective, constraints, ambiguity, evidence and quarantined instructions before model orchestration begins.
Test Layer 1 →AlignmentDecision support
Inspect alignment state
Truth, clarity, coherence, dignity, constructive unity, evidence support, verifiability and execution readiness remain visible as separate signals.
Run Alignment →Council4 provider interfaces
Cross-model review
Independent outputs are followed by cross-review. Agreement, contradiction, missing evidence and novel insight are preserved separately from factual verification.
Run Council →SynthesisHuman review required
Governed OHI synthesis
OMOS prepares a structured result without erasing uncertainty or dissent. Human approval or rejection remains required before final record disposition.
Start Run →RecordAuditable
Commit the Decision Record
The record retains normalized input, provider outputs, reviews, synthesis state, verification state, hashes, timestamps, persistence metadata, and human disposition.
The human gate is enforced inside the Record transition. Durable restart-safe persistence depends on the production PostgreSQL backend reporting durable=true.
HistoryRun records
Reopen the reasoning trail
Recent server run records can be reopened through the authenticated Council APIs and directly inside Ask OMOS.
GET /api/v1/council/runs
Canonical product sequence
INPUT → LAYER 1 → ALIGN → COUNCIL → SYNTHESIZE → RECORD → HISTORY
The visible product rail is intentionally simpler than the internal governance machinery. Human approval/rejection remains mandatory inside the Record transition.
1InputCapture the difficult question and explicit context.
2Layer 1Classify objective, constraints, evidence, ambiguity and quarantined instructions.
3AlignEvaluate decision-support dimensions and hard gates.
4CouncilCollect independent outputs and cross-model critiques.
5SynthesizeProduce governed OHI output while preserving uncertainty and dissent.
6RecordHuman approve/reject occurs here, then the Decision Record is committed.
7HistoryReopen, inspect and audit prior runs.