slug: warrant-dev
provider: Warrant
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: 3
edges:
- tag: Roles & Permissions
  spec_file: warrant-dev-roles-permissions-api-openapi.yml
  capability_id: BC-620.20
  capability_id_l1: BC-620
  capability_name: Identity & Access Management
  confidence: 0.92
  evidence: POST /v1/roles/{roleId}/permissions/{permissionId}  assignPermissionToRole  Assign a permission
    to a role; POST /v1/users  createUser
  reason: Explicit RBAC surface — roles, permissions, users, tenants — which is squarely Identity & Access
    Management.
- tag: Warrants
  spec_file: warrant-dev-warrants-api-openapi.yml
  capability_id: BC-620.20
  capability_id_l1: BC-620
  capability_name: Identity & Access Management
  confidence: 0.85
  evidence: 'POST /v1/warrants  createWarrant  Create a warrant; schemas: Subject, Warrant'
  reason: Warrants are the relationship tuples granting a subject access to an object — i.e. authorization
    grant management, part of IAM. 'Warrant' here is not a legal or financial instrument.
- tag: Check
  spec_file: warrant-dev-check-api-openapi.yml
  capability_id: BC-620.20
  capability_id_l1: BC-620
  capability_name: Identity & Access Management
  confidence: 0.82
  evidence: 'POST /v2/authorize  checkAccess  Check access; schemas: Subject, CheckRequest, CheckResult'
  reason: Operations evaluate whether a subject may access a resource — runtime access control decisions,
    which is Identity & Access Management. Not an industry-specific capability; the vendor is an authorization
    devtool.