CivilGood
Presentation edition 0.1

You do not have to solve the whole problem to make it solvable.
CivilGood explores how a community could connect people who need a hand with people willing to offer one, without turning help into a payment, score, or debt.

Editorial reading of the social purpose
Editorial vision: CivilGood could help communities see needs and spare capacity together, then choose a useful small contribution, host a shared session, or be honest when more support is needed. The idea is to make mutual help easier to coordinate while keeping it free, voluntary, and human.

A small exchange of need and time
[implemented]
Today’s prototype lets someone post either a request for help or an offer of help. It uses a category, optional tags, a broad area, and an availability window to show possible matches. A match is an invitation to look more closely, not an introduction or a promise.
How: Listings can be paused, resumed, or closed by the person who created them. Expired listings leave the board. The prototype does not expose contact details, arrange a meeting, or certify anyone as safe.
Possibility: A small, clear starting point could let a community learn what kinds of coordination are useful before it takes on more responsibility.
Tension: Making needs visible is only one part of helping. People still need choice, trust, time, and a way to stop.
Sources: foundation, listing-model, matcher

A match is a possibility
[implemented]
The current matcher looks for an active request and offer with the same category, broad area, and some overlapping availability. Shared tags add to its explained score. It does not know how long the task takes, how many people are needed, or whether the need was resolved.
How: A high score means that listing fields fit the current rules. It is not a measure of a person, trust, commitment, or success.
Possibility: Future experiments could show the actual pieces a task needs and leave any missing piece visible, so nobody mistakes a promising fit for a finished plan.
Tension: More planning can make help clearer, but too much planning can burden the people already coordinating it.
Sources: matcher, assessment

I can do this part
[proposed]
One experiment would let a requester or host describe a few bounded pieces of a need. Someone might offer one short, clearly described part without taking responsibility for the whole task. The plan would show what is agreed and what is still missing.
How: The assessment proposes starting with at most three pieces: one helper, a pair, or a helper plus a resource. Each piece would have clear limits and timing. A resource loan would need agreed care, return, and damage terms before real use.
Possibility: Someone with only a little time could still see a contribution that matters, while the requester keeps control of the plan and its boundaries.
Tension: Partial work can help, but dependencies and cancellations may make coordination harder. Unfilled pieces must stay visible without making anyone feel responsible for them.
Sources: assessment

Bring a common need into one shared session
[proposed]
Another experiment would let a willing community host notice that several people want similar help and offer an opt-in session in a suitable shared place. A general device-help session is one illustration: people could learn basic settings while keeping their own devices and credentials under their control.
How: This is a future coordination idea. It depends on a willing host, a suitable venue, enough capacity, and a topic that can be handled within clear boundaries. It is not a feature of the current listing prototype.
Possibility: A hosted session could make help easier to reach and reduce the need for private one-to-one encounters.
Tension: A group format may suit common questions but leave unusual needs unanswered. People should be able to decline and still have another route where one exists.
Sources: assessment, safety-proposal

Safety is a community responsibility
[proposed]
The current prototype stops at showing a possible match. The separate safety design describes decisions and controls that would need to be agreed, built, staffed, and reviewed before any real-world pilot. A matching score cannot decide whether a person or meeting is safe.
How: The proposal puts consent, easy withdrawal, limited disclosure, accountable human decisions, reporting, and appeal routes at the centre. Until those operating arrangements exist, the prototype should not be extended into real introductions.
Possibility: Communities could shape help around clear task boundaries and shared responsibility, so people are not asked to rely on a score or a stranger’s promise.
Tension: Good intentions do not remove risk. Safety takes people, policies, resources, and accountability over time.
Sources: foundation, safety-proposal, assessment

Learn from what was actually helpful
[proposed]
If a separately approved pilot ever happens, the assessment suggests learning from whether requesters or hosts confirm that a need was resolved, how much coordination it took, and whether asking and helping felt manageable. Unresolved, cancelled, expired, and unknown outcomes should remain distinct.
How: These are proposed learning measures, not current data or results. A simulation with invented cases can explore a design question; it cannot establish demand, impact, or safety.
Possibility: Careful learning could help a community keep a useful simple process or drop an elaborate one that does not help.
Tension: A small experiment can guide another experiment, but it cannot prove that a model works everywhere or that nobody was harmed.
Sources: assessment, safety-proposal

PRINCIPLES
Help is freely offered
No payment, reward, credit, public reputation, or repayment is part of the idea. Offering help never creates a debt.
Small efforts can matter
A contribution can be useful without being the whole answer. Any unfinished part stays clear, and no one is pressured to fill it.
People keep their choice
A person can ask, offer, pause, or withdraw. A community’s coordination work should not turn into a judgement of anyone’s character or worth.
Safety needs accountable people
Software can explain a possible fit. It cannot certify a person or encounter as safe, replace human responsibility, or settle an appeal.

ILLUSTRATIVE SCENARIO: A few hands for the community garden
An illustrative future exercise: a group is preparing shared garden beds. Explore whether a bounded plan helps, while leaving gaps and safety conditions visible.
Start: garden-start

garden-start: What is the first useful step?
Imagine a community group wants to prepare its shared beds. No real request or volunteer is represented here.
How should the group frame the work?
Choice: Break it into a few bounded pieces
Bed preparation, tools, and labels become separate needs.
Possible next: People could choose one piece that fits their time.
Still unresolved: Someone must check how those pieces depend on one another.
Continue at: garden-plan
Choice: Start with one simple ask
The group focuses on the most useful first task.
Possible next: A smaller request could be easier to understand and host.
Still unresolved: The rest of the preparation may remain unfinished.
Continue at: garden-simple

garden-plan: How much of the plan should be open?
The group has sketched a few pieces, but a sketch is not a commitment and a match is not proof that the work is feasible.
What should people see next?
Choice: Keep independent work separate from dependencies
The group can see which work might stand on its own.
Possible next: A bounded task could proceed if its host confirms the conditions.
Still unresolved: The wider plan stays incomplete until dependent needs are met.
Continue at: garden-independent
Choice: Show every missing piece clearly
Tools and labels remain visibly unconfirmed.
Possible next: A later volunteer could see a specific useful gap.
Still unresolved: The group may need to simplify or postpone some work.
Continue at: garden-gaps

garden-simple: Who could hold the boundaries?
The group could keep the ask small, while deciding who will make sure the place, task, and timing are suitable.
Which next step fits the group?
Choice: Ask whether a host can lead a shared-space task
The task stays in the group’s shared garden setting.
Possible next: People could take part together if the host and conditions are ready.
Still unresolved: The plan depends on an accountable host and agreed boundaries.
Continue at: garden-hosted
Choice: Ask the host to narrow the task first
The group checks what is actually needed and suitable.
Possible next: A clearer, smaller request could be easier to coordinate.
Still unresolved: The group waits while the details are clarified.
Continue at: garden-clarify

garden-independent: Can one piece stand on its own?
The group has separated an independent task from the rest. It still needs a host to confirm that the task and setting are appropriate.
What should happen if conditions are checked?
Choice: Keep the task within the confirmed group setting
Only that bounded piece is treated as ready to plan.
Possible next: It could be useful even if the wider garden plan remains open.
Still unresolved: The other pieces still need separate decisions and capacity.
Continue at: garden-ready
Choice: Pause until the conditions are clear
No contribution is treated as ready before the host confirms it.
Possible next: A later, clearer plan could make participation easier.
Still unresolved: The garden work may wait or remain undone.
Continue at: garden-paused

garden-gaps: What should the visible gaps invite?
The open pieces are information for the group, not a message that someone owes them help.
How could the group respond?
Choice: Leave the gaps open without reminders
People can choose freely whether any piece suits them.
Possible next: A suitable offer may arrive later without pressure.
Still unresolved: There is no promise that the full plan will be completed.
Continue at: garden-open
Choice: Redesign around the one confirmed task
The group removes pieces that depend on unavailable tools or help.
Possible next: A smaller activity could still be useful.
Still unresolved: The original goal may need to wait for another occasion.
Continue at: garden-small

garden-hosted: Is the shared task ready to host?
A shared setting may reduce some uncertainty, but the group still needs a willing host and agreed limits.
What if those conditions are checked?
Choice: Plan only within the host’s confirmed scope
The proposed activity stays inside its agreed boundaries.
Possible next: People could join a clear task together.
Still unresolved: This says nothing about unplanned work or the wider need.
Continue at: garden-ready
Choice: Wait if the host or scope is missing
The group avoids treating an uncertain gathering as arranged.
Possible next: The group could revisit the idea when conditions improve.
Still unresolved: The task is postponed and may stay unresolved.
Continue at: garden-paused

garden-clarify: What does clarification make possible?
A host can help the group choose a task that fits its time and setting, or decide that it needs more support.
How should the group use that information?
Choice: Keep one clearly bounded task
The group sets aside parts it cannot responsibly plan now.
Possible next: One piece could remain useful without claiming the whole need is met.
Still unresolved: Some garden preparation stays undone.
Continue at: garden-small
Choice: Leave the need open for more support
The group records its uncertainty without creating pressure.
Possible next: Another appropriate source of help may be considered.
Still unresolved: There is no immediate plan for the work.
Continue at: garden-open

garden-ready: A bounded task could be planned
In this imagined path, the host has confirmed a suitable scope and people can decide whether to join. This is a possible plan, not a report of real signups or completed work.
Possible ending: One garden task may be ready for a separately approved future coordination process.
Still unresolved: The wider garden need, participation, safety arrangements, and actual outcome remain unknown.

garden-paused: The group waits for clearer conditions
In this imagined path, the group chooses to pause rather than invite people into an unclear task.
Possible ending: No gathering is arranged through this scenario.
Still unresolved: The work remains undone or unknown until the group finds a suitable next step.

garden-open: The remaining need stays visible
In this imagined path, the group keeps the gap clear and leaves people free to respond or not.
Possible ending: A future contribution could still be considered if it fits.
Still unresolved: No one has committed to the open work, and the original goal is not confirmed as complete.

garden-small: The group makes the goal smaller
In this imagined path, the group chooses one useful piece that fits its known capacity.
Possible ending: A smaller activity could be planned within the host’s boundaries.
Still unresolved: The remaining garden work stays outside this plan and may need another source of support.

ILLUSTRATIVE SCENARIO: Could a shared device-help session work?
An illustrative future exercise: a host hears that people may want basic device guidance. Choices explore consent, scope, and capacity without collecting real requests or credentials.
Start: device-start

device-start: How could a host learn what people want?
Imagine a community host thinks a shared session might help with everyday phone questions. This example contains no real participants, requests, or venue details.
How could interest be explored?
Choice: Invite people to share a general topic privately with the host
The host can look for common themes without publishing personal stories.
Possible next: A general session may fit if people choose to share similar topics.
Still unresolved: The host still needs consent, care, and time to handle the information.
Continue at: device-private-topics
Choice: Offer a general opt-in session idea
People can decide for themselves whether the topic suits them.
Possible next: A clear invitation could find enough shared interest.
Still unresolved: An open invitation may not reveal whether a host or capacity is available.
Continue at: device-open-session

device-private-topics: What kind of help is being requested?
The host has only voluntary, general topic information. The group should never ask people to reveal passwords or hand over account control.
Which boundary fits the topics?
Choice: Keep the session to general settings and accessibility features
The possible session has a clear learning topic.
Possible next: People could try steps themselves on their own devices.
Still unresolved: Some individual problems may not fit a group lesson.
Continue at: device-general-scope
Choice: Set aside account recovery or credential requests
The host does not ask anyone to share private access details.
Possible next: The host could point toward a suitable existing support route.
Still unresolved: A person with a sensitive problem may still need help elsewhere.
Continue at: device-sensitive-boundary

device-open-session: Is there enough shared capacity?
An opt-in invitation may reveal interest, but it does not by itself provide a host, a room, or appropriate support.
What should the organizer check?
Choice: Check that a host and suitable venue are available
The session is considered only if someone can own the boundaries.
Possible next: A shared session could be proposed when capacity is real.
Still unresolved: Without that capacity, interest alone is not enough.
Continue at: device-capacity
Choice: Wait if interest or support is too limited
A thin response is not treated as a failure by any participant.
Possible next: The organizer could revisit the idea when conditions change.
Still unresolved: People may need another route for now.
Continue at: device-thin-interest

device-general-scope: Can the learning stay within its scope?
A general session might explain common settings while each person remains in control of their own device.
What should happen when a question goes beyond that scope?
Choice: Keep the session to general guidance people can try themselves
The group can discuss a shared topic without taking anyone’s credentials.
Possible next: The session could be useful for common questions.
Still unresolved: It may not solve an individual account or device problem.
Continue at: device-session-possible
Choice: Set aside questions that need private access or specialist help
The host keeps the group session within its stated limits.
Possible next: The general session could continue while another route is considered.
Still unresolved: Some questions remain unresolved.
Continue at: device-session-limited

device-sensitive-boundary: What if someone needs more private support?
A community session should not turn into a request for passwords, private messages, or control of a device.
How can the host respond?
Choice: Offer an optional signpost to an appropriate support service
The person can choose whether to follow that route.
Possible next: A suitable service may be better placed to help.
Still unresolved: The host cannot promise that another service is available.
Continue at: device-referral
Choice: Leave the issue open when no suitable route is known
The host explains the session’s limit without asking for private access.
Possible next: A future, better-supported route may be considered.
Still unresolved: The immediate need stays unresolved.
Continue at: device-postponed

device-capacity: What if the host and place are available?
A willing host and suitable venue could make a future group session possible, subject to separate safety and operating decisions.
What should the organizer confirm?
Choice: Set a clear topic and capacity before inviting people
The proposed session has a bounded purpose and owner.
Possible next: People could decide whether to opt in.
Still unresolved: The plan still needs real consent and operating approval.
Continue at: device-session-possible
Choice: Pause until the host can support the session
The organizer avoids treating a room or invitation as enough by itself.
Possible next: The idea could return when responsibilities are clear.
Still unresolved: The session does not happen now.
Continue at: device-postponed

device-thin-interest: What if a group does not form?
A quiet response says little about the worth of anyone’s need. The organizer should not publish a roster or pressure people to join.
What is a respectful next step?
Choice: Offer an optional route through the host if one exists
A person can ask for an individual signpost without joining a group.
Possible next: An existing service or partner may be a better fit.
Still unresolved: The host may not know a route that can meet the need.
Continue at: device-referral
Choice: Wait for a session to make sense without collecting more details
The organizer leaves participation voluntary and the roster private.
Possible next: A future session may be possible if a host and capacity emerge.
Still unresolved: No immediate group help is planned.
Continue at: device-postponed

device-session-possible: A general session could be proposed
In this imagined path, a host offers a bounded group lesson and people can choose whether to attend. No device is taken over and no credentials are requested.
Possible ending: A future, separately approved session may be worth planning.
Still unresolved: There are no actual attendees or results here. Staffing, consent, venue, accessibility, and safety arrangements remain to be decided.

device-session-limited: The group session stays within a smaller scope
In this imagined path, the host keeps the general lesson and leaves private or specialist problems outside it.
Possible ending: A limited group session may still be useful to some people.
Still unresolved: Questions set aside remain unanswered unless another appropriate route exists.

device-referral: A person may choose another support route
In this imagined path, a host can offer an optional signpost without making the group session responsible for private account access.
Possible ending: The person keeps the choice to seek another form of help.
Still unresolved: Availability and suitability of any outside support are unknown.

device-postponed: The session waits for better conditions
In this imagined path, the organizer waits for an accountable host, a useful scope, or enough capacity.
Possible ending: No session is arranged through this scenario.
Still unresolved: The need remains open until a suitable support option is found.

BOUNDARIES
No value ledger
The product direction excludes payments, tips, credits, rewards, cryptocurrency, public reputation scores, and any expectation that someone must give back.
Compatibility is not completion
A match compares listing fields. It does not show that enough time, people, tools, or skill are available, and it does not mean the need has been met.
The current prototype stops before introductions
It does not reveal contact details, arrange meetings, or certify safety. The safety design and real-world operating gates remain proposals that must be resolved before a pilot.
People are not the score
No story here represents an actual person, volunteer signup, request, or address. An empty place in a plan describes a need, not someone’s failure or an obligation to help.

SOURCE NOTES
foundation: CivilGood product foundation [Project specification]
Defines the prototype purpose, request-and-offer loop, free-help principles, and the boundary that matching only shows possible fits.
safety-proposal: Safety and privacy system design [Project specification]
A proposal for the decisions, consent, privacy, human review, and operating controls required before real-world activity.
listing-model: CivilGood listing model [Source code]
The current listing fields include request or offer, category, tags, broad area, availability, and status, with checks against contact details and precise locations.
matcher: CivilGood candidate matcher [Source code]
The deterministic matcher requires opposite listing kinds, matching category and broad area, and positive time overlap; tags and overlap contribute to an explained score.
assessment: Pass 3: a feature worth testing [Enhancement assessment]
Recommends exploring bounded contributions and hosted sessions as product hypotheses, while distinguishing compatibility from task feasibility and leaving adoption and safety decisions open.

Help can begin small
The prototype can show where a request and an offer might fit. A future CivilGood could help a community make a small, bounded contribution useful, while staying free and voluntary and showing clearly whenever a need is still open.