YOU

Architecture of system

How you-agent-factory is structured: factory topology, work, workstations, workers, resources, and live FactorySession runtime.

System Diagram

The diagram below shows how work moves through a live session: submitted work enters the Factory Session, a workstation dispatches to a worker, an optional resource can bound capacity, and the outcome routes back into work states.

How work moves through you-agent-factory

  • Session / work flow
  • Worker dispatch / outcome
  • Optional resource bound
Submitted work enters a live Factory Session. A workstation dispatches to a worker, may hold an optional resource bound, and routes the outcome back into work states.

How To Use

Use Architecture of system for the system-structure map: how factory topology, work, workstations, workers, resources, and Factory Session fit together. Open Configuration when you need factory.json topology fields. Open Workers, Workstations, or Resources when you need deep contracts for those nouns. Open What is you-agent-factory when you need product framing before system structure. Factory Session, dynamic workflows, and Petri framing belong on their own documentation surfaces when you need live-runtime, JavaScript orchestrator, or CPN depth beyond the system-structure map.

Limits And Assumptions

Architecture of system stays at the system-structure overview. It is not a field dump, not a sync of packaged CLI docs, and not a deep dive into MCP, API, logs, or metrics surfaces. Sibling field-reference and runtime pages own those contracts when they are published.

Tags

On this page

System DiagramHow To UseLimits And AssumptionsTags