Operator Context

The problem: Founders live in assistants on phone and desktop, but portfolio state still lives in scattered SaaS tabs.

The wedge: A stable Operator API + MCP tools that expose read-mostly context (Focus bets, signals, decision queue) and write-only-through-approval actions (defer, approve, annotate lesson).

Non-goals: Autonomous sends, deploys, or policy changes from an assistant.

Depends on: TUR Company OS control plane, MeshGuard permission model, Signal Mesh ranked inputs.