system-forgelisted

# System Forge ## Outcome Design a bounded system whose topology, authority, shared state, and proof obligations are visible before execution, then compile it when a Foundry runtime is present. ## Choose the smallest system shape - **Skill composition:** one actor can perform the work sequentially. - **Swarm:** independent or specialized workers need explicit coordination. - **Vertical:** domain rules, audiences, taste, and evaluation recur across several capabilities. - **Plugin:** a set of validated skills and optional MCP connectivity must be distributed to ChatGPT and Codex. Do not create a swarm merely to make a workflow sound advanced. Parallelism is justified only for genuinely separable work, independent evaluation, latency reduction, or permission isolation. ## Procedure 1. Start with a Task Envelope. - Include deliverables, stakes, autonomy, capability selection, permissions, required evidence lanes, and deployment targets. 2. Resolve capabilities. - Prefer registered skills and agents. - Treat lexical graph suggestions as discovery hints, never silent routing decisions. 3. Choose topology. - `manager-workers`: one owner decomposes and synthesizes. - `handoff`: ownership moves between specialists. - `agents-as-tools`: one agent retains control and invokes bounded specialists. - `parallel-merge`: separable outputs join under a deterministic merge. - `debate-synthesize`: independent hypotheses are judged and synthesized. 4. Define author