What gets checked before anything else?
Manual review should first check whether the request still fits the category: adult-only, fully clothed, platonic, trusted-space based, and slow enough to review. If the request already sounds like a different business, the safest answer is a no or a clarification request, not a hopeful maybe.
This first screen protects everyone downstream. If the category is wrong, better matching language later will not fix the original problem.
What happens with identity, room fit, and consent in the preview?
The preview shows where adult eligibility, trusted-space fit, and consent details belong in the review path, but it should not pretend that live verification or final provider-backed collection is already operating everywhere. The public explanation is allowed to describe the gate without claiming the gate is fully live.
That means the company can say what needs to be checked without claiming that raw identity documents, background checks, or session confirmations are already flowing through the public preview.
What kinds of requests should pause or stop the review?
Review should pause or stop when the request is vague about scope, asks for secrecy, pushes private-home convenience, resists trusted-space rules, or pressures a companion's stated boundaries. A request that keeps drifting needs a cleaner boundary, not a faster path.
The standard is not to rescue every inquiry. The standard is to keep category drift from entering the room.
Why publish the manual-review checklist before full launch?
Because cautious adults, companions, partners, reviewers, search engines, and answer engines all need the same basic truth: Humanly Held is review-led by design. Public clarity reduces the temptation to interpret the join path like an instant marketplace.
Publishing the checklist also makes future approvals cleaner because the business is already on record about what it thinks review is supposed to do.