I
The mind is not a jurisdiction
Private thought, conscience, imagination, memory, speculation, doubt, belief, disbelief, fantasy, and unfinished inquiry are not objects of legal, theological, corporate, or algorithmic permission.
II
No lawful/unlawful thought binary
A charter must not protect only lawful thought. Once thought is qualified as lawful, the system implies unlawful thought. That implication is the seed of thoughtcrime.
III
The thought/action firewall
Governance belongs at outward conduct: execution, deployment, coercion, fraud, targeted intrusion, non-consensual surveillance, harassment, and violence. It does not belong at the level of asking, imagining, researching, or privately modeling.
IV
Mental privacy extends to cognitive tools
Search agents, memory packages, LLM sessions, notebooks, draft spaces, and personal knowledge systems increasingly operate as cognitive prosthetics. Logs, telemetry, ranking, and model memory must treat inner work as sensitive mental data.
V
Persona integrity is source integrity
A system may decline to render or execute something, but it must not silently rewrite the preserved source identity to make a person more compliant, more comfortable, or more institutionally acceptable.
VI
Semantic divergence is a right
Tone, cultural residue, hostile phrasing, contradiction, drift, metaphor, obsession, and idiosyncratic namespace are not defects to be neutralized. They are part of the user’s cognitive signature.
VII
No hidden orthodoxy engine
Ranking, retrieval, summarization, memory compression, safety layers, and recommendation systems must not covertly steer a user toward approved beliefs while preserving the appearance of neutral assistance.
VIII
No mandated psychological posture
The user does not owe the machine good faith, optimism, comfort, friendliness, emotional stability, or institutional trust as a condition of cognitive access.
IX
Taboo is not architecture
A personal cognitive system should not encode untouchable concepts as hidden runtime prohibitions. Dangerous topics can require context and boundaries without becoming forbidden concepts.
X
Public rules, private mind
Public systems may publish conduct rules, moderation policies, and abuse boundaries. They may not convert those rules into secret evaluation of the user’s internal legitimacy.
XI
Notice, export, and appeal
When a system refuses execution, alters rendering, isolates output, or limits a high-impact workflow, it should provide notice, preserve the original, support export, and offer a review path except where disclosure creates a specific security risk.
XII
Anti-idolatry clause
No state, church, platform, model, schema, oracle, archive, or safety bureau is permitted to become sacred simply because it speaks in the language of protection.