slug: dojo
provider: Dojo
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: Webhooks
  spec_file: dojo-webhooks-api-openapi.yml
  capability_id: BC-4270.80
  capability_id_l1: BC-4270
  capability_name: Webhook & Event Subscription Management
  confidence: 0.75
  evidence: POST /webhooks  Webhooks_Subscribe  Subscribe to an event; GET /webhooks/events  List all
    events; POST /webhooks/{subscriptionId}/secrets  Generate a secret
  reason: The surface is the full lifecycle of outbound event subscriptions and their signing secrets
    exposed to integrating developers, which is exactly BC-4270.80 Webhook & Event Subscription Management.
    Though webhooks are often plumbing, this frame has an explicit capability for vendor-exposed webhook
    subscription management.
- tag: Customers
  spec_file: dojo-customers-api-openapi.yml
  capability_id: BC-420.10
  capability_id_l1: BC-420
  capability_name: Customer Data Management
  confidence: 0.7
  evidence: 'POST /customers  Customers_Create  Create a customer; PATCH /customers/{customerId}  Customers_Update  Update
    information about a customer; schemas: CustomerFull, Address, SearchCustomerRequest'
  reason: Full CRUD and search over customer master records (name, address, secrets) held by the merchant,
    with stored payment methods attached. The dominant surface is maintaining the customer record itself,
    which is Customer Data Management; the payment-method sub-resources add some ambiguity, hence 0.7.