slug: fermyon
provider: Fermyon
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: Payments
  spec_file: fermyon-payments-api-openapi.yml
  capability_id: BC-4250.40
  capability_id_l1: BC-4250
  capability_name: Payment Collection & Dunning
  confidence: 0.7
  evidence: POST /api/payments/setup-checkout; GET /api/payments/customer-portal; GET /api/payments/plans
    — schemas PlanItem, PaymentIntegrationUrl
  reason: Checkout setup and a billing customer portal are payment-method and collection mechanics for
    a subscription plan catalogue, placing this in subscription billing; some ambiguity remains because
    the plans endpoint also touches plan/entitlement design.
- tag: variable-pairs
  spec_file: fermyon-variable-pairs-api-openapi.yml
  capability_id: BC-4210.60
  capability_id_l1: BC-4210
  capability_name: Configuration & Secrets Management
  confidence: 0.7
  evidence: POST /api/variable-pairs Create api variable pairs — schemas CreateVariablePairCommand, GetVariablesQuery,
    VariablesList
  reason: Create/list/delete of application variable pairs is management of runtime configuration values
    (and secrets) consumed by deployed services, matching configuration & secrets management.