Company, blueprint and Pod
A company is the ownership boundary. Its blueprint records business facts, goals, processes, brand guidance, rules, permissions and selected knowledge. A Pod is created from that context for one objective. Each Pod records the company blueprint version used at creation.
Specialists and platform roles
Specialists have definitions for mission, inputs, outputs, tools and quality. Platform roles include Pod Manager, Workforce Orchestrator and Workforce Observer. Registry definitions are not proof of a connected model or tool; execution depends on the selected mode and available providers.
Tasks and controls
A Pod plan contains dependent tasks. Tasks may be planned, running, completed, blocked, rejected, cancelled or waiting for approval. Human-only and approval-controlled steps remain visible to the owner. A task may be revised with feedback and a new version.
Evidence and result
Selected company text chunks use semantic/keyword retrieval when embeddings are configured, with keyword fallback. The result records its mode and review state. Owners should verify claims, sources and assumptions before using an output externally.