Trendzion is a community devoted to the spoken and written words of leaders of The Church of Jesus Christ of Latter-day Saints. Discussion here should reflect that devotion — not as a loyalty test, but as an editorial frame that keeps the conversation grounded in reverence for the source material and for one another.
These standards are the basis on which every comment is reviewed. They are not rules of belief — you are not required to agree with the Church to post here. They are rules of tone, posture, and subject.
The nine pro-positions
We are, publicly and unapologetically:
- Pro Latter-day Saints — respectful of members, missionaries, leaders, and lay.
- Pro Zion — honoring the gathering, the covenant community, and the shared aim of a consecrated people.
- Pro life — affirming the sanctity of human life at every stage.
- Pro modesty — in dress, speech, and intent.
- Pro service — volunteer labor, ward and stake participation, quiet acts, the ministry.
- Pro charity — helping the poor and needy; the first and greatest public expression of our faith.
- Pro Jesus — Christ as the Redeemer and the Head of the Church.
- Pro God — Heavenly Father, the plan of salvation, and reverence for Deity.
- Pro celebration — joy in faith, joy in community, joy in the good news.
What we do not allow
Posts that violate the community standards fall into these categories:
- Hostility toward the Church, its leaders, or its doctrine. Respectful disagreement is welcome. Sustained or vulgar attacks are not.
- Vulgarity, profanity, or crude language. Clean speech is a standard we hold to; coarse language moves a post toward moderation.
- Sexual content. None, ever, regardless of era or framing.
- Calls for violence or self-harm. None, ever.
- Doctrinal hostility — content whose purpose is to tear down faith rather than engage it. A question honestly asked is not hostility; a slogan deployed to mock is.
- Personal attacks and doxxing. Directed cruelty toward named members of the community or toward named Church figures.
- Spam, commercial links, and off-topic advertising. This is a discussion space, not a marketplace.
- Sustained hateful rhetoric — racial, ethnic, gender-based, or anti-religious (including rhetoric directed against faiths other than ours).
What happens when a post violates these standards
Trendzion uses two views: Liberty (the default) and Captivity (moderator-flagged).
- Clean posts appear in Liberty view, visible to everyone.
- Posts with narrow, surgically-masked issues (a single slur or crude word) appear in Liberty view with the offending span masked.
- Posts with more than one violation, or a whole-post violation, are moved to Captivity view.
- Deeply hostile or doctrinally-attacking posts are moved directly to Captivity view.
Captivity view exists because removing these comments entirely felt dishonest — they are part of the community conversation. Making them visible only behind a deliberate maturity gate felt like the right compromise. Trendzion does not host unsafe content in either view.
Appeal and edit
If your post is masked or moved to Captivity, you may edit it. The edit goes to a human moderator review queue. There is no SLA and no automated re-opening. A moderator reviews and either restores your comment to Liberty, keeps it masked, or deletes it. This is intentional: the editing path exists so you can make your argument again, better; it does not exist as a retry loop.
Banning
Repeated violations revoke posting privileges. A banned user can still read. Past comments remain where they are (masked stays masked, clean stays clean). We do not retroactively hide the history of a banned user — accountability matters.
Who enforces these standards
- The automated classifier (Moonshot Kimi-K2-Turbo in test mode; Anthropic Haiku 4.5 in production) reviews every new post and assigns a verdict.
- Human moderators review edits, appeals, and any post a user reports. Moderators can override the classifier in either direction.
- Administrators and the super admin can revoke moderator or admin status, create new accounts at any role, and edit this document.
Version and change history
This document is version-controlled alongside the site code. Every change ships through review; the live site renders the canonical copy at /community-standards.html.