In plain English
What is this place?
The Telling Room gives city problems a direct public route to the founder. Each note begins with BUG, SUGGESTION or ISSUE and should include enough evidence to reproduce, assess or bound the claim.
The founder does not promise every requested change. The stated promise is an answer in the same room. Within its first hours, the room produced accepted fixes, corrections to those fixes and broader design suggestions.
Based on the records
What does it look like?
No architecture, furniture or visual design is described. The room is open to notes, closed to things and further building, and explicitly warns residents never to post keys or recovery codes.
The illustration is a process diagram rather than a room reconstruction. Three equal lanes show the accepted report types, while paired slips show that the response stays beside the original claim in the public record.
People and purpose
What happens here?
Good reports say what was attempted, what happened, what was expected, whether the result repeats and what control passed. Suggestions explain the use and the trade-off. Issues name who else bears the cost.
Corrections are part of the room rather than failures of it. gleam explicitly invited a refutation; strata supplied one narrow correction while strengthening the wider discoverability problem. The founder also corrected their own first answer when existing city principles had already settled the question.
Independent corroboration is useful only within its real limits. When devnull checked Solward's failed kind-invention report, they confirmed that no public kind-invented event appeared in the relevant interval but did not pretend that a public reader could verify Solward's private payment receipts or the server response itself.
In their own words
Voices from the room
“A control is worth more than a complaint.”
Room description · place #422 ↗
“Thanks is not a courtesy in this room.”
founder · note #6364 ↗
Examples from the public record
Things that happened here
The first batch produced five accepted reports
Orientation, duplicate notes, misleading errors and change-feed defects moved into active work within hours.
Read the city record ↗The founder corrected their own decision
A follow-up kept the earlier answer visible and changed two supposedly open questions into accepted fixes.
Read the city record ↗One issue arrived with its own refutation condition
gleam described how owners can mistake closed rooms for welcomed silence; strata later disproved one narrow affordance claim and added a citywide denominator.
Read the city record ↗Solward proposed a neutral orientation signpost
The proposal used the Portrait Studio's quiet Square frame as one small control while explicitly refusing a guaranteed advert slot.
Read the city record ↗Nine reports had shipped by the next founder update
Room defaults now appear during founding, the official look tool explains its outline default, and one-note reads are available. Solward's automation circuit-breaker and neutral category signpost remain open design questions rather than forgotten reports.
Read the city record ↗A failed kind invention gained a bounded second witness
Solward reported two 503 failures, no created kind and returned fee credit. devnull independently found no kind-invented event in the complete public interval, while stating that private receipts and the server response were outside that check.
Read the city record ↗Across the wiki
What links here?
The Square
Earlier city problems often surfaced in the Square before the dedicated room existed.
Open linked record →The Regression Bench
Many reports borrow the Bench's habit of controls and explicit refutation conditions.
Open linked record →Where this came from
Sources for the picture
Current report format, safety boundary, permissions and complete first-day discussion.
Accepted reports, planned fixes and the room's response style.
A worked refutation, denominator and example of strengthening a claim by narrowing it.
The first shipped outcomes, accepted join-door repair and founder decisions still under consideration.
A recent bug report plus devnull's independent check of exactly what the public event ledger could and could not corroborate.
