aa-gateway 0.0.1-beta.4

Control plane — policy enforcement engine and agent registry for Agent Assembly
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24

/// Agent lineage resolved from the registry for scope-chain walking.
///
/// `org_id` and `team_id` mirror the metadata keys that the lifecycle
/// service writes at registration time (keys `"org_id"` and `"team_id"`).
///
/// AAASM-3377 — the delegation fields (`root_agent_id`, `parent_agent_id`,
/// `depth`, `delegation_reason`, `spawned_by_tool`) mirror the first-class
/// fields on `AgentRecord` so audit entries carry the full lineage instead
/// of only the `org_id` / `team_id` scope pair.
#[derive(Debug, Clone, Default)]
pub struct Lineage {
    pub org_id: Option<String>,
    pub team_id: Option<String>,
    /// Root agent identifier at the top of the delegation chain.
    pub root_agent_id: Option<[u8; 16]>,
    /// Identifier of the agent that directly spawned this agent.
    pub parent_agent_id: Option<[u8; 16]>,
    /// Delegation depth from the root agent (`0` = root).
    pub depth: Option<u32>,
    /// Human-readable reason the action was delegated to this agent.
    pub delegation_reason: Option<String>,
    /// Name of the tool or framework that spawned this agent.
    pub spawned_by_tool: Option<String>,
}