Observation
What did you see or experience?
Reported experience until the relevant facts are checked.Chapter 03 · Evolving practice
How can residents help Wilbraham understand a decision without turning every observation into an official fact—or every useful digital tool into an official Town system?
Residents can contribute knowledge, memories, photographs, questions, concerns and lived experience through a visible verification and public-process route. CivicSS can organize those contributions and show where input is still useful. It cannot silently convert a contribution into verified evidence, a recommendation, an appropriation, a public record determination or Town authority.
The public promise
The goal is not to produce one person’s version of Wilbraham. The goal is to help Wilbraham recognize itself.
What residents know can complete a decision picture that no filing cabinet or single official can hold alone. A safe participation path lets people contribute what they see, remember, question and care about—then shows how that contribution is protected, checked, answered and carried into the proper public process.
Being heard is not the same as being declared correct. An observation can matter before it is verified. Verification can strengthen evidence without turning it into a recommendation. A recommendation still does not become an appropriation, contract, payment or official result.
The resident journey
From “I noticed something” to “I can see what happened.”
- 1
Notice
A resident sees a place, service, pattern, problem, possibility or missing part of the story.
- 2
Learn
The resident can find the question, decision stage, responsible roles, known evidence and date when input can still matter.
- 3
Contribute
Submit a bounded observation, source, question, memory, photograph, perspective or correction request—with provenance and permission choices.
- 4
Classify and protect
Separate reported experience from source evidence; remove unnecessary personal data; identify public, restricted or review-needed handling.
- 5
Verify
A responsible reviewer checks the source, meaning, date, scope, contradiction and relationship to the decision. Received is not verified.
- 6
Route
Send the question or evidence gap to the person, department, custodian or public process that can actually act on it.
- 7
Deliberate and decide
Authorized bodies discuss and decide through the governing public process—not through a private digital side channel.
- 8
Report and deliver
Show what was recommended, authorized, funded, implemented and accepted without collapsing those stages.
- 9
Learn
Compare the promised purpose with the actual result and preserve what residents and participants should know next time.
What the community can add
Different contributions deserve different evidence labels.
Source
What public or properly supplied record can another person inspect?
Evidence candidate with source, date and locator—not automatically controlling authority.Question
What remains unclear, and who may be able to answer?
Open information need with an owner and response state.Memory
What history or prior decision may otherwise disappear?
Community knowledge that needs attribution, corroboration and context.Photograph
What condition, use, relationship or character does it help us notice?
Visual contribution with date, place, rights and privacy review.Perspective
What do you value, fear losing or believe the current picture misses?
A legitimate human viewpoint—not proof of motive, consensus or fact.Correction request
What appears wrong, incomplete, stale or unfairly represented?
A visible review path; correction requires evidence and preserves change history.“Some residents will contribute historical knowledge. Some will contribute financial insight. Some will notice details others overlook. Some will share memories, photographs, concerns, or hopes for future generations.”
What changes—and what does not
The evidence state can advance. Authority does not appear by accident.
Received
The contribution exists and has a stable identity.
Classified
Its type, provenance, sensitivity and related decision are identified.
Verified or disputed
The claim was checked, corroborated, contradicted or left unresolved.
Accepted for a defined use
An authorized control route allows the evidence to support a particular question or report.
Recommended
An authorized body adopted a position through its governing process.
Decided and authorized
The lawful decision maker approved a defined act, amount, condition or scope.
Implemented and measured
Delivery and actual results are established by later evidence.
Missing is not zero. Reported is not verified. Verified is not accepted for every use. Accepted evidence is not an adopted recommendation. A recommendation is not the decision.
What a safe civic application is
One experience for residents; five separately controlled functions underneath.
Contribution workspace
Prepare a question or contribution; show what will be collected, why, and what should not be submitted.
Administrative review
Completeness, classification, privacy, records, accessibility and routing checks happen before public or official use.
Governed register
Correctable structured records preserve sources, prior values, decisions, status, owners and audit history.
Public-body support
Factual questions, evidence and meeting-packet preparation support deliberation without becoming off-meeting debate, polling or voting.
Public read-only view
Approved fields, sources, formal actions, status and results are understandable without exposing restricted material or implying unfinished work is official.
Demonstrated internal releaseTown Decisions v0.3.0
Seven neutral connected-facilities configurations, twelve common parameters, eighty-four explicit path assessments and twelve governed gaps.
What that provesOrganizing and explanation method
The same evidence can appear in several connected views without ranking a choice or copying it into inconsistent stories.
What it does not proveTown authorization or safe production use
The sealed release is independent, internal, undeployed and unpublished. It has not been approved to collect real municipal submissions.
Controls before real municipal use
A useful interface does not resolve governance, records, law, security or accessibility.
Authority and custody
Name the municipal owner, business owner, system administrator, records custodian, official-copy rules and decision authority before real use.
Records and retention
Define search, export, redaction, retention, legal hold, correction history and production responsibilities.
Privacy and minimization
Collect only what the approved purpose needs; separate public, restricted, security-sensitive and review-needed information.
Public-process boundary
Do not create private deliberation, polling, ranking, serial communication or implied committee positions outside the governing process.
Security and continuity
Use role-based access, authentication, logging, encryption, backups, recovery, vendor review, incident response and separate test/production environments.
Accessibility and alternatives
Keyboard, screen-reader, contrast, error, mobile, zoom, attachment, caption and assistance paths belong in requirements and acceptance—not an afterthought.
These are design and planning controls—not a current legal conclusion. Before official use, the Town would need fact-specific review by the responsible business, records, clerk, accessibility, technology/security, procurement, financial and legal authorities under the rules then in force.
Established, proposed and missing
Where does this capability actually stand?
The learning language, contribution types, evidence-state discipline, authority distinctions, respectful perspective method and a tested internal organizing-app pattern.
A resident-to-public-process participation path, municipal application layers, correction route and connected decision-to-result experience.
Town sponsorship and ownership; approved process and data definitions; records, privacy, retention, security, accessibility and legal decisions; public testing; operational support; and evidence of adoption or results.
How should a contribution move through the system?
- 1
Begin with the Town problem and public purpose, not with CivicSS, a preferred committee, a product or a predetermined solution.
- 2
Accept bounded contribution types such as observation, source, question, memory, photograph, perspective and correction request; label provenance and evidence state at entry.
- 3
Classify, minimize, protect and route the contribution before public display or decision use; preserve what is reported separately from what has been verified.
- 4
Send factual questions and evidence gaps to the responsible owner without creating a private off-meeting deliberation channel for a public body.
- 5
Carry validated information into the lawful recommendation, authorization, implementation and results process; preserve what changed and what the decision taught.
What does this chapter not authorize or promise?
- The municipal-application controls are draft planning guidance, not legal advice, Town policy or an authorization to collect real municipal submissions.
- The current Town Decisions product is a sealed internal independent organizing-and-learning release. It is not deployed, published, official, audited, certified or approved for a Town presentation.
- An independent prototype may use fictional, sanitized or already-public information. Real municipal use requires identified Town ownership, records custody, security, retention, accessibility, procurement and current legal review.
- A resident observation may reveal essential knowledge without becoming an official fact. A formal public process may acknowledge a contribution without adopting its conclusion.
- No page in this Atlas should promise anonymity, confidentiality, deletion, public-record status, Open Meeting Law compliance or legal sufficiency; those determinations belong to current authoritative rules and responsible officials or counsel.
Where can a specialist verify the complete evidence?
- Understanding-Together-Build1.2-PrintFormatted.xlsx, including Community Is Writing, Community Knowledge So Far, Through Your Eyes, Stewardship Dimensions and What We Need Next.
- CSKE-Town-Roles-Spending-Authority-Pass-6.2-Public-Review-Copy-20260826.xlsx and Sherie Atlas Roles.md.
- Municipal Application Development Controls.md, status Draft governance and development guidance, August 22, 2026.
- Codex Town Decision Information and Participation: Start Here, current v0.3.0 release records, source-coverage matrix, QA and working assessment/SWOT.
- Atlas Sherie Overview, site-assessment and feedback records, with Sherie Notes Atlas Defects read last as directed.