Production control note
What is a seating service-code legend?
It maps an opaque user-entered code to exact host-approved operational wording for staff files, while keeping that code and meaning out of guest-facing cards and finder lists.
Do not infer the category
The desk does not decide whether a code refers to a meal, access arrangement, language, service sequence, or another project-specific instruction. Preserve the owner’s authoritative source outside the browser project and label every assumption that remains unverified.
Avoid unexplained abbreviations
Every code used by a guest record must exist in the current legend so recipients are not asked to guess. Review the result as production evidence, not as a recommendation or professional approval; the responsible people remain accountable for the decision.
Review the latest legend
A changed meaning can affect operations even when no guest-facing card changes, so the comparison tracks it separately. Carry this limitation into the proof and handoff so a fresh recipient knows what changed, what was checked, and what still requires human confirmation.