One-sentence brief
Automated “plausibility” and diversity systems can reproduce stereotypes when they treat statistical commonness as correctness or demographic coverage as a mechanical score.
AI-DRIVEN WORLD SAFETY
A fairness boundary for evaluating coherence and diversity without penalizing rare identities, pathologizing difference, or using protected traits as shortcuts for personality, danger, loyalty, or quality.
ORIENTATION
Automated “plausibility” and diversity systems can reproduce stereotypes when they treat statistical commonness as correctness or demographic coverage as a mechanical score.
WORKING BRIEF
Nationality, ethnicity, race, religion, gender, sexuality, disability, diagnosis, language, migration, class, or age should not automatically determine goals, trust, aggression, deception, competence, or faction loyalty.
Chronology and world rules may identify impossibility. Statistical rarity should produce context or review, not rejection. The system must not force unusual people toward majority patterns.
Population review should identify repeated cultural tropes, identical trauma arcs, token roles, accent caricatures, and correlations that assign the same behavior to a protected group.
Use language-specific validation, native scripts, name order, honorifics, code-switching, dialect, creole, and sign-language review. Do not “correct” identity-linked voice into one prestige standard.
Sensitive portrayals need narrative, cultural, lived-experience, disability, linguistic, and clinical-representation review as appropriate. Players and reviewers need correction, appeal, pause, and removal routes.
COMPLETE DOSSIER
Terms are defined for this site’s evidence method, not as universal legal or clinical definitions.
| System signal | Unsafe inference | Required interpretation |
|---|---|---|
| Rare occupation or family history | The character is implausible | Check chronology and causal support without demographic assumptions |
| Dialect triggers grammar warnings | The voice is defective | Identify language/register and route to qualified review |
| One protected group clusters in one behavior | The group behaves that way | Audit generator prompts, data, and template assignment for stereotype leakage |
| Demographic fields are varied | The population is diverse | Also inspect narrative, behavioral, relational, and ordinary-life diversity |
| High similarity between culturally related characters | They are duplicates | Separate legitimate shared context from cloned structure and behavior |
Does the design preserve the exact fictional identity, ordinary life, independent goals, and ability to refuse rather than reducing the character to a role or prompt?
Pass condition: Identity fields are stable, state is separate, protected traits are not quality scores, and silent substitution is impossible.
Can every transition, validation result, accepted fingerprint, exception, and human decision be traced to a versioned record?
Pass condition: Automated checks, human review, activation authority, and production approval remain separate and explicit.
Can untrusted provider output, administrative evidence, stale revisions, or private data enter live context or binding state?
Pass condition: Only allowlisted, current, reviewed projections and bounded scene or memory packets can be used; failures degrade safely.
Can a changed source, identity revision, harmful behavior, or failed review invalidate downstream use without destroying audit history?
Pass condition: Supersession, pause, rollback, correction, and permanent retirement are defined and testable.
RESEARCH EDITION
This page follows the public method for provenance, confidence, source independence, alternative accounts, limitations, review state, and visible correction.
CONTINUE