Captured retroactively. This was a discrete decision-capture session, not a feature ship — it produced four governance entries at once that opened the design space for everything reaction-, comment-, and credit-related. The credit value is intentionally small per the Entry 017 methodology (decision-capture sessions in the 4–8 range) and is subject to revision under G-038's calibration mechanism.
What shipped (governance entries, not code)
- Entry 015 — Pre-launch engagement. The principle decision: open Support / Concern reactions to anonymous viewers and let registered users earn credits during the founding phase, with rate intentionally unspecified.
- G-035 — Mutual-consent comment model. Tier 2 open question defining the three-state visibility shape (private / author-public / mutual) for comments, even though no code shipped yet.
- G-036 — Reaction system parameters. Tier 2 open question naming the operational parameters that the thin-slice reactions implementation deliberately deferred (anonymous-vs-registered weighting, cooldowns, abuse heuristics).
- G-037 — Pre-launch credit accrual mechanics. Tier 2 open question naming the rate, qualifying actions, cap, time-decay, conversion-at-launch, disclosure-timing, and refusal-path sub-questions.
Why this is on the roadmap
Decision-capture work is governance, not infrastructure. Per the Entry 017 boundary, it would normally not earn its own credit. This session is the exception because it shipped four entries at once that the next two infrastructure projects (P-001 roadmap surface and P-002 reactions) directly built on. Without this session, those ships would have happened without governance ground under them.
This one entry on the roadmap is the boundary: ongoing governance writing isn't a project, but a session that opens the design space for multiple infrastructure ships gets named.