Production control note
How should same-table and different-table reminders work?
They should record an explicit host-authored pair and reason note, warn when the current assignment conflicts, and never automatically move a guest, rank relationships, or claim that satisfying the recorded pair makes the plan suitable.
Warnings preserve agency
An automatic solver would need to choose which competing preference loses. This desk leaves that judgment with the responsible people. Preserve the owner’s authoritative source outside the browser project and label every assumption that remains unverified.
A missing reminder is not permission
Unrecorded context may matter more than the visible pairs. Review the complete plan outside the tool. Review the result as production evidence, not as a recommendation or professional approval; the responsible people remain accountable for the decision.
Use neutral wording
Do not encode sensitive reasons when an operational reminder is sufficient. Carry this limitation into the proof and handoff so a fresh recipient knows what changed, what was checked, and what still requires human confirmation.