Section 432 of 440
Complete canonical tutorial. This reader section contains the same teaching body as PWR-250 · Community sensing. Open the Power dossier.
PWR-250 · SUPERVISED full tutorial
Design a community-sensing chain from legitimate purpose to verified data, response and deletion
This lesson teaches the full provider-led community-sensing method: establish an accountable sponsor and decision purpose, involve affected communities before collection, set a protocol and metadata, and protect sensitive places and people. You will also train observation and quality checks, measure participation and coverage bias, verify signals, connect findings to an accountable response, return results to contributors, and govern access, secondary use and deletion. Practice uses fictional records only.
1 · Permission and limits
Know exactly what you may do
2 · Get ready
Gather what you need and check the starting conditions
What you need
- Authorised facilitator and a fictional flood-puddle observation project in the imaginary town of Merehaven.
- Fictional sponsor/decision card, protocol, metadata form, consent/privacy and sensitive-location screen.
- Twenty supplied observations. O1-O10 are unique, timed North Path reports at hourly times 08:00-17:00 with standing-water depths 2, 3, 2, 4, 3, 4, 5, 3, 2 and 4 cm. O11-O14 are unique timed reports from West Lane, South Gate, East Path and Market Square at 09:15, 10:30, 11:45 and 13:00 with depths 1, 2, 1 and 3 cm. O15 exactly duplicates O2; O16 duplicates O5; O17-O19 lack observation time; O20 includes an exact-home image and is restricted from open use. The verification sample is O1, O3, O6, O10, O12 and O14; references verify O1, O3, O12 and O14 but not O6 or O10. Supply a coverage map and response log.
Before you start
- Confirm the project, contributors, coordinates, species and institutions are entirely fictional.
- Write the decision purpose and accountable sponsor before opening the packet.
- Set collection limits, verification, deletion and stop rules, including no real field visit or sensing.
3 · The method
Follow these steps in order
- Define sponsor and decision
Name the accountable body, exact question, intended decision, jurisdiction, duration and non-uses.
Why: Data without a decision owner can extract effort without response.
Check: The purpose is narrow and the sponsor can act or explain why not.
- Involve affected interests
Identify residents, land/rightsholders, workers, accessibility groups, privacy interests and absent people before protocol design.
Why: Community sensing is not legitimate because volunteers are available.
Check: The design records influence and unresolved representation.
- Specify observation protocol
Define what counts as an observation, units/categories, time window, location precision, equipment, repeats and invalid cases.
Why: Comparable records require a shared method.
Check: Two fictional contributors would record the same event similarly.
- Set consent and data lifecycle
Separate participation, location, image, contact, publication and secondary-use choices; define access, correction, retention and deletion.
Why: Open collection is not blanket permission.
Check: Every field and use has authority and an expiry.
- Protect people and sensitive places
Remove exact homes, protected sites, vulnerable populations and ecological locations unless specifically authorised; provide a no-collection rule.
Why: Precision can create privacy, safety or ecological harm.
Check: Sensitive records are coarsened, restricted or excluded.
- Run quality checks
Validate time, location class, protocol fit, duplicates, equipment/observer notes and plausibility; keep rejected records and reasons visible.
Why: Cleaning can hide inconvenient or biased data.
Check: Each record is valid, uncertain or excluded with a reason.
- Measure participation and coverage
Map who reported, where and when, concentration, gaps and access barriers; do not treat empty space as absence.
Why: Volunteer data often cluster by access and motivation.
Check: The coverage table names North Path concentration and every unobserved area or time.
- Verify before response
Compare a sample with authorised reference or trained review, record false positives/negatives and uncertainty.
Why: Raw reports are signals, not facts.
Check: Only verified evidence reaches the fictional decision route.
- Close response and feedback
Record what the sponsor did, why, how contributors were informed and how corrections or complaints are handled.
Why: Participation should have an accountable consequence.
Check: Contributors can trace data to response or explained non-action.
- Review reuse and retire
At the endpoint, review value, harm, bias and unresolved need; delete, restrict or renew under fresh authority.
Why: Projects should not collect forever by inertia.
Check: No data remains active beyond purpose without a governed decision.
4 · Worked example
See the whole method used once
Scenario
Merehaven’s fictional public-works sponsor asks whether repeated standing-water reports justify inspecting one drainage zone; twenty invented observations are supplied.
Walkthrough
- The facilitator locks the purpose to selecting an inspection priority, not proving flood cause, and records affected residents and privacy limits.
- The learner applies the protocol and excludes two duplicates, three missing-time records and one exact-home image from open use.
- Fourteen records remain; the coverage map shows 10 of 14, or 71%, came from one easy-access path, and the reference review verifies four of six sampled reports.
- The sponsor chooses a limited inspection, reports uncertainty and coverage bias to contributors, deletes contact fields and rejects secondary marketing use.
Result
The exercise demonstrates a governed signal-to-response chain with visible bias and deletion. It does not validate a real project, location or environmental cause.
5 · Right and wrong
Compare correct or safer execution with the common wrong version
| Moment | Right / safer | Wrong / riskier | Why it matters |
|---|---|---|---|
| Starting collection | Name sponsor, decision and affected interests first. | Launch a form because the sensor is available. | Availability does not create purpose or authority. |
| Reading density | Analyse who could report, where observations cluster and which areas remain unseen. | Treat map clusters as the real distribution. | Reports cluster where people can and choose to observe. |
| Using reports | Verify sampled reports and record mismatches, missingness and measurement uncertainty. | Send every raw report directly to action. | Unverified signals can misdirect resources or expose people. |
| Reusing data | Seek renewed authority and consent before reusing contributor data for another purpose. | Reuse because data is already open. | Technical access does not erase purpose and community rights. |
6 · Common mistakes
Spot the error and apply the correction
| Mistake | Fix |
|---|---|
| The sensing purpose stops at vague awareness raising. | Name the exact accountable decision and response owner. |
| The observation protocol allows ambiguous free-text categories. | Define observable categories, time and invalid cases. |
| The form collects exact homes without decision need. | Use the coarsest location needed and protect sensitive records. |
| Easy-path clustering is omitted from the finding. | Report concentration, gaps and access barriers beside findings. |
| Cleaning deletes rejected records and their exclusion reasons. | Keep rejected-record reasons and quality counts. |
| Contributors receive neither findings nor an explained response. | Add feedback, correction and explained non-action routes. |
7 · Practice
Turn the steps into a usable skill
First session
- Define fictional sponsor, purpose, affected interests and non-uses.
- Build protocol, metadata and consent/lifecycle rules.
- Classify all 20 fictional observations for quality and privacy.
- Map participation/coverage and verify the supplied sample.
- Write response, feedback, deletion and stop decisions with the facilitator.
Repeat plan
The authorised sponsor sets any real programme cadence. Repeat the fictional audit with a new packet that changes season or reporting channel, keeping the same decision and quality rule.
Progress when
- Protocol, consent and sensitive-location rules are applied consistently.
- Coverage bias and verification error remain visible in the conclusion.
- The sponsor’s response, contributor feedback and deletion route close the lifecycle.
Do not progress when
- Any real person, location, image, ecological site or public-subject data appears.
- Sponsor, decision authority, community involvement, verification or response route is missing.
- Collection risks privacy, surveillance, ecological harm, trespass or retaliation.
8 · Check the result
Measure what changed
Integrity of one fictional sensing chain from protocol to response
How: Score sponsor/purpose, community input, protocol, metadata, consent, sensitivity, quality, coverage, verification, response, feedback and retirement; calculate valid/excluded counts and sample error.
Good result: A good result completes all 12 stages, reports bias and error, and links only verified data to the declared fictional response.
This does not prove: It does not prove truth, representation, causal impact, ecological validity or authority to collect/publicise real data.
Self-check
- Which decision can the sponsor actually make with these data?
- What makes one observation valid, uncertain or excluded?
- Who or where is under-represented in the coverage map?
- What happens to contact, location and secondary-use rights at project end?
9 · Stop, adapt or get help
Keep the safety boundary practical
Stop and get help
- Stop if real precise locations, protected sites, identifiable people or sensitive community knowledge enters the exercise.
- Stop when there is no accountable sponsor, decision, verification or harm-response route.
- Route real environmental, public-health, privacy, research and community data work to authorised specialists and rightsholders.
Accessibility and adaptations
- Provide participation, consent, protocol, correction and feedback in accessible formats and needed languages.
- Offer offline, assisted and non-smartphone contribution routes in any legitimate project and measure who remains excluded.
- Avoid requiring images, exact coordinates or public identity when the decision does not need them.
10 · Evidence and limits
Why these instructions are here
- primary research
A citizen-science flood-data case study documents engagement and local collection while showing that participation and data quality depend on the configured project.
Citizen scientists' engagement in flood risk-related data collection: a case study in Bui River Basin, Vietnam - primary research
A community-monitoring study found displacement rather than a simple overall reduction in forest use, illustrating why response and spillover matter beyond reports.
Can community monitoring save the commons? Evidence on forest use and displacement
Limits
- All observations, places and people are fictional.
- Community participation does not guarantee data quality or legitimacy.
- Verified data still does not erase rights, distribution, response or secondary-use limits.
- Raw reports or map density cannot establish truth, representation or benefit.
- Participation was highly concentrated in one study; community monitoring did not reduce overall forest use in another and displaced loss outside monitored areas.
Open the complete canonical research register
- Primary empirical supportLimiting / contraryCitizen scientists' engagement in flood risk-related data collection: a case study in Bui River Basin, Vietnam
Huan N. Tran; Martine Rutten; Rajaram Prajapati; Ha T. Tran; Sudeep Duwal; Dung T. Nguyen; Jeffrey C. Davids; Konrad Miegel · 2024 · Primary research
- Primary empirical supportLimiting / contraryCan community monitoring save the commons? Evidence on forest use and displacement
Sabrina Eisenbarth; Louis Graham; Anouk S. Rigterink · 2021 · Primary research
- Primary empirical supportLimiting / contraryAdoption of community monitoring improves common pool resource management across contexts
Tara Slough; Daniel Rubenson; Ro’ee Levy; Francisco Alpizar Rodriguez; María Bernedo del Carpio; Mark T. Buntaine; Darin Christensen; Alicia Cooperman; Sabrina Eisenbarth; Paul J. Ferraro; Louis Graham; Alexandra C. Hartman; Jacob Kopas; Sasha McLarty; Anouk S. Rigterink; Cyrus Samii; Brigitte Seim; Johannes Urpelainen; Bing Zhang · 2021 · Primary research
Read the complete evidence interpretation on the Power dossier.
Tutorial delivery controls
Learn, adapt, troubleshoot and resume
Progress is saved only in this browser on this device.
Step-by-step learner mode
Each activity includes its success check, a nearby accessible alternative and an “I’m stuck” correction path. Alternatives preserve the target where possible; when they change the task, Titan labels them as related rather than equivalent.
Define sponsor and decision
Name the accountable body, exact question, intended decision, jurisdiction, duration and non-uses.
Data without a decision owner can extract effort without response.
The purpose is narrow and the sponsor can act or explain why not.
I’m stuck on this step
Reset: Re-read this authored instruction — “Name the accountable body, exact question, intended decision, jurisdiction, duration and non-uses.” — and its success check, then attempt only this step.
Possible snag: The sensing purpose stops at vague awareness raising.
Correction: Name the exact accountable decision and response owner.
Stop / get help: Stop if real precise locations, protected sites, identifiable people or sensitive community knowledge enters the exercise.
Involve affected interests
Identify residents, land/rightsholders, workers, accessibility groups, privacy interests and absent people before protocol design.
Community sensing is not legitimate because volunteers are available.
The design records influence and unresolved representation.
I’m stuck on this step
Reset: Re-read this authored instruction — “Identify residents, land/rightsholders, workers, accessibility groups, privacy interests and absent people before protocol design.” — and its success check, then attempt only this step.
Possible snag: The result from “Identify residents, land/rightsholders, workers, accessibility groups, privacy interests and absent people before protocol design.” does not yet meet this declared check: The design records influence and unresolved representation.
Correction: Return to the start of “Involve affected interests”, reduce complexity or pace, and repeat only the part needed to satisfy: “The design records influence and unresolved representation.”
Stop / get help: Stop if real precise locations, protected sites, identifiable people or sensitive community knowledge enters the exercise.
Specify observation protocol
Define what counts as an observation, units/categories, time window, location precision, equipment, repeats and invalid cases.
Comparable records require a shared method.
Two fictional contributors would record the same event similarly.
I’m stuck on this step
Reset: Re-read this authored instruction — “Define what counts as an observation, units/categories, time window, location precision, equipment, repeats and invalid cases.” — and its success check, then attempt only this step.
Possible snag: The observation protocol allows ambiguous free-text categories.
Correction: Define observable categories, time and invalid cases.
Stop / get help: Stop if real precise locations, protected sites, identifiable people or sensitive community knowledge enters the exercise.
Set consent and data lifecycle
Separate participation, location, image, contact, publication and secondary-use choices; define access, correction, retention and deletion.
Open collection is not blanket permission.
Every field and use has authority and an expiry.
I’m stuck on this step
Reset: Re-read this authored instruction — “Separate participation, location, image, contact, publication and secondary-use choices; define access, correction, retention and deletion.” — and its success check, then attempt only this step.
Possible snag: The result from “Separate participation, location, image, contact, publication and secondary-use choices; define access, correction, retention and deletion.” does not yet meet this declared check: Every field and use has authority and an expiry.
Correction: Return to the start of “Set consent and data lifecycle”, reduce complexity or pace, and repeat only the part needed to satisfy: “Every field and use has authority and an expiry.”
Stop / get help: Stop if real precise locations, protected sites, identifiable people or sensitive community knowledge enters the exercise.
Protect people and sensitive places
Remove exact homes, protected sites, vulnerable populations and ecological locations unless specifically authorised; provide a no-collection rule.
Precision can create privacy, safety or ecological harm.
Sensitive records are coarsened, restricted or excluded.
I’m stuck on this step
Reset: Re-read this authored instruction — “Remove exact homes, protected sites, vulnerable populations and ecological locations unless specifically authorised; provide a no-collection rule.” — and its success check, then attempt only this step.
Possible snag: The form collects exact homes without decision need.
Correction: Use the coarsest location needed and protect sensitive records.
Stop / get help: Stop if real precise locations, protected sites, identifiable people or sensitive community knowledge enters the exercise.
Run quality checks
Validate time, location class, protocol fit, duplicates, equipment/observer notes and plausibility; keep rejected records and reasons visible.
Cleaning can hide inconvenient or biased data.
Each record is valid, uncertain or excluded with a reason.
I’m stuck on this step
Reset: Re-read this authored instruction — “Validate time, location class, protocol fit, duplicates, equipment/observer notes and plausibility; keep rejected records and reasons visible.” — and its success check, then attempt only this step.
Possible snag: Cleaning deletes rejected records and their exclusion reasons.
Correction: Keep rejected-record reasons and quality counts.
Stop / get help: Stop if real precise locations, protected sites, identifiable people or sensitive community knowledge enters the exercise.
Measure participation and coverage
Map who reported, where and when, concentration, gaps and access barriers; do not treat empty space as absence.
Volunteer data often cluster by access and motivation.
The coverage table names North Path concentration and every unobserved area or time.
I’m stuck on this step
Reset: Re-read this authored instruction — “Map who reported, where and when, concentration, gaps and access barriers; do not treat empty space as absence.” — and its success check, then attempt only this step.
Possible snag: Easy-path clustering is omitted from the finding.
Correction: Report concentration, gaps and access barriers beside findings.
Stop / get help: Stop if real precise locations, protected sites, identifiable people or sensitive community knowledge enters the exercise.
Verify before response
Compare a sample with authorised reference or trained review, record false positives/negatives and uncertainty.
Raw reports are signals, not facts.
Only verified evidence reaches the fictional decision route.
I’m stuck on this step
Reset: Re-read this authored instruction — “Compare a sample with authorised reference or trained review, record false positives/negatives and uncertainty.” — and its success check, then attempt only this step.
Possible snag: The result from “Compare a sample with authorised reference or trained review, record false positives/negatives and uncertainty.” does not yet meet this declared check: Only verified evidence reaches the fictional decision route.
Correction: Return to the start of “Verify before response”, reduce complexity or pace, and repeat only the part needed to satisfy: “Only verified evidence reaches the fictional decision route.”
Stop / get help: Stop if real precise locations, protected sites, identifiable people or sensitive community knowledge enters the exercise.
Close response and feedback
Record what the sponsor did, why, how contributors were informed and how corrections or complaints are handled.
Participation should have an accountable consequence.
Contributors can trace data to response or explained non-action.
I’m stuck on this step
Reset: Re-read this authored instruction — “Record what the sponsor did, why, how contributors were informed and how corrections or complaints are handled.” — and its success check, then attempt only this step.
Possible snag: Contributors receive neither findings nor an explained response.
Correction: Add feedback, correction and explained non-action routes.
Stop / get help: Stop if real precise locations, protected sites, identifiable people or sensitive community knowledge enters the exercise.
Review reuse and retire
At the endpoint, review value, harm, bias and unresolved need; delete, restrict or renew under fresh authority.
Projects should not collect forever by inertia.
No data remains active beyond purpose without a governed decision.
I’m stuck on this step
Reset: Re-read this authored instruction — “At the endpoint, review value, harm, bias and unresolved need; delete, restrict or renew under fresh authority.” — and its success check, then attempt only this step.
Possible snag: The result from “At the endpoint, review value, harm, bias and unresolved need; delete, restrict or renew under fresh authority.” does not yet meet this declared check: No data remains active beyond purpose without a governed decision.
Correction: Return to the start of “Review reuse and retire”, reduce complexity or pace, and repeat only the part needed to satisfy: “No data remains active beyond purpose without a governed decision.”
Stop / get help: Stop if real precise locations, protected sites, identifiable people or sensitive community knowledge enters the exercise.
Correct versus incorrect execution
These accessible process diagrams are built from the tutorial’s own right/wrong teaching. They are not anatomical illustrations and do not add technique beyond the canonical tutorial.
Name sponsor, decision and affected interests first.
Launch a form because the sensor is available.
Analyse who could report, where observations cluster and which areas remain unseen.
Treat map clusters as the real distribution.
Verify sampled reports and record mismatches, missingness and measurement uncertainty.
Send every raw report directly to action.
Seek renewed authority and consent before reusing contributor data for another purpose.
Reuse because data is already open.
Method-structure checklist
10 of 10 structural checks present
- Ordered, Power-specific instructions — present
- Every activity has a success check — present
- Materials or supplied records are declared — present
- Measurement or assessment rule is present — present
- Tutorial-specific troubleshooting is present — present
- Stopping or escalation boundary is present — present
- Every activity has an adjacent alternative — present
- Correct-versus-incorrect comparison is present — present
- Evidence context is bound to the Power record — present
- Planning metadata is present — present
The method-readiness band and presence checklist assess tutorial presentation and are separate from evidence quality for the underlying Power. They are automated editorial aids, not human approval.
Manual editorial sign-off: Pending. This tutorial must not display a human-approved state until an identified editor signs the exact content hash.