slug: pact
provider: Pact
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: Verifications
  spec_file: pact-verifications-api-openapi.yml
  capability_id: BC-4200.50
  capability_id_l1: BC-4200
  capability_name: Software Quality Engineering
  confidence: 0.82
  evidence: POST /verification-results publishVerificationResult "Publish a verification result"
  reason: Publishing and querying contract verification results is test-result management for automated
    test suites, squarely Software Quality Engineering rather than any business-domain capability.
- tag: Pacts
  spec_file: pact-pacts-api-openapi.yml
  capability_id: BC-4200.50
  capability_id_l1: BC-4200
  capability_name: Software Quality Engineering
  confidence: 0.78
  evidence: PUT /pacts/provider/{provider}/consumer/{consumer}/version/{version} publishPact "Publish
    a pact for a consumer version"
  reason: Publishing and retrieving consumer-driven contracts is automated test-artefact stewardship —
    contract testing is part of test strategy and automated test suite management, i.e. Software Quality
    Engineering.