slug: prodsmart
provider: Prodsmart
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: Purchase Orders
  spec_file: prodsmart-purchase-orders-api-openapi.yml
  capability_id: BC-500.30
  capability_id_l1: BC-500
  capability_name: Purchase Order Management
  confidence: 0.9
  evidence: POST /api/v1/purchase-orders/ createPurchaseOrder 'Create purchase order'; 'Update purchase
    order'
  reason: Full CRUD lifecycle over purchase orders plus attached documents is plainly purchase order management
    within procurement.
- tag: Inventory
  spec_file: prodsmart-inventory-api-openapi.yml
  capability_id: BC-530
  capability_id_l1: BC-530
  capability_name: Inventory Management
  confidence: 0.78
  evidence: GET /api/v1/inventory/{id}  Retrieve product inventory; POST /api/v1/inventory-movements/  createInventoryMovement
  reason: Operations read product inventory and record inventory movements, which is stock management.
    Which L2 applies (movements vs. accuracy vs. allocation) is not determinable, so only the L1 is asserted.
- tag: Suppliers
  spec_file: prodsmart-suppliers-api-openapi.yml
  capability_id: BC-510
  capability_id_l1: BC-510
  capability_name: Supplier Management
  confidence: 0.72
  evidence: POST /api/v1/suppliers/ createSupplier 'Create supplier'; 'List suppliers'
  reason: Maintains the supplier master used by the purchasing module, which is supplier management; the
    plain CRUD surface does not name onboarding, performance or risk, so no L2 is asserted.