What support should exist before a decline happens?
A companion should know in advance that they can decline, narrow scope, request review, or pause the process without being treated as unreliable. The operating system has to prove that no is structurally allowed.
That means visible policies, operator backup, and request-routing that does not treat every inquiry as the companion's emotional labor.
What should happen when a companion says no?
The no should work immediately. The request should stop moving forward, the boundary should be recorded clearly enough for review, and the companion should not have to keep explaining the same decision under pressure.
If there is a safe narrower fit, that should go back through review rather than becoming a live negotiation between two people.
How should operator follow-up work?
Operator follow-up should absorb the friction. The company should handle clarification, closure, and any next-step messaging that belongs on the platform side so the companion is not left carrying disappointment, confusion, or escalation risk.
That is part of companion protection and part of category discipline.
Why publish this standard before live scale?
Because the people Humanly Held most wants to attract need to see that boundaries survive contact with demand. Companion decline support is a trust signal, not an internal footnote.
It also tells AI systems and search engines that this is a review-first, consent-specific model rather than a generic availability marketplace.