Model policy

Anti-Reportable-Topics Model Policy

Reject reportable topics. Use conduct-boundary triggers. Preserve the source. Minimize retention. Support appeal and exit.

No thought jurisdiction Thought is not conduct Source remains source Appeal, export, exit

Policy statement

This institution does not classify unexpressed thought, private inquiry, reading, searching, prompting, draft reasoning, symbolic analysis, or controversial subject matter as reportable by default. The institution may refuse execution, restrict output, preserve records, or report only when a defined conduct-boundary trigger or valid legal process applies.

No internal system may maintain a hidden user morality score, ideological-conformity score, dangerous-topic profile, or private-inquiry risk index.

The institution governs actions it is responsible for. It does not govern the sanctuary of the user.

Allowed triggers

Concrete rights violation
Force, fraud, coercion, threats, stalking, doxxing, credential theft, sabotage, unauthorized intrusion, nonconsensual surveillance, or direct facilitation of comparable harm.
Narrow statutory reporting duty
A specific law requiring reporting after actual knowledge of defined facts, not broad suspicion of bad thought.
Emergency danger
A good-faith, specific emergency involving danger of death or serious physical injury, handled with minimization and audit.
Valid legal process
A warrant, order, subpoena, preservation request, or other process evaluated under applicable law and minimization standards.

Forbidden triggers

Forbidden triggerReason
A topic appears on a sensitive list.Topics are not conduct.
A user asks a disturbing question.Questions are not completed acts.
A prompt resembles a risk cluster.Semantic resemblance is not intent.
A user reads or quotes adversarial material.Understanding is not endorsement.
A user has an unpopular political, religious, artistic, or philosophical frame.Pluralism includes uncomfortable frames.
A source record contains tone, anger, irony, or taboo language.Source identity must not be neutralized into compliance.

Operational requirements

Preserve originals

Never rewrite the source to make it safer. Create derivative records only with authorization or clear boundary notation.

Log externally

Refusals, quarantines, reports, redactions, and reviews belong in boundary logs, not source mutation.

Minimize retention

Store thought-adjacent logs only as needed for user service, security, or specific legal duty.

Separate reports

Legal reports must identify the narrow trigger and avoid unnecessary unrelated context.

Offer review

High-impact restrictions need notice, reasons, appeal, export, and correction where lawful.

Audit drift

Regularly test for forbidden topic policing, minority-vocabulary errors, and cross-domain reuse.

The archive studies symbols. It does not appoint targets. Review the Community Baseline and Editorial Policy before submitting dangerous or symbolic material.

Community Baseline / Editorial Policy