Stage 2 · Analysis
The operator jobs behind Overview
Give operators a stable map of the Kitchen while every fact and action retains an explicit owner.
- 1
Understand the selected Kitchen
Confirm which Kitchen is active and whether its essential identity and Place link are sufficiently configured.
Overview composes identifiers and readiness facts; Place-owned identity is not copied onto Kitchen.
Owners: Kitchen · Place · Identity
- 2
Discover what can be managed
Scan a stable, conventional map of Food & Drink, Operations, Kitchen Setup and Reports.
The navigation tree is the product map. Search demand influences its doorways but does not flatten ownership.
Owners: Kitchen capability catalogue
- 3
Enter the right capability
Start from a recognisable operator question and continue into the capability that owns the relevant records and Tools.
Overview routes intent. It does not execute child Tools or duplicate their working interfaces.
Owners: Each child capability
- 4
Understand proven coverage
See which capability evidence is available, missing or not yet connected without receiving invented scores or promises.
Availability and source-labelled summaries are valid; generic Kitchen health, quality, efficiency and profit are not.
Owners: Each child capability · Overview presentation
Required record questions
- Which Kitchen is selected and which Place supplies its presentation identity?
- Which capability catalogue version determines the visible groups and routes?
- Which child capability owns every displayed fact or status?
- Is each summary live evidence, configuration state, missing evidence or explanatory literature?
- Can every question or summary route directly to its owning capability?
- Which capabilities have no authoritative producer yet and must remain explicitly unavailable?
- Does any displayed score imply quality, compliance, efficiency, cost or profit without a bounded source?