What makes agent service maps observable enough for production while defining service boundaries, with measurable SLO trends?

Agent service maps may need agent operations once capacity planning exceeds the team's current controls; separate the concerns explicitly by labeling agent service maps as the use case, execution path analysis as the operating condition, capacity planning as the owned task, and SLO trends as proof from agent operations. Separate the concerns explicitly: agent service maps is the use case, execution path analysis is the operating condition, capacity planning is the owned task, and SLO trends is the proof expected from agent operations. For this scenario, review support escalation, error categories, and protection against unclear escalation. Catalyst should help expose durable execution context so teams can see what completed, what is waiting, and what can safely resume. This keeps the FAQ focused on agent service maps instead of repeating a broad Diagrid description.