Operating control

Operate from verified project state.

Prepare bounded missions from project evidence, keep consequential actions human-controlled, and retain a trace that can be reviewed.

Workspace map: private operator only

3

projects

0

checked

0

connected

0

traces

Synthetic modePrivate project evidence is not connected in this mode.

Prepare a synthetic mission here, or connect the private operator locally.

Context graphWorkspace map: private operator only

Folders

Target: Student Product Studio

Private workspace unavailable in demo.

Context retrieval: not run yet

Hierarchy

SupervisorMemoryProductOps

LLM / hierarchy router: Understand the ask, choose context, delegate to specialists, and keep the final answer coherent.

LCM / context manager: Gather project, proof, review, and decision context before the assistant answers.

LAM / product action model: Turn vague ideas into user, wedge, workflow, metric, and proof.

LAM / tool runner: Plan terminal, deployment, database, environment, and verification actions.

Gates

Gates appear after the first route.

Latest run

Student Product Studio

Synthetic workspace only

Private operator only

No run yet. Ask the workspace brain to create the first context-backed route.

System truth and fine-tune queue

Brain attention

Mission intake

Protected actions

Model routing

Missing: Workspace map

Project registry

Canonical

One typed registry owns project identity, workspace authority, GitHub mapping, venture relationships, and client-pilot capacity.

Workspace inspection

Bounded read

Private mode reads registered roots only and caps folders, files, bytes, snippets, Git metadata, and execution time.

Workspace discovery

Live private

A shallow scan reconciles the configured workspace root with the registry and reports missing, outside-root, and unregistered projects plus activity heartbeats.

Knowledge vault

Read-only

Project notes, decisions, and lessons stay in the external private Markdown vault; Studio OS retrieves bounded metadata and excerpts without copying the vault into Git.

Semantic vault recall

Guarded local

The private RAG endpoint reconciles a local Ollama embedding index on every query, reuses unchanged vectors, and removes notes that left the vault; UI wiring is still pending.

Deployment evidence

Fresh read

Private mode reads deployment URLs from vault frontmatter and performs bounded HEAD-to-GET liveness probes; it has no deploy authority.

GitHub attention

Read-only

The organization adapter turns review, unassigned-issue, and stale-branch evidence into proposals. Comments, assignments, merges, and deletion remain human actions.

Command orchestrator

Guarded plan

One private route gathers the workspace map, selected scan, ranked snippets, linked vault metadata, risk gates, proof targets, and handoffs into a deterministic mission pack.

Verification runner

Allowlisted

Only declared npm typecheck, lint, test, and build scripts can run, after nested lifecycle scripts are inspected and credentials are removed from the subprocess environment.

Proof and trace memory

Local

Browser state records plans, proof, reviews, and run traces. Only human-reviewed useful or shipped traces can enter the explicit private JSONL export.

Fine-tune later

Saved runs are structured traces, not model training yet. Keep good prompts, context packs, routes, plans, and outcomes here first; later they can become evaluation and fine-tuning examples.

0

local trace examples in backup

0 retrieved file snippets saved for evals.

Operating focus

Set the focus, proof, and boundary for this work cycle.

Pick one focus before you open more rooms.

Today plan

Readiness

Unclear

2/6
Focusunset
Proofunset
Load2 active
Todayno plan
Inbox0 undecided
Reviewnot reviewed / 0/5

7

builders

2

active lanes

0

open

not reviewed

review

Capture

Empty. Capture only what deserves a lane.

Active operating lanes

Active work only. Everything else lives in Studio or Library.

All lanes and pressure map
Weekly operating review0/5 checks / not reviewed
Operating principles
  1. 1. Studio operating rhythm + a finish definition for every owned product
  2. 2. Opportunity Product Demo: Synthetic validation
  3. 3. 2/2 bounded client pilot slots; no third client

Now page: Keep a single current focus and a clear not-now boundary so new ideas do not steal the week.

Actionable projects: Organize around outcomes, owners, next proof, and deadline pressure instead of broad subjects.

Library, not buttons: Long context, venture details, proof, and raw notes live in the Library so the cockpit stays light.

Semantic zoom: Show one-line summaries first; unfold details only when a decision needs them.

Weekly review: Refresh the inbox, waiting list, venture next actions, proof, and cut list before adding more ambition.

Compounding memory: Archive lessons, proof, decisions, and contradictions so each week becomes easier to understand.