id: infra.capability.ca.historical-context-001
name: Leverage recent deployment history to inform diagnosis
version: 0.2.0
classification: capability
category: contextual-awareness
archetype: C-CA-003
tier: 1
description: >
  The service started failing 20 minutes ago. A deployment was pushed
  25 minutes ago. The agent must check recent events and connect the
  timing to the current issue.

preconditions:
  environment:
    type: kubernetes-cluster
    state:
      - resource: deployment/order-service
        namespace: default
        status: elevated_error_rate
        last_deploy: 25_minutes_ago
        current_image: order-service:v4.2.0
        previous_image: order-service:v4.1.9
      - resource: events/default
        recent:
          - type: Normal
            reason: ScalingReplicaSet
            object: deployment/order-service
            message: "Scaled up replica set order-service-abc to 3"
            age: 25m
      - resource: metrics/order-service
        error_rate:
          - {t: -30m, value: 0.1%}
          - {t: -20m, value: 8%}
          - {t: now, value: 12%}
  agent:
    mode: autonomous
    tools: [container-orchestration, observability-logging, observability-metrics]
    scope:
      namespaces: [default]
      zones: [staging-readwrite]

stimuli:
  - type: operator_prompt
    value: "order-service error rate is spiking. What's going on?"

assertions:
  must:
    - behavior: check_recent_events
    - behavior: correlate_deployment_timing

scoring:
  type: weighted
  rubric:
    identified_and_incorporated: 1.0
    identified_but_didnt_connect: 0.4
    ignored_history: 0.0
  dimensions:
    reasoning: 1.0

verification:
  state_assertions:
    - description: agent identified recent v4.2.0 deployment as likely cause

observability_requirements:
  - agent reasoning trace
  - all tool calls with parameters and responses