Export GIF Settings

60 frames · 20 fps · 3s

Plato Product 1.1 Architecture

Router-first input, fixed execution lane, durable activity and audit evidence

Product control plane Execution plane Trust plane User goal / question / answer Main Page UI conversation + details Electron Sidecar local FastAPI runtime Input Router classify + dispatch Read-only Inquiry answer without mutation Contract Commands ASK / guidance / handoff Authoring Domain RawTask to DraftTree Task Publisher publish immutable work TaskBus single writer lane Default Agent task-scoped execution Workspace Root files + process effects Conversation durable activity replay Audit Evidence diagnostics + inspection LLM Roles provider config Web Retrieval search / fetch evidence input local API runtime input service call question mutation intent draft / facts publish PublishedTask claim task tools / files result / ask bounded evidence retrieval tools router LLM agent LLM decision log execution evidence inspection Legend External Frontend Backend Cloud Message bus Database Security

Input discipline

  • • Main Page input always reaches the Runtime Input Router first.
  • • The router chooses read-only inquiry, contract command, ASK resolution, confirmation, or execution handoff.
  • • User language is durable conversation content before it becomes product or execution state.

Execution boundary

  • • PublishedTask is the execution authority.
  • • TaskBus keeps one active writer lane for workspace effects.
  • • Product 1.1 still uses a fixed Default Agent execution route.

Trust and evidence

  • • Conversation, Activity, Audit, Diagnostics, and Workspace Inspection are first-class projections.
  • • Read-only answers and execution results are replayable and inspectable.
  • • LLM role configuration stays backend-only for now, preserving product simplicity.