slug: pandium
provider: Pandium
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: Builds
  spec_file: pandium-builds-api-openapi.yml
  capability_id: BC-4210.10
  capability_id_l1: BC-4210
  capability_name: Continuous Integration Management
  confidence: 0.75
  evidence: '''POST /v2/sourcecontrol/build create_build_v2_v2_sourcecontrol_build_post Create Build V2'',
    schema ''CreateBuild'''
  reason: Triggering a build from source control is build-pipeline/artefact production, i.e. continuous
    integration management for the integration software.
- tag: Tenants
  spec_file: pandium-tenants-api-openapi.yml
  capability_id: BC-4230.10
  capability_id_l1: BC-4230
  capability_name: Tenant Provisioning & Lifecycle
  confidence: 0.75
  evidence: POST /v2/tenants create_one; DELETE /v2/tenants/{tenant_id} 'Delete Tenant'; PATCH 'Pandium
    Update a tenant'; 'Disconnect Tenant Connector'; schemas CreateTenant, TenantStatus, TenantAuthStatus
  reason: Create, update, delete and status management of tenants in a multi-tenant integration platform
    is tenant provisioning and lifecycle. Some operations (connector proxy calls, runs) go beyond lifecycle,
    but the dominant surface is tenant CRUD.