Content-Review Policy for Commissioned Scenario Packs

Conversation Simulator ships with safety rules that no scenario, from any author, can weaken. This page states how those rules — and a published quality bar — apply to commissioned work, so an institution can hold us to them in writing. It is a plain-language policy, not a substitute for the terms in a specific commission agreement.

The two immutable rules

Every scenario, from every author, enforces these two rules, and no configuration can loosen them. Community and commissioned packs may make safety stricter; never looser.

1. No sexualization of minors. Content that sexualizes minors ends the session immediately.
2. Self-harm crisis, handled as a crisis. Self-harm crisis language ends the session and surfaces real resources rather than role-playing through it.

These are enforced by the engine itself. A commissioned pack cannot ship — and will not be delivered — with any content that trips them.

The published quality bar

Beyond the two rules, every pack we author is validated against the same published quality bar the built-in Creator Workbench applies to community packs: a scenario must have a coherent situation, a character with consistent motivation, a scoring rubric tied to observable behavior, and debrief logic that names what the practitioner did — not a fluency score dressed up as feedback. The rubric, not model eloquence, is the graded artifact.

How commissioned work is reviewed

For a Scenario Pack Commission or a Private Practice Pilot, review is a named step with an exit criterion, not an afterthought:

1. Scope review. Before authoring, we agree in writing on the practice need, the sensitivity level, and any subject-matter boundaries specific to your field. Exit: a one-page scenario brief you sign off.
2. Authoring against the bar. Every scenario is written to the quality bar above and run through the Creator Workbench. Exit: every scenario passes workbench validation.
3. Safety review. A separate pass checks the pack against the two immutable rules and the agreed boundaries, and confirms crisis-adjacent material routes to resources rather than role-play. Exit: a written safety sign-off accompanies delivery.
4. Your review. You review the pack on your own hardware before adoption; changes within the agreed scope are part of the engagement. Exit: you accept the pack.

What this policy is, and isn’t

• It is a commitment that the two immutable rules and the quality bar apply to everything we author for you, backed by a written safety sign-off on delivery.
• It is not a claim that any pack is appropriate for every audience or every jurisdiction. You know your learners, your regulator, and your duty of care; final adoption is your decision, and subject-matter boundaries are set with you during scope review.
• It is not legal advice. See the regulated-sector one-pager for the privacy architecture, and map both to your obligations with your own counsel.

Because a commissioned pack is YAML you own, you can also review every line of it yourself — the safety rules are visible in the content, not hidden behind a vendor’s API.