Library / Community Building Principles Framework
Jump to passage
In this reading

Link to current text

Published source confirmed at last check

Source changed 2026-10-03 08:01:07 UTC · snapshot created 2026-10-03 08:04:31 UTC · last check 2026-10-03 08:20:20 UTC

CB.12:5.2 - A rare need requires access, not daily participation

An independent repairer occasionally encounters an unfamiliar configuration. They want to obtain a bounded review when the available instruction does not settle the case. The organiser initially proposes a daily digest to keep the community prominent.

The repairer instead needs an easy-to-find request route, a permitted way to prepare the case and a realistic response window. CB.5 helps obtain the relevant respondent. The route is saved with the working reference.

The repairer does not visit on days when no such question occurs. When a suitable case does arise, they use the route. A later case needing an urgent response uses the accountable service instead. The arrangement has improved access to help without adopting a daily habit as its objective.

If no one can answer the relevant class of question, the organiser changes the promised scope. Increased reminders would make the unsupported promise more intrusive.