> For the complete documentation index, see [llms.txt](https://eurekabusiness.caiziii.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://eurekabusiness.caiziii.com/eurekabusinesscommunity-en/module-reference/restaurant-module.md). # Restaurant Module Boundaries Restaurant is an optional content module built on top of Core framework contracts, providing restaurant simulation mechanics. ## Module Boundaries Restaurant depends on Core, but maintains strict isolation from Retail. Menus, culinary blocks, dining orders, and kitchen tasks belong to Restaurant's domain and are not mixed with Retail value catalogs. ## Core Framework Integration Restaurant consumes Core features including: * Qualified type IDs and common data models; * Element definitions and frozen read-only views; * Customer variants, behavior tasks, and Work Order extensions; * Server-authoritative state, persistence, and registration lifecycles. ## Development Status Specific culinary recipes, station blocks, and order mechanics will be specified in future milestones. This page defines architectural boundaries for addon developers. Compatibility layers should reside in standalone adapters, cleanly disabling features when optional dependencies are absent. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://eurekabusiness.caiziii.com/eurekabusinesscommunity-en/module-reference/restaurant-module.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.