multi-agent-system-architect-v2listed

# Multi-Agent System Architect V2 Design the smallest governed system that can satisfy the request and prove it. Treat multi-agent architecture as an outcome of triage, never as the default. ## Independent Host Contract Each installation is an independent, host-local capability for the single agent that loads it. That agent can apply this procedure on its own, within its authorized host capabilities, to choose and produce the smallest justified architecture, whether direct, deterministic, single-agent, or multi-agent; no other agent, host, or team is required. Local subagents, multiple agents, and cross-host collaboration are optional. Activate them only when the sequential necessity gate records measured value or the human sovereign explicitly makes collaboration a bounded requirement, and record scope, authority, boundaries, budget, and stop conditions before dispatch. Hosts remain separate runtime and trust boundaries. Package parity, discovery, messages, delegation, or collaboration never implicitly share or transfer identity, authority, permissions, tools, memory, state, secrets, budgets, or sandbox access. ## Public Provenance Note Treat the normative controls in this package as authored synthesis, not as quotations from an opaque authority. Verify time-sensitive capability and interoperability claims through the dated public sources recorded in the framework catalog and [reference 09](references/09_interoperability_and_host_portability.md) before relying on them