lukas/Ghost_Kitchen
1
0
Fork 0
Code Issues 1 Pull Requests Actions Packages Projects Releases Wiki Activity

Freeze an Order Item's Recipe at order time

Browse Source 
Price was already snapshotted per Order Item so later menu changes
don't rewrite history, but the Recipe (Step list) wasn't: advancing an
Order Item looked up its next Step from the live menuItemSteps table,
so an operator editing a Menu Item's Recipe mid-cook could silently
reshape an Order already in flight (different Machine Tag, duration,
or Step order than what the customer paid for).

Adds order_item_steps as a per-Order-Item copy of the Recipe, taken at
placement time; placeOrder, advanceOrderItemStep, and getOrderStatus
now all read from that snapshot instead of the live menu. Recorded as
docs/adr/0005 and added Recipe as a formal CONTEXT.md term.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
This commit is contained in:
lukas
2026-09-09 19:55:05 +02:00
co-authored by Claude Sonnet 5
parent d291312139
commit 9c3ad51686
8 changed files with 732 additions and 43 deletions
Download Patch File Download Diff File Expand all files Collapse all files
drizzle/0002_large_lake.sql
+10
View File
@@ -0,0 +1,10 @@
CREATE TABLE "order_item_steps" (
"id" serial PRIMARY KEY NOT NULL,
"order_item_id" integer NOT NULL,
"sequence" integer NOT NULL,
"machine_tag_id" integer NOT NULL,
"estimated_duration_seconds" integer NOT NULL
);
--> statement-breakpoint
ALTER TABLE "order_item_steps" ADD CONSTRAINT "order_item_steps_order_item_id_order_items_id_fk" FOREIGN KEY ("order_item_id") REFERENCES "public"."order_items"("id") ON DELETE no action ON UPDATE no action;--> statement-breakpoint
ALTER TABLE "order_item_steps" ADD CONSTRAINT "order_item_steps_machine_tag_id_machine_tags_id_fk" FOREIGN KEY ("machine_tag_id") REFERENCES "public"."machine_tags"("id") ON DELETE no action ON UPDATE no action;