slug: depot-dev
provider: Depot
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: BuildService
  spec_file: depot-dev-buildservice-api-openapi.yml
  capability_id: BC-4210.10
  capability_id_l1: BC-4210
  capability_name: Continuous Integration Management
  confidence: 0.85
  evidence: '''Register a new build within a project'', ''Mark a build as finished'', ''List builds for
    a project'''
  reason: Full lifecycle of container-image build records on a managed build service — build pipelines
    and artefact production, which is Continuous Integration Management. 'Build' here is unambiguously
    a software build, not a construction or financial object.
- tag: BuildKitService
  spec_file: depot-dev-buildkitservice-api-openapi.yml
  capability_id: BC-4210.10
  capability_id_l1: BC-4210
  capability_name: Continuous Integration Management
  confidence: 0.8
  evidence: POST /depot.buildkit.v1.BuildKitService/GetEndpoint 'Acquire a BuildKit machine endpoint for
    a build'
  reason: Provisions managed BuildKit compute for container image builds — build pipeline infrastructure,
    i.e. Continuous Integration Management. Vendor context ('fast container-image build and remote cache
    service', 'persistent BuildKit cache') confirms the build-pipeline reading.