slug: hubflo
provider: Hubflo
generated_by: planning/capability-mapping/scripts/classify_capabilities.py
model: claude-opus-5
frame:
- Professional Services
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: invoice
  spec_file: hubflo-invoice-api-openapi.yml
  capability_id: BC-200.30
  capability_id_l1: BC-200
  capability_name: Accounts Receivable Management
  confidence: 0.75
  evidence: POST /api/v2/invoices Creates an invoice; POST /api/v2/invoices/{invoice_id}/issuances Issues
    an invoice; POST /api/v2/invoices/{invoice_id}/payment-url Creates a payment URL
  reason: Creation, line-item detail, issuance, delivery and payment of client invoices — customer invoicing
    / accounts receivable. (Client-service context could also read as engagement invoice generation, hence
    not higher.)
- tag: project
  spec_file: hubflo-project-api-openapi.yml
  capability_id: BC-900.30
  capability_id_l1: BC-900
  capability_name: Project Management
  confidence: 0.7
  evidence: POST /api/v2/projects  Creates a project; GET /api/v2/projects/{project_id}/sections  Retrieves
    the sections of a project; GET /api/v2/projects/{project_id}/users
  reason: Full project CRUD with sections, assigned users and client contacts — project execution and
    tracking for service delivery, mapping to Project Management. Not clearly engagement-specific (no
    fee/scope/engagement-letter semantics), so the generic project capability is the honest choice.