A 311 supervisor agent delegates to subagents without passing purpose and retention limits. What is missing?
Select an answer to reveal the explanation.
Short Explanation
When the boss agent hands work to helpers, the rules about why data is used and how long it is kept have to travel too. Propagate purpose and retention limits on every handoff. Silent delegation without policy is how PII outlives its welcome.
Full Explanation
A 311 supervisor agent that delegates to subagents without passing purpose and retention limits drops mandatory privacy policy context at the handoff boundary. What is missing is propagating policy context such as purpose and retention through agent handoffs so every downstream civic agent inherits why resident data may be used and how long it may be kept. Without that propagation, subagents may over-collect, over-retain, or reuse 311 ticket content beyond the original service purpose.
Unlimited retention so subagents keep every resident message forever fails by concept: it contradicts retention limitation and expands breach and discovery exposure. Stripping all privacy labels so subagents process tickets faster removes the metadata needed for purpose enforcement. Forwarding supervisor OAuth refresh tokens into every subagent prompt shares long-lived credentials through model context instead of propagating privacy policy.
Exam caveat: propagating purpose and retention is necessary for multi-agent privacy continuity; subagents must also enforce those constraints in their tools and stores, not merely receive them as unread text. Operational check: delegate a 311 ticket with explicit purpose and 30-day retention to a subagent, inspect the handoff payload for those fields, and verify the subagent’s memory/store enforces deletion or blocking after the retention window and refuses off-purpose tool uses.