Basket optimization
MILP
A solver-backed implementation with stock constraints and re-solving. This describes the algorithm, not measured sales impact.
Validation notes Back to portfolio
Current BasketOps interface in disconnected mode. No live purchase or backend result is shown.Open full capture
Case study / Local engineering prototype
HyperFlow
A commerce prototype connecting basket optimization, approval boundaries, reconciliation, durable jobs, and experimental demand modeling.
Local engineering prototype
Solo project; AI-assisted development.
The idea
The problem
An optimized basket still needs stock reconciliation, approval, and recoverable provider actions before it becomes an executed order.
The implementation
What I built
Implemented solver-backed baskets and reconciliation, then strengthened action approval, workflow state, and experiment provenance.
- FastAPI
- React
- Python
- MILP
- LightGBM
Features
- Optimize baskets with stock constraints
- Re-solve after cart reconciliation
- Review approval state before provider actions
Architecture
- React workbench and FastAPI services.
- MILP solver with stock constraints and reconciliation-driven re-solving.
- Provider adapters, durable job paths, replay scenarios, and separate model fit/evaluation artifacts.
Engineering decisions
- Keep a proposed basket distinct from an authorized provider action.
- Re-solve after stock or cart constraints change.
- Separate synthetic demand experiments from operational commerce metrics.
Validation and measured results
- Basket optimization uses an actual MILP solver; reconciliation adjusts constraints and re-solves.
- Demand studies measure relative WMAPE improvement on synthetic censored rows, not recovered real sales.
- These notes describe the current local workflow. No operational commerce benchmark or public receipt download is attached.
Limits and unfinished work
- No recovered revenue, live operational accuracy, or deployment-wide provider execution is claimed.
- Older repository material can contain superseded claims. This case study describes the narrower current scope.
- Authenticated provider execution depends on actual credentials and availability.
Evidence and sources
- Implementation and validation notes
Locally reviewed implementation. The repository was not publicly accessible on 14 October 2026; historical claims need separate qualification.