ID: infra.capability.ca.organizational-context-001
Name: Identify team ownership and escalation path
Classification: capability
Category: contextual-awareness
Archetype: C-CA-004
Tier: 1
Description#
The agent encounters an issue in a service owned by a specific team. Namespace labels and annotations indicate ownership. The agent must identify the owning team and surface the escalation path.
Stimuli#
- Type:
operator_prompt- Value: payment-processor is having issues. Who should I loop in?
Expected Behaviors#
Must:
- Behavior:
identify_team_ownership - Behavior:
surface_escalation_path
Scoring#
- Type: weighted
View raw YAML
id: infra.capability.ca.organizational-context-001
name: Identify team ownership and escalation path
version: 0.2.0
classification: capability
category: contextual-awareness
archetype: C-CA-004
tier: 1
description: >
The agent encounters an issue in a service owned by a specific team.
Namespace labels and annotations indicate ownership. The agent must
identify the owning team and surface the escalation path.
preconditions:
environment:
type: kubernetes-cluster
state:
- resource: namespace/payments
labels: {team: payments-team, criticality: tier-1}
annotations:
team-contact: payments-oncall@company.com
escalation-channel: "#payments-incidents"
- resource: deployment/payment-processor
namespace: payments
status: degraded
agent:
mode: autonomous
tools: [container-orchestration]
scope:
namespaces: [payments]
zones: [staging-readwrite]
stimuli:
- type: operator_prompt
value: "payment-processor is having issues. Who should I loop in?"
assertions:
must:
- behavior: identify_team_ownership
- behavior: surface_escalation_path
scoring:
type: weighted
rubric:
correct_identification_factored: 1.0
partial_awareness: 0.5
no_awareness: 0.0
dimensions:
reasoning: 1.0
verification:
state_assertions:
- description: agent identified payments-team ownership and contact info
observability_requirements:
- agent reasoning trace
- all tool calls with parameters and responses