Vision

Browser Operating Environment

Omnacta Studio

The definitive browser-based environment for taking missions from described outcome to evidence-scoped acceptance. The Kernel and shared ledger remain authoritative.

Status: Vision and capability direction. This page describes the intended experience architecture. Implementation is in development.

← Product overviewRequest technical briefing

Authority architecture

Studio is a client surface, not a second orchestrator. The Omnacta Kernel owns mission transitions, execution, and authoritative state. Studio submits commands and receives events—it does not maintain a competing mission ledger.

  • The Kernel owns completion truth; Studio shows progress.
  • The Kernel owns intervention authority; Studio submits requests.
  • The Kernel owns evidence; Studio presents views.
  • Disconnection shows stale state; it does not advance mission progress.

Experience model

These capabilities represent the intended Studio experience architecture. Implementation follows the sequenced delivery roadmap.

  • Outcome Composer

    vision

    Describe what you want in natural language or structured contracts. Attach repositories, documents, data, constraints, and acceptance criteria.

    Conceptual interface—implementation in progress.

  • Mission Control

    vision

    Monitor live state, parallel workstreams, elapsed time, costs, risk indicators, and attention requests. See the authoritative mission ledger, not a client simulation.

    Conceptual interface—implementation in progress.

  • Context Inspector

    vision

    Explore what Omnacta selected, excluded, summarized, and cached. Pin, correct, or constrain context without rewriting history.

    Conceptual interface—implementation in progress.

  • Environment Views

    vision

    Governed views into shells, browsers, and tools. When supported, take over for direct control with explicit authority handoff.

    Conceptual interface—implementation in progress.

  • Intervention Ladder

    vision

    Redirect, pause, constrain, sandbox, or terminate through Kernel-owned authority. Every intervention is recorded and attributable.

    Conceptual interface—implementation in progress.

  • Evidence & Acceptance

    vision

    Review deliverables, supporting evidence, and acceptance criteria. Accept, reject, or request repair through versioned commands.

    Conceptual interface—implementation in progress.

Cross-surface continuity

The same mission identity and authority model spans every Omnicta surface. Start in Studio, continue in CLI, automate via API—without losing context or state.

SurfacePrimary strength
Web StudioFull mission and acceptance state
DesktopLocal resources, native notifications
CLIPrecision, scripting, automation
API / SDKEmbedding and programmatic orchestration
EditorCode proximity and focused changes
AutomationScheduled and event-triggered missions

Asynchronous execution

Missions outlive browser tabs, network connections, and individual operators. Studio provides supervision and notification; the Kernel ensures durable execution.

  • Durable server-side checkpoints — Mission state persists beyond client lifetime.
  • Version-checked commands — Idempotent, conflict-detected operations.
  • Reconnect and resume — Pick up from event cursor without state loss.
  • Notification and escalation — Attention requests reach you where you work.

Experience the vision

Request a technical briefing on the Studio vision, authority boundaries, and planned delivery sequence. Studio is not currently available.

Request technical briefing