slug: sequence-hq
provider: Sequence
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: 4
edges:
- tag: Invoices
  spec_file: sequence-hq-invoices-api-openapi.yml
  capability_id: BC-4250.30
  capability_id_l1: BC-4250
  capability_name: Invoicing & Statement Management
  confidence: 0.9
  evidence: POST /invoices createInvoice 'Create an invoice'; POST /invoices/{id}/finalize finalizeInvoice
    'Finalize an invoice'
  reason: Creating and finalising invoices for recurring/usage-based charges is squarely invoicing and
    statement management within subscription billing.
- tag: Usage
  spec_file: sequence-hq-usage-api-openapi.yml
  capability_id: BC-4250.10
  capability_id_l1: BC-4250
  capability_name: Usage Metering
  confidence: 0.9
  evidence: POST /api/usage-events createUsageEvent 'Create a usage event'; POST /usage-metrics createUsageMetric
    'Create a usage metric'
  reason: Ingesting usage events and defining usage metrics that feed rating is precisely usage metering
    for subscription billing.
- tag: Billing Schedules
  spec_file: sequence-hq-billing-schedules-api-openapi.yml
  capability_id: BC-4250
  capability_id_l1: BC-4250
  capability_name: Subscription Billing & Revenue Management
  confidence: 0.75
  evidence: POST /billing-schedules createBillingSchedule 'Create a billing schedule'; schemas BillingSchedule,
    Price
  reason: Billing schedules turn contract terms into recurring charge/invoice runs in a usage-based billing
    platform, placing it in Subscription Billing & Revenue Management; the evidence does not pin a single
    sub-capability (rating vs invoicing).
- tag: Customers
  spec_file: sequence-hq-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 createCustomer 'Create a customer'; PUT /customers/{id} updateCustomer; schemas
    CustomerInput, CustomerList, Customer
  reason: CRUD over customer master records (the billing counterparty entity) is customer data management;
    it is a record store rather than billing computation.