An Area is a reusable capability bundle. It can provide additional instructions, Knowledge, Standards, and Connectors, with optional ownership by a responsibility Role. Agents select Areas instead of recreating the same scope repeatedly.
Area
A named capability with instructions and attached resources.
Agent
Selects the Area as additional scope.
Activation
Loads or removes the Area during work.
Give the Area a discoverable purpose
The description tells people and the Agent when the Area is useful. An Area with no meaningful description is effectively invisible to selection and planning. Use language based on the capability, not the first Agent that consumes it.
Bundle related material
Combine instructions and attachments that should become active together. Split unrelated scopes that have different owners or activation reasons.
Attach to several Agents
Reuse is the point: improvements to the Area can support every Agent that selects it. Review downstream behavior when changing high-use instructions or Connectors.
Ownership is not access
An optional owner helps stewardship. It does not replace the visibility on a Standard or the access grants required to edit Agents and Connectors.
Next: choose whether the Area is always on or activated when needed.