Peaceful Chats. Real Answers.
One Community Standard for Veritatis Splendor
Our community chats are where we plan gatherings, ask for help, share good news, and stay connected. They should be places we enjoy belonging to.
But when disagreements become endless debates, everyone gets pulled into them. Announcements get buried. Conversations become tense. Neighbors feel pressure to take sides.
Muting the chat means missing updates. Leaving means losing a connection to the community. Staying means continuing to scroll through a conflict you never chose to join.
We shouldn’t have to disconnect from our neighbors to get a break from an argument.
At the same time, people raising concerns deserve a meaningful answer. Simply telling them to “take it elsewhere” accomplishes little unless there is somewhere to take it—and a clear commitment to respond.
As Veritatis Splendor grows, we need a structure that protects both: our ability to enjoy community life and our ability to raise concerns.
An Established Democratic Approach—Adapted for Our Community
Democratic institutions already use formal petitions—written requests backed by signatures—to give public concerns a defined path to an answer or hearing.
- In the United Kingdom, petitions on the official platform receive a government response at 10,000 signatures. At 100,000, they are considered for parliamentary debate. (petition.parliament.uk)
- In the European Union, citizens’ initiatives that meet the qualifying requirements receive an opportunity for a public hearing and a reasoned response. The Commission must explain its position, but it does not have to propose the legislation requested. (citizens-initiative.europa.eu)
We can adapt that principle here: give concerns a structured hearing without requiring leaders to agree with every demand.
Pair that with clear boundaries for our shared chats, and people have a dependable way to seek answers without making every neighbor participate in every dispute.
What We Ask the Charity, Developer, and POA to Adopt
The same commitments apply to all three entities. Once adopted, the process works like this:
1. Put the concern in writing and invite support.
You create an online petition explaining:
- The community concern.
- The entity responsible.
- The question or action you want considered.
You share a brief notice and signing link in the community chat, along with an invitation to a separate discussion.
Interested neighbors participate there. Everyone else continues enjoying the general chat without following the debate.
2. Ten verified signatures require a public answer.
When the petition reaches 10 verified signatures from eligible constituents, the responsible entity must publish a formal written response within 15 business days.
The response addresses the concern, explains the entity’s position, and identifies any intended next steps. An acknowledgment alone is not enough.
3. Twenty-five post-response endorsements require a public town hall.
If the response leaves the concern unresolved, supporters can request a town hall by gathering 25 verified endorsements after the response is published.
- The underlying petition stays the same.
- Original signers can endorse again.
- The threshold is 25 people total—not 25 additional people.
- Earlier signatures do not automatically count toward this stage.
The responsible entity must hold the town hall within 30 calendar days of verification, with:
- At least 10 calendar days’ public notice.
- An invitation to the whole community.
- A neutral moderator.
- A fair opportunity for questions and differing viewpoints.
4. Close with an answer and follow-through.
Within 10 business days after the town hall, the entity publishes its decision or conclusion, its reasons, and any next steps. Commitments are tracked publicly.
Each entity retains its decision-making authority. It can agree, change its approach, propose an alternative, or decline the request.
A guaranteed process—not a guaranteed “yes.”
Disagreement alone does not automatically trigger another town hall on the same matter. New material information, changed circumstances, or unfulfilled commitments provide grounds to request renewed consideration.
Share the Petition. Keep the Debate Out of the General Chat.
Alongside this process, general community chats managed by all three entities adopt the same boundaries:
- Petition invitations are welcome: a brief, neutral notice, signing link, invitation to a separate discussion, and one reminder.
- Debate happens separately: arguments, rebuttals, and discussion of the petition’s merits stay out of the general chat.
- Official updates remain available: brief notices and links to responses, town halls, and conclusions are welcome without restarting debate.
- Personal conflicts are handled privately: moderators remove or redirect personal disputes.
- The rules apply equally: supporters, opponents, and entity representatives follow the same boundaries.
These boundaries begin alongside the functioning petition process. No one needs signatures to speak privately with neighbors or raise a concern directly with an entity.
Help Us Grow as Neighbors
A growing community needs more than goodwill. It needs shared expectations that make room for different views without dividing everyday life into competing sides.
By signing, I ask the Charity, Developer, and POA to adopt this shared petition process and accompanying group-chat standards.
I support:
- Community chats we enjoy belonging to.
- A dependable path to meaningful answers.
- The freedom to choose which debates we join.
- The same standards for everyone.
My signature supports this process—not every future petition or any particular outcome.
Let’s give concerns a place to be heard—and our community chats room to be enjoyable again.
