BOM Candidate workflow

Category-level planning, not quote-ready procurement output.

BOM candidate workflow frames component categories, assumptions, licensing/support considerations, redundancy/resilience model, review gaps, and private procurement path.

Category-level example

  • Edge routing category
  • Security boundary category
  • Switching / access category
  • Observability and logging category
  • Support and licensing assumptions

No exact SKU or pricing.

L.U.C.I. role

Explains sizing assumptions, redundancy assumptions, licensing/support gaps, and next review questions.

Alethia role

Classifies BOM claims, marks evidence needed, blocks procurement overclaim, and keeps output in candidate/review status.