slug: eppo
provider: Eppo
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: 3
edges:
- tag: Experiments
  spec_file: eppo-experiments-api-openapi.yml
  capability_id: BC-4280.50
  capability_id_l1: BC-4280
  capability_name: A/B Test Execution
  confidence: 0.85
  evidence: POST /experiments  createExperiment  Create an experiment
  reason: Creating and listing experiments on a feature flagging and experimentation platform is configuration
    and monitoring of running A/B tests; L1 Product Telemetry & Experimentation Management is clear, sub-capability
    split between programme management and test execution.
- tag: Allocations
  spec_file: eppo-allocations-api-openapi.yml
  capability_id: BC-4210.50
  capability_id_l1: BC-4210
  capability_name: Feature Flag Management
  confidence: 0.82
  evidence: GET /flags/{flagKey}/allocations  List allocations for a flag
  reason: Allocations are the targeting/traffic-split rules attached to a feature flag in Eppo, i.e. runtime
    control and targeting of feature flags — Feature Flag Management. Some ambiguity with A/B test execution
    since allocations also drive experiment traffic split.
- tag: Assignments
  spec_file: eppo-assignments-api-openapi.yml
  capability_id: BC-4280.10
  capability_id_l1: BC-4280
  capability_name: Product Telemetry Instrumentation
  confidence: 0.7
  evidence: POST /assignments  ingestAssignments  Ingest assignment events
  reason: Ingestion of assignment events (which subject saw which variant) is telemetry/event capture
    feeding experiment analysis. Maps to product telemetry instrumentation; moderate confidence as it
    could also be read as A/B test execution plumbing.