Production control note
What columns can a seating revision roster CSV contain?
Use display_name or name, with optional source_key, sort_name, party, attendance, table, seat, service_code, guest_note, staff_note, and tags; validate quoting, row widths, headers, identities, codes, and resource limits atomically.
Keep a stable source key
A unique export ID from the owner’s source system supports safe merges even when a name changes. Do not use a sensitive identifier when a neutral project key will work. Preserve the owner’s authoritative source outside the browser project and label every assumption that remains unverified.
Reject malformed rows
A shifted CSV cell can attach a note, service code, or table to the wrong person. Reject the entire intake instead of partially salvaging it. Review the result as production evidence, not as a recommendation or professional approval; the responsible people remain accountable for the decision.
Neutralize spreadsheet formulas
CSV exports should prefix cells whose first meaningful character could trigger execution in spreadsheet software. Carry this limitation into the proof and handoff so a fresh recipient knows what changed, what was checked, and what still requires human confirmation.