slug: resistant-ai
provider: Resistant AI
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: 1
edges:
- tag: Tenants
  spec_file: resistant-ai-tenants-api-openapi.yml
  capability_id: BC-4230.10
  capability_id_l1: BC-4230
  capability_name: Tenant Provisioning & Lifecycle
  confidence: 0.8
  evidence: 'POST /tenants  createTenant  Create tenant; DELETE /tenants/{tenant_id}  deleteTenant; description:
    ''Managing tenants within organization - creation, deletion and listing'''
  reason: Explicit multi-tenant provisioning lifecycle. The nested application/credential operations (TenantApplicationCreateRequest,
    ClientSecretCredentials) also touch developer credential management, hence some ambiguity on the exact
    sub-capability, but tenant create/list/delete is the dominant surface.