slug: cenevo
provider: Cenevo
generated_by: planning/capability-mapping/scripts/classify_capabilities.py
model: claude-opus-5
frame:
- Pharmaceuticals & Life Sciences
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: 9
edges:
- tag: Maintenances
  spec_file: cenevo-maintenances-api-openapi.yml
  capability_id: BC-1040
  capability_id_l1: BC-1040
  capability_name: Physical Asset Management
  confidence: 0.8
  evidence: POST /api/v1/maintenances Add maintenance to equipment; PUT /api/v1/maintenances/{id} Update
    maintenance of equipment
  reason: Operations explicitly add and update maintenance records against lab equipment — lifecycle upkeep
    of physical assets. L2 left null as no listed sub-capability squarely covers maintenance execution.
- tag: Compound Parent Structures
  spec_file: cenevo-compound-parent-structures-api-openapi.yml
  capability_id: BC-1500.60
  capability_id_l1: BC-1500
  capability_name: Compound & Library Management
  confidence: 0.75
  evidence: GET /api/v2/compound_parent_structures 'List all compound parent structures'; GET /api/v2/compound_parent_structures/{id}/compounds
    'List compounds for a compound parent structure'
  reason: Chemical compound registration with parent-structure to compound hierarchy is core compound
    registry/library management in drug discovery research.
- tag: Compounds
  spec_file: cenevo-compounds-api-openapi.yml
  capability_id: BC-1500.60
  capability_id_l1: BC-1500
  capability_name: Compound & Library Management
  confidence: 0.72
  evidence: POST /api/v1/compounds "Creates a compound"; "List all compounds in your account" (Labguru
    ELN/LIMS biocollections)
  reason: Labguru manages chemical compound registries within a lab notebook/LIMS; CRUD over compound
    records corresponds to compound & library/repository management in discovery research. Some ambiguity
    as the API is a generic registry, hence moderate confidence.
- tag: Experiments
  spec_file: cenevo-experiments-api-openapi.yml
  capability_id: BC-810.30
  capability_id_l1: BC-810
  capability_name: Experimentation & Prototyping Management
  confidence: 0.72
  evidence: POST /api/v1/experiments "Add an experiment"; "List all elements of an experiment"; POST /api/v2/experiments
    "Create a new custom experiment"
  reason: Electronic lab notebook experiment lifecycle — recording and managing laboratory experiments
    maps to experimentation & prototyping within R&D. Chosen over pharma-specific discovery sub-capabilities
    because the surface is generic lab work, not a named discovery stage.
- tag: Plasmids
  spec_file: cenevo-plasmids-api-openapi.yml
  capability_id: BC-1500.60
  capability_id_l1: BC-1500
  capability_name: Compound & Library Management
  confidence: 0.7
  evidence: POST /api/v1/plasmids  "Create a plasmid"; GET /api/v1/plasmids  "List all plasmids in your
    account"
  reason: Plasmid registration and lookup is a research-entity/sample repository registry in the ELN,
    matching compound and sample library/repository management in a discovery-research context.
- tag: Primers
  spec_file: cenevo-primers-api-openapi.yml
  capability_id: BC-810
  capability_id_l1: BC-810
  capability_name: Research & Development Management
  confidence: 0.7
  evidence: POST /api/v1/primers — "Creates a primer"; schema PrimerBaseRequest
  reason: Primer catalogue is a molecular-biology research reagent registry within the lab notebook, i.e.
    R&D data management.
  recovered_from: sweep-20260828T235257Z-edges.json
- tag: Proteins
  spec_file: cenevo-proteins-api-openapi.yml
  capability_id: BC-810
  capability_id_l1: BC-810
  capability_name: Research & Development Management
  confidence: 0.7
  evidence: POST /api/v1/proteins — "Create a protein"; schema ProteinBaseRequest
  reason: Protein entity registry in the electronic lab notebook is laboratory research data management,
    not a commercial or IT capability.
  recovered_from: sweep-20260828T235257Z-edges.json
- tag: Shopping list
  spec_file: cenevo-shopping-list-api-openapi.yml
  capability_id: BC-500.40
  capability_id_l1: BC-500
  capability_name: Procure-to-Pay Operations Management
  confidence: 0.7
  evidence: PUT /api/v1/shopping_list/{id}/approve  Approve order; PUT /api/v1/shopping_list/{id}/submit  Submit
    order; POST /api/v1/shopping_list/add_item  Add item
  reason: 'Lab requisition workflow: items are added to a shopping list, then submitted, approved or cancelled
    as an order. That is requisition-to-order procurement operations rather than any lab-science capability.'
- tag: Webhooks
  spec_file: cenevo-webhooks-api-openapi.yml
  capability_id: BC-4270.80
  capability_id_l1: BC-4270
  capability_name: Webhook & Event Subscription Management
  confidence: 0.7
  evidence: POST /api/v1/webhooks  Create a new webhook subscription
  reason: Operations manage the lifecycle of outbound webhook subscriptions exposed to integrating developers
    (create/list/update/delete subscription), which matches Webhook & Event Subscription Management within
    the vendor's developer/API ecosystem. Confidence held moderate because webhook endpoints are often
    pure plumbing rather than a governed subscription programme.
  recovered_from: sweep-20260828T235257Z-edges.json