Community story
booth.
Collect and return local stories through a visible, trusted community presence.
The opportunity
Design for the moment that matters.
What breaks today
Oral histories are difficult to gather consistently, and recording booths can feel extractive when people do not know who will use their story or how.
The presence pattern
A local facilitator or remote interviewer appears in a dedicated booth, explains consent and use, records the story and shows how participants can review or withdraw it.
Design requirements
Make it useful before making it magical.
- 01
Obtain real consent
Make capture, participation, recording and synthetic transformation choices understandable and reversible.
- 02
Protect emotional context
Do not use surprise, false liveness or manipulative simulation in intimate or vulnerable moments.
- 03
Keep people in control
Use simple entry, exit, mute, delete and human-support paths appropriate to the audience.
Operator runbook
Design the complete service—not only the scene.
- 01
Frame the service
Libraries, cities and cultural organizations should document the intended audience, room, session length, approved content or knowledge, human escalation path and the current baseline for consented stories.
- 02
Invite with clarity
Before the community story booth experience begins, explain why the presence is there, whether it is live, recorded or AI-assisted, what it can do and how a participant can leave or reach a person.
- 03
Operate the moment
A local facilitator or remote interviewer appears in a dedicated booth, explains consent and use, records the story and shows how participants can review or withdraw it. The operator should be able to observe state, recover the session and protect the physical activity already happening in the room.
- 04
Close the loop
End with a visible next step, capture only consented information and record consented stories, participant diversity, review completion. Review failures and handoffs before repeating or expanding the experience.
Pilot scorecard
Prove a real outcome in the room.
Consented stories
Define the starting event, completion event and current-workflow baseline for consented stories. Count only observable outcomes.
Participant diversity
Review participant diversity by audience, session stage and operator. Use the pattern to find where confidence is gained or lost.
Review completion
Set a minimum threshold for review completion before launch. Name the owner and recovery action when a session misses it.
Decision gates
Know when presence is—and is not—the answer.
Presence must earn the room
If the same community story booth outcome can be achieved by a well-designed phone, kiosk or conventional video call with equal trust and clarity, use the simpler tool.
The boundary must stay visible
Do not launch community story booth until participants can identify the role, source, live or synthetic state, information boundary and human fallback without guessing.
The operation must survive novelty
Libraries, cities and cultural organizations should be able to run, pause, recover and measure the experience repeatedly. Do not scale while success depends on a founder or engineer standing beside it.
Evidence status. This page is a product-design field brief, not a claim that Reality Relay has already produced the stated customer outcome. Replace the hypothesis with measured pilot evidence before presenting it as proof.
Build the first pilot
Start narrow enough to learn.
For Community story booth, begin with one real environment, one defined audience and one repeatable interaction. Establish who operates the experience, what information or tools it can access and exactly when a person must take control.
Reality Relay Platform coordinates content, session state, approved intelligence and operations. Reality Relay Spaces give the experience a calibrated physical endpoint with intentional scale, eye line, sound and grounding. The pilot should earn expansion by improving the scorecard above—not by novelty alone.
- Primary audience
- Libraries, cities and cultural organizations
- Experience family
- Personal presence & community
- First decision
- Choose the room, baseline and accountable operator
- Expansion rule
- Scale only after the scorecard beats the current workflow