Recipe Platform Current-State Analysis

Current-State Analysis

Scope

This artifact describes the business current state that motivated the project: the existing corporate recipe collection and menu builder environment has missing or insufficient capabilities for commercial-kitchen scaling, rollups, forecasting, production records, ordering forecasts, and accuracy analysis.

The prototype represents a proposed future operating model rather than the current corporate environment. Current-state findings are based on identified operating gaps, while prototype behavior and tests support the proposed solution direction.

Executive Summary

• User-provided: The current corporate recipe collection/menu builder lacks several desired functions, including proper mass-to-volume conversion, unconventional volume units/conversions such as hotel pans, sub-recipe ingredient rollups, forecasting tied to production records, automated ordering forecasts, and forecast-to-production accuracy analysis.
• Observed: The prototype repository implements or is actively building these missing capabilities across Recipe Collection, Menu Builder, Forecasting, Production Record, Inventory, and future Analytics. Evidence: README.md, AGENT.md, docs/agent_context/*.md, services, tests, and schema.
• Observed: The prototype operating loop is Recipe Collection -> Menu Builder -> Forecasting -> Production Record -> Inventory, with future Analytics consuming stabilized facts. Evidence: README.md, docs/agent_context/shared_agent_workflow.md.
• Inferred: The corporate current-state pain is not only recipe storage; it is the lack of a reliable operational chain from recipe truth through scaled production, ingredient demand, ordering signals, and actual-vs-forecast learning.

Corporate Current-State Limitations

Area	Current-State Limitation	Business Impact	Evidence Quality	Evidence
Recipe scaling	Proper mass-to-volume conversion is missing or insufficient.	Recipes cannot be reliably scaled across production quantities when ingredient or yield basis crosses unit families.	User-provided	User clarification
Hotel-pan units	Unconventional volume units/conversions such as hotel pans are not adequately supported.	Production users cannot forecast or scale in familiar commercial-kitchen container units.	User-provided	User clarification
Sub-recipe rollups	Current tools lack recipe roll-up behavior for scaling from sub-recipe ingredients.	Ingredient demand cannot be accurately derived from nested recipes.	User-provided	User clarification
Forecasting	Menu forecasting is not sufficiently tied to production record workflows.	Forecasts do not naturally become production-facing plans or measurable operational records.	User-provided	User clarification
Ordering forecast	Automated ordering forecast is missing or incomplete.	Purchasing and inventory planning require manual translation from menus/production needs.	User-provided	User clarification
Accuracy analysis	Forecast-to-production accuracy analysis is missing or incomplete.	Managers lack a feedback loop for improving forecast assumptions and production planning.	User-provided	User clarification

Prototype Capability Evidence

Future-State Prototype Capability	Prototype Current Implementation / Direction	Evidence Quality	Evidence
Recipe Collection	Structured recipe/base-food authoring, item detail, search, scaling, flattened recipe views, print sheets, and mock-user-scoped My Recipes.	Observed	README.md; docs/agent_context/recipe_collection.md; src/services/recipe_*; tests/test_recipe_*
Unit conversion	Same-family conversion, mass/volume bridge conversion, item authority fields, and warnings for unsupported conversions.	Observed	src/services/unit_conversion_service.py; src/services/recipe_scaling_service.py; tests
Hotel-pan scaling	Advanced hotel-pan units are reserved for live scaling and Forecasting rather than basic authoring.	Observed	src/config/units.py; src/config/hotel_pan_units.py; recipe/forecast docs and tests
Sub-recipe rollups	Hierarchical and flattened recipe views support nested recipe expansion and ingredient-level scaling.	Observed	src/services/recipe_flattening_service.py; src/services/recipe_scaling_service.py; tests
Menu Builder and Forecasting	Dated menu cycles, slot assignments, yield/case/portion forecasting, case packs, batch splits, and production summaries.	Observed	src/services/menu_service.py; src/services/menu_forecast_service.py; docs/agent_context/menu_builder.md
Production Record	Forecast snapshots, actuals, leftover/shortage, implied demand, forecast accuracy, post/lock, review, export, and history.	Observed	src/services/production_record_service.py; production tests
Inventory and ordering	Live counts, item usage, planning, ordering preferences, inventory availability, catalog bridge, invoice staging, and vendor/substitute work.	Observed	src/services/inventory_*; docs/agent_context/inventory.md; inventory tests
Analytics path	Analytics is intentionally deferred until stable production, inventory, purchasing, cost, and variance contracts exist.	Observed	README.md; AGENT.md

Architecture Observations

• Observed: The prototype uses Python 3.13+, Flask, SQLite, server-rendered templates, focused JavaScript, service/query modules, and forward-only SQL migrations. Evidence: pyproject.toml, README.md, database/migrations/, database/schema.sql.
• Observed: Business calculations are primarily in service/query layers rather than templates. Evidence: recipe scaling, menu forecasting, production record, inventory usage, inventory ordering, and invoice services.
• Observed: Git history shows the prototype has evolved from recipe collection toward menu planning, forecasting, production records, inventory, catalog/vendor bridge work, and production trend analysis. Evidence: git log --date=short --max-count=40.
• Inferred: The prototype is a future-state validation vehicle for missing corporate capabilities, not just a replacement CRUD app.

Current Constraints and Unknowns

• User-provided: The exact corporate current-state system details are represented only by the stated missing functions in this artifact; no source documents from the corporate system were provided.
• Observed: The prototype uses mock auth for MVP role testing; production identity and deployment requirements are not yet defined.
• Observed: Inventory counts and invoice placement are operational prototype concepts, not finalized accounting workflows.
• Unknown: The deployment target, enterprise integration needs, approval model, data migration approach, and compliance requirements for replacing or augmenting the corporate system are not defined in repo evidence.

BA Alignment

• Activity areas: Elicit and collaborate; analyze strategy; evaluate solution against desired future-state capabilities.
• Techniques used: Current-state analysis, gap identification, document analysis, interface analysis, data modeling.