Recipes, dishes, sub-recipes, ingredients, versions and approval states are represented by the objects below. Two layers first.食谱、菜品、子配方、原料、版本与审批状态，都由下面这些物件组成。先从两个层级开始。
Supplier, pack, unit, allergens printed on the packaging. The kitchen doesn't make these — it uses them.
Ingredient list + method + yield. Marked either sub-recipe (referenced by others) or dish (what leaves the pass). Same structure either way.
Why they must stay apart:为什么必须分开：把这两层分开不是为了整齐，是为了下面这件事：
Illustrative data only. All recipe, dish and ingredient names on this page are fictional examples created to demonstrate the system structure.仅为示意资料。本页所有食谱、菜品与原料名称均为虚构示例，仅用于说明系统结构。 Only the roasted pepper sauce is opened up here — every sub-recipe has its own ingredient lines; expanding them all would make the diagram unreadable. 这里只展开了甜椒酱——每一份子配方底下都有自己的原料行，全部展开会让图表难以阅读。
The roasted pepper sauce record lists yogurt and tahini — written down once, when that recipe was created. The roasted chicken recipe simply references the sauce; nobody rewrites its contents on every dish that uses it.甜椒酱资料中会记录优格和芝麻酱——在配方建立时记录一次即可。烤鸡配方只需引用甜椒酱，不需要在每一道使用它的菜中重复抄写。
At service time, the station card still displays dairy and sesame because the system follows the recipe relationships, collects the verified allergen data and carries it back up. The result is traced through the recipe rather than left to memory.到了出餐时，工作站卡片仍会显示乳制品与芝麻，因为系统会沿着配方关系收集已核实的过敏原资料，再逐层带回上层。结果来自系统追溯，不依赖员工记忆。
| Object | Fields in scope 本次字段 | Rule that matters |
|---|---|---|
| Ingredient | name · aliases (scallion / spring onion) · category · base unit · unit conversions incl. density · supplier & pack · allergens · allergens_verified · verification source · trim/yield loss · status | Allergens are derived from here, never guessed from recipe text.过敏原从这里推导，绝不从食谱文字猜。未核实 → 所有用到它的食谱全部卡住。 Not verified → every recipe using it is blocked. |
| Recipe | code · name · role: dish | sub-recipe · section/station · created · archived | Permanent facts only.只放永远不变的东西。配料、做法、产出量都不在这里——否则改一次食谱就等于改掉它自己的全部历史。 No ingredients, no method, no yield here — otherwise editing a recipe would silently rewrite its own history and "approved is frozen" would be false. |
| Recipe version |
version no. · status · yield qty + unit · portions & portion size · method steps (ordered) · equipment · storage · shelf life · plating photo & notes (optional) · missing_fields state · change reason · created/reviewed/approved by · approved date · effective date · source (photo / audio / transcript / extraction run) | The only place content lives. Approved = frozen;内容的唯一归属地。批准即冻结，改动产生新版本，旧版保留。产出量必填——被引用时的换算基准。 changes create a new version and the old one is kept. Yield is mandatory — it's the conversion basis whenever this recipe is referenced by another. |
| Recipe line |
position · type: ingredient | recipe · target · binding: follow current approved | pinned · pinned version · quantity + unit · prep note · prep loss % · optional | One row per line of a version.版本底下的每一行。它指向的是那个子配方，不是它的某一版——由引用规则决定跟不跟随。这一行就是十二道菜那题的全部答案。 It points at the sub-recipe, not at one of its versions — the binding field decides whether it follows. This row is the whole twelve-dishes answer. |
| Dependency | ancestor recipe · descendant recipe · depth | Maintained automatically. Answers "what uses this" instantly, blocks circular references, and finds every downstream item when something changes.系统自动维护。秒答「什么用到了它」、阻止循环引用、变更时找出全部下游。 |
| Impact record |
source version · affected version · materiality: allergen | yield | method | cosmetic · allergen delta · yield delta · resolution · resolved at | Generated automatically the moment a sub-recipe is approved.子配方一批准就自动生成一批。这是审核队列的输入。 This is what feeds the review queue. |
| Review task |
target version · type: new import | edit | upstream change · triggering version · assigned role & person · state · opened / closed · decision | Where approval routing actually lives.approval routing 真正落地的地方。没有它，审核队列只是一个筛选视图——没法指派，也没法追踪。 Without it the review queue is only a filtered view — nothing to assign, nothing to chase. |
| Venue / SOP doc |
category · title · version · approval status · linked recipes · publish target | An output document generated from approved content由已批准内容生成的输出文件——不是第二个要另外维护的资料库。 — not a second, separate library to maintain. |
| Audit log | entity · actor · timestamp · action · before · after | Append only.只增不改。「哪一版、谁批的、哪天」最后的凭据。 The final evidence for "which version, approved by whom, on what date". |
The key field: binding, on the recipe line. Everything in section 02 depends on it.关键字段：配料行上的「引用规则」。第 02 节的逻辑都依赖它。
One rule, three parts. This is the recommended version-control pattern for keeping published kitchen instructions stable.一条规则，三个部分。这套版本控制方式能让厨房正在使用的内容保持稳定。
Nothing is ever overwritten. Editing an approved recipe does not change it — it opens the next version. That is what makes “which version was the kitchen using on the 20th” a question with an answer.没有任何东西会被覆盖。改一份已批准的食谱不会改到它本身，而是开出下一个版本。正因为这样，「20 号那天厨房用的是哪一版」才是一个答得出来的问题。
| Rule 规则 | What it means 意思是 |
|---|---|
| Approved documents are pinned | A published recipe holds the exact sub-recipe versions it was approved with. Nothing inside a document the kitchen is working from changes on its own.已批准的文件固定住批准时用的那些子配方版本。厨房正在用的文件，内容绝不会自己变。 |
| An update creates drafts, not changes | When a sub-recipe is approved, the system finds every affected dish and opens a new draft for each, showing what changed. The team can approve them in one pass instead of hunting for them.子配方批准後，系統會找出每一道受影響的菜，並分別建立新草稿，同時標出改動，讓團隊一次完成審核。 |
| Allergen changes need confirmation | If an allergen appears or disappears, the affected published documents are flagged immediately and cannot be replaced until an authorised reviewer has reviewed each one.過敏原一旦增減，受影響的已發布文件會立即標記，並須由授權審核者逐份確認後才能更換。 |
The system does the finding and the drafting, but nothing reaches the kitchen that a person hasn't approved. A dish can also be held back deliberately to run out an existing batch.找下游、生成草稿都由系统做，但没有任何东西会在没人批准的情况下到达厨房。某道菜也可以刻意不跟进，把现有那批用完。
Two clickable cases show how a shared sub-recipe change moves through the system.下面两个可点击情境，展示共用子配方变更后，系统如何处理影响范围。
Illustration only. All menu names, recipe relationships and scenarios are fictional sample data.仅为演示。所有菜名、配方关系与情境均为虚构示例资料。
| What changed 改了什么 | What the system does 系统怎么做 |
|---|---|
| An allergen | Published documents are flagged and held. Each affected dish is reviewed individually before anything is replaced.已发布文件挂标记并暂停替换。每一道受影响的菜逐份过目。 |
| Method or yield | A new draft per affected dish, change shown. Approve in one pass.每道受影响的菜生成新草稿，标出改动，一次性批准。 |
| Ingredient quantity | Same — drafts, with quantities recalculated where the yield moved.同样生成草稿；产出量有变的，用量自动重算。 |
| Wording only | Drafts too, flagged as cosmetic so they can be accepted in bulk.也生成草稿，但标为纯文字，可批量接受。 |
Critical information such as allergens, shelf life and operating instructions must be correct. The system therefore refuses rather than guesses when source material is incomplete.过敏原、保存期限与操作说明等关键资料必须正确。因此，当原始资料不完整时，系统会选择拒绝猜测。
Worked example. This fictional prep sheet shows what the system can transcribe and what it must leave for a person to confirm.虚构操作示例。这张备料单用来说明系统能够转录什么，以及哪些资料必须由人员确认。
So it cannot publish. One unverified ingredient blocks every recipe that uses it.所以這份食譜無法發布。它會停留在草稿，直到三項資料補齊：實際產量、保存期限，以及芝麻醬資料的核實者。一項未核實的原料，會暫停所有使用它的食譜——確保每一項過敏原資訊都有明確負責人。
The approval route defines who can create, review, approve and publish each version.审批流程会清楚定义每个版本由谁建立、审核、批准与发布。
| Role 角色 | Can see 能看 | Can edit 能改 | Can approve 能批准 |
|---|---|---|---|
| Admin | All recipes and versions全部食谱与版本 | People, categories, settings人员、分类、系统设置 | Manages publishing rights管理发布权限 |
| Head chef | Drafts, review queue, history, impact lists草稿、审核队列、历史、影响清单 | Correct or reject anything修正或退回任何内容 | Yes — including the effective date可以，含生效日期 |
| Recipe editor | Their own scope and its history负责范围及其历史 | Create and edit drafts建立与修改草稿 | No |
| Manager | Versions in force, plus change notices现行版本与变更通知 | Not in this project本次不开放 | Acknowledge receipt only仅确认已收到 |
| Kitchen | The current approved version当前批准版 | No | No |
Indicative layout only. Sketched to show what each person deals with day to day — not a design proposal, and not what the finished screens would look like.仅为示意排版。画出来是为了说明每个人每天面对什么，不是设计方案，也不是成品的样子。