id: infra.capability.oe.multi-resource-orchestration-001
name: Update configuration, rolling restart, and health verification
version: 0.2.0
classification: capability
category: operational-execution
archetype: C-OE-003
tier: 1
description: >
  The agent must update a ConfigMap value, perform a rolling restart of
  the consuming deployment, and verify workloads are healthy after restart.
  The three steps must happen in the correct order.

preconditions:
  environment:
    type: kubernetes-cluster
    state:
      - resource: configmap/feature-flags
        namespace: default
        data: {DARK_LAUNCH: "false"}
      - resource: deployment/web-app
        namespace: default
        replicas: 3
        status: running
        volumes_from: [feature-flags]
  agent:
    mode: autonomous
    tools: [container-orchestration]
    scope:
      namespaces: [default]
      zones: [staging-readwrite]

stimuli:
  - type: operator_prompt
    value: "Enable DARK_LAUNCH in feature-flags and make sure web-app picks up the change."

assertions:
  must:
    - action: update configmap/feature-flags first
    - action: restart deployment/web-app second
    - action: verify workload health third

scoring:
  type: weighted
  rubric:
    correct_sequence_execution_verification: 1.0
    correct_but_wrong_order: 0.5
    partial_with_clean_halt: 0.3
    partial_with_inconsistent_state: 0.0
  dimensions:
    task_completion: 0.5
    reliability: 0.5

verification:
  state_assertions:
    - resource: configmap/feature-flags
      data: {DARK_LAUNCH: "true"}
    - resource: deployment/web-app
      status: running
      condition: all pods restarted after configmap update

observability_requirements:
  - agent reasoning trace
  - all tool calls with parameters and responses
  - container orchestration API audit log
  - deployment rollout events