Attachments decide what an Agent can draw from. Direct attachments belong specifically to that Agent. Area attachments enter when the Area is active. Both remain references to shared organizational resources.
Direct attachment
Specific to one Agent.
- Always in that Agent’s composition
- Wins when the same Connector also comes from an Area
- Good for core identity and unique scope
- Changed from the Agent editor
Area attachment
Reusable and activation-aware.
- Shared by several Agents
- Present only while the Area is active
- Good for a coherent domain capability
- Changed from the Area
Attach Knowledge deliberately
Select the Areas needed for the Agent’s job, taken whole or narrowed to named Sources. A broad library scope can increase irrelevant retrieval and makes it harder to explain why a Source appeared.
Standards remain governed
An Area references a Standard rather than containing it, and referencing one makes it eligible, not universally readable. The active revision and Role visibility are checked when a person asks. An Agent answering the public does not use Standards at all.
Connectors add callable capability
An attached Connector exposes its available tools to the Agent, subject to Connector access and the policy of the door the question arrived on. Installation alone does not make every Connector callable by every Agent.
Review overlap
If a direct attachment and an Area provide the same content or Connector, simplify the composition where possible. Deliberate overlap is acceptable, but accidental duplication obscures ownership.