slug: antimetal
provider: Antimetal
generated_by: planning/capability-mapping/scripts/classify_capabilities.py
model: claude-opus-5
frame:
- Software & Technology
min_confidence: 0.7
capability_model:
  source: https://github.com/vincentmakes/turbo-ea-capabilities
  license: CC-BY-4.0
  attribution: Turbo EA Capabilities by Vincent Verdet — Turbo EA, https://github.com/vincentmakes/turbo-ea-capabilities,
    CC BY 4.0
  notice: NOTICE
edge_count: 2
edges:
- tag: Artifacts
  spec_file: antimetal-artifacts-api-openapi.yml
  capability_id: BC-4220.20
  capability_id_l1: BC-4220
  capability_name: Observability Management
  confidence: 0.7
  evidence: GET /artifacts 'Retrieve artifacts by IDs'; schemas LogArtifactDto, TraceArtifactDto, MetricArtifactDto,
    EventArtifactDto, TopologyArtifactDto
  reason: The artifact types are precisely logs, metrics, traces, events and topology — the telemetry
    that makes a running production service understandable, retrieved as evidence during incident investigation.
    That is Observability Management, not product usage telemetry (BC-4280), since the signals are infrastructure-level.
- tag: Issues
  spec_file: antimetal-issues-api-openapi.yml
  capability_id: BC-4220.30
  capability_id_l1: BC-4220
  capability_name: Incident Response Management
  confidence: 0.7
  evidence: '''Create a new issue'', ''Update issue status by ID'', ''Fetch investigation results by ID
    (UUID)''; vendor: agents that ''triage noisy signals into structured issues, investigate incidents
    down to a root cause'''
  reason: Issues here are triaged production incidents with investigation results, per the vendor description
    — detection, coordination and resolution of production problems maps to Incident Response Management.
    Some overlap with BC-600.30 IT Service Management, which is why confidence is 0.7 rather than higher.