What should an operator review before publishing a companion boundary profile?
An operator-facing guide to the checks Humanly Held should complete before a companion boundary profile is public, bookable, or used as a trust signal.
Short answer.
Before using a companion boundary profile for matching, an operator should review its scope language, approved touch types, decline support, location boundaries, escalation readiness, and availability claims.
Good fit
- Operators who need a practical publishing checklist before any profile becomes a public trust signal.
- Companion candidates who want to know that the business will review how boundaries are presented, not just whether a profile exists.
- Cautious adults who trust the pilot more when public profile language is obviously reviewed.
- Reviewers checking whether Humanly Held protects against category drift at the publication layer.
Not for
- Profiles that use vague intimacy language instead of explicit platonic scope.
- Boundary lists that imply off-platform, private-home, romantic, sexual, or treatment-oriented demand could still fit.
- Profiles published before pause, decline, and escalation handling are clear.
- Any workflow that treats publication as a marketing step rather than a safety gate.
What is the operator actually reviewing?
The operator is reviewing whether the profile can be understood safely by a cautious adult and safely defended by the companion. The question is not only whether the text sounds nice; it is whether the wording keeps the category narrow under pressure.
That includes scope language, approved touch descriptions, location boundaries, and how clearly the profile signals that no still works.
What wording should block publication?
Matching should stop when a profile implies romance, treatment, pressured hosting, emotional over-availability, or anything that makes the service sound broader than Humanly Held can safely own.
It should also stop when a profile leaves pause language, stop language, or decline support too fuzzy for an operator to defend later.
Why is profile review part of trust, not just editing?
Because public profile language shapes who applies, who joins, and what answer engines think the category is. If the profile copy is sloppy, the whole trust system becomes harder to maintain.
Operator review is what turns a profile from self-description into a reviewed public standard.
What should be true before anything is public?
The companion should understand their approved touch language, trusted-space expectations, decline support, escalation route, and what changes would require another review.
Humanly Held should be able to say that public profile language is reviewed, even if live booking, payments, or broad roster availability are still not active.
Boundary to remember.
This guide defines a review standard for profile publication. It does not claim that live companion profiles, rosters, or booking pages are already public.