slug: authzed
provider: Authzed
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: Permissions
  spec_file: authzed-permissions-api-openapi.yml
  capability_id: BC-620.20
  capability_id_l1: BC-620
  capability_name: Identity & Access Management
  confidence: 0.85
  evidence: POST /v1/permissions/check — 'CheckPermission determines for a given resource whether a subject
    computes to…'; LookupSubjects returns all the subjects of a given type that have access
  reason: The operations execute fine-grained authorization decisions (permission checks, resource/subject
    lookups) — this is access management tooling, mapping to Identity & Access Management rather than
    any business-domain capability.
- tag: Relationships
  spec_file: authzed-relationships-api-openapi.yml
  capability_id: BC-620.20
  capability_id_l1: BC-620
  capability_name: Identity & Access Management
  confidence: 0.78
  evidence: POST /v1/relationships/write — 'WriteRelationships atomically writes and/or deletes a set
    of specified…'; schemas RelationshipFilter, SubjectReference
  reason: Relationship tuples here are the authorization grant data of a Zanzibar-style access control
    system; writing/reading them is the administration of access rights, i.e. IAM. Not a CRM 'relationship'
    concept.