How readers respond to Journal and Register entries — what the default visibility is, who sees what when, and how exchanges become public.
Why this matters
The point of publishing the Journal openly is to invite scrutiny. Without a feedback channel, the open publication is performative — readers can see decisions but cannot push back. The Register is an even more direct invitation: a register of open questions implies a way to respond.
But default-public comment threads on every entry would import the failure modes the project is structurally designed against — Fandom-style noise, performative pushback, drive-by ideological fights, a moderation burden the project does not yet have staffing for, and a public record of ill-considered hot takes that ages badly for both commenter and project.
The design question is how to enable real engagement without those failure modes.
Sub-questions
- Default visibility. Are comments public by default, private by default, or something else?
- Publication mechanic. If not default-public, what flips a comment to public — entry-owner consent, commenter consent, both, neither (time delay), some combination?
- Counts vs content. Should the public see that private dialogue exists on an entry even when it cannot see the content?
- Retraction. What happens to consented-public comments when one party later retracts consent? "You cannot unring a bell" vs "privacy was a promise."
- Phased entries. Comments on phased entries — are they limited to the public framing, or can admins discuss the internal section in shared private threads?
- Internal entries. Comments on internal-only entries — admin-only presumably, but worth confirming.
- Identity floor. Anonymous? Authenticated? Verified-identity? Different rules for different entry tiers?
Proposed direction
Mutual-consent default, drawing the line so commenters and the entry owner each have unilateral veto over publication but neither can compel silence:
- Comments default to private between commenter and entry owner.
- Either party can mark a comment "ready to publish." Publication requires both marks. Either party can withdraw their mark, which un-publishes the comment going forward (existing rendered copies stay, but the comment no longer appears as public).
- A public counter on each entry surfaces that dialogue exists: "8 private exchanges, 1 published" — accountability without content disclosure.
- Linear threads (no nested replies) to keep the moderation surface small.
- Phased entries: comments scoped to the public body. Admin-only side threads available for the internal half.
- Internal-only entries: admin-only comments.
Identity floor and the relationship to anonymous reactions (Entry 015 + G-036) — not yet settled.
Related
- Entry 005 — Contributor sovereignty (the value frame for treating commenter identity carefully)
- Entry 010 — Mission Stewardship (the body that could resolve "is this comment about the mission?" disputes)
- Entry 014 — Constitutional Amendment Process (the formal pipeline a qualifying comment could feed)
- Entry 015 — Pre-Launch Engagement (reactions and credits, the parallel engagement layer)
- G-008 — Constitutional amendment process specifics
- G-036 — Reaction system parameters