← חזרה לכל השלבים

Orion Studio — Vision (P5, stage: VISION)

PRISM product #5. Gate: APPROVED by Ben (Creative Director), 2026-06-13, with three
locks (§ Locks). Owner: vision agent. Upstream: brief.md, research/research.md.
Downstream: BRAND (visual language; divergence enforced). This document is executable (P3):
if implementation differs from this Vision, the implementation is wrong.

North star

One calm cockpit over the whole machine. Sit down, and in one glance know the truth of

both layers — Orion running, PRISM building — then reach out and act, without ever leaving

the seat or SSH-ing anywhere.

The metaphor — glass cockpit, not IDE

A glass cockpit: not a passive dashboard, and deliberately not an IDE. Dashboards only

report; IDEs are for editing files. Orion Studio is for flying two living systems — live

instruments (runs, costs, stages, gates) plus direct controls (terminal, approvals, submit) on

one surface. The cockpit's discipline is calm under density: a hundred readouts, but you

feel in command, not flooded.

Reframe (deliberate, Lock 3): the brief.md framing of "IDE" is retired. The Studio is a
glass cockpit. It never becomes a code editor — see Lock 1.

Who it's for

Ben, the operator — honestly, today. Built for the real workflow of one person, not a

hypothetical crowd. But every boundary that would differ for a second operator — auth,

identity, what's exposed — is built as a seam, so a future teammate or OSS self-hoster

slots in without a rebuild. Design for one; leave the door open; never dilute for ghosts.

The two halves (P10, made visible in one frame)

cards, cost/token rings); HITL gates that light up only when they need you; replay; and a

VPS terminal right in the seat (ttyd over Tailscale — no open ports). Sherlock's truth,

surfaced — never recomputed.

Vision/Brand gates awaiting approval; the memory brain browsable (patterns / evaluations

/ playbooks); and — Create tier — submit a PrismTask into Orion.

Emotional goal → design law

The emotional target is calm command. It is not a mood; it is enforceable law (these become

EVALUATE criteria):

  1. The UI never computes status. It reads Orion's stores (Postgres + Directus). What you

see is true because it is Orion's truth. Trust is the feature, not a side effect.

  1. One drama per scene (inherits memory/evaluations/quiet-not-flat + brand-isolation):

the live run is the hero; chrome recedes; ≤1 accent/alert per viewport unless something

genuinely needs your hand.

  1. Nothing on fire silently. Failures and gates surface calmly but unmissably. Calm ≠ hiding.
    1. Everything within reach (bounded — Lock 1): the four verbs are **observe · terminal ·

    approve · submit**. Leaving the seat — SSH, psql, a second tab — is a Vision failure. The

    terminal is the deliberate catch-all escape hatch: anything not modeled as a first-class

    control (e.g. editing a file) is done in the shell. The Studio does not grow a code editor.

    Positioning

    intimacy — it speaks Klaus steps, PrismTasks, pipeline stages, gates, and reads the

    actual stores. Generic tools cannot.

    Grafana board. We study them, embed where smart (ttyd for the terminal), and build only

    the thin Orion+PRISM glue.

    or foodflow (warm / teal). A tool identity — its own dark, instrument-grade language.

    BRAND decides the specifics; divergence is a gate, not a preference.

    Scope ladder — aligned to First Light's four tiers

    First Light (orion-os) defines Orion Studio as four measured-trigger tiers:

    Observe (tier 1) → Review (tier 2) → Replay (tier 3) → Create/manage (tier 4).

    hatch; it is not one of the four tiers — it is the floor beneath them.

    v1 as a felt experience

    Open Studio (localhost, or remote via passkey + Tailscale) → **see every live run and the state

    of every product in seconds, zero commands → drop into the VPS terminal** in the same frame

    when you need the shell. That is the whole of v1. Acting (approve / replay / submit) arrives only

    when its trigger fires.

    Success metrics (so EVALUATE can gate it)

    terminal commands.**

    (no separate SSH / psql / browser tab).

    computed status, ever.

    rule; automatable check).

    Caddy TLS + passkey + ttyd auth — defense in depth).

    Non-negotiables

    on Ben's word.

    Observe panel displays and exposes the Observe API the cockpit reads.

    Locks (Ben, at the VISION gate — 2026-06-13)

    1. "Within reach" is bounded to observe / terminal / approve / submit. **Not a file-editing

    IDE.** The terminal is the catch-all escape hatch.

    1. v1 = Observe (tier 1) + Terminal only. Approvals (Review / tier 2) and submit-PrismTask

    (Create / tier 4) are trigger-gated fast-follows; tier labels align to the First Light

    four-tier doc.

    1. Deliberate reframe from "IDE" → "glass cockpit" — confirmed and intentional.

    Open questions handed to BRAND

    marketing surface. (Divergence from portfolio/foodflow is a hard gate.)

    Source / precedent