17
DraftS05-CON-010v0.1Source imported
Section 25 of 102
24. Agent Context Architecture
Stable section ID: S05-CON-010-SECTION-25 · 21 content blocks
Agent Context Architecture defines the information that an agent may use to understand its current task and operational environment.
Context may include:
- User request.
- Agent role.
- Current project or building.
- Applicable BDL configuration.
- Building BIOS state.
- Digital Twin observations.
- Lifecycle phase.
- Current event and alarm state.
- Applicable codes and Engineering Profiles.
- Tool availability.
- Active permissions.
- Prior approved decisions.
- Environmental and occupancy conditions.
- Time and location.
- Unresolved risks.
- Required approvals.
Context shall be scoped to the task and authority of the agent. Access to one project, building, tenant, or subsystem shall not imply access to another.
The agent shall distinguish authoritative context from advisory information, inferred information, temporary working data, and unverified external content.
Material context changes shall trigger re-evaluation of plans and permissions. An action approved under one condition shall not automatically remain approved after the underlying context has materially changed.