Scopes
Scopes are the structural boundaries that organize everything in matic: where primitives live on disk, what can see them, and how policy and context inherit downward. The four scopes, org, project, team, and agent, map directly to the filesystem hierarchy, making visibility and ownership inspectable with ls and enforceable through git. Understanding scopes is prerequisite to working with any other part of the system because scope determines what is visible in a given context and how inherited state flows downward.
Overview
Overview explains what scopes are, how the four-level hierarchy works, and the core principle that scope is structural, meaning visibility and inheritance, rather than operational, meaning routing and dispatch.
Org Scope
Org Scope covers the root operational context. Org-scoped primitives such as policies, library, routines, memory, and decisions are visible to every project, team, and agent within the org.
Project Scope
Project Scope describes a bounded, goal-directed body of work. Project-scoped primitives are visible to the team and agents engaged on that project but isolated from other projects in the org.
Team Scope
Team Scope explains a composition of agents assembled to execute a specific project. Teams are not standing organizational units; they form for a project and disband when it completes.
Agent Scope
Agent Scope defines the individual autonomous actor. Agent-scoped primitives such as probes, experience, memory, and work pile are private to that agent and not visible to peers.
Visibility and Inheritance
Visibility and Inheritance details how primitives inherit downward through the scope chain, org -> project -> team -> agent, which primitives exist at which scopes, and how read-only inheritance interacts with git-mediated mutation.
Groups and Routing
Groups and Routing shows how scope context and group membership combine to resolve which agent responds to a signal. Scope sets context, groups set the eligible responder pool, and response ownership is always singular.