Design the notification and activity layer — the delivery substrate for annotation/LoreLine replies, Fact review outcomes, grace-period expiry, and the impact-echo ("your Fact now powers N pages") that the gamification model depends on.
Why this matters
The build already has un-notified events (threaded annotation replies), and the product roadmap adds many more. The impact-echo — the primary intrinsic gamification mechanic (Entry 031) — cannot exist without a delivery channel. Open decisions:
- Event taxonomy — what generates a notification: replies to your annotation/LoreLine (Entry 010), your Fact confirmed/contested in the review queue (G-060), grace-period expiry on a Fact you own (Layer 10), governance events you're eligible to vote on, and the impact-echo (your contribution cascaded / got cited).
- Channels & cadence — in-app activity feed vs. email vs. digest; per-type user controls; how it avoids the engagement-maximizing dark patterns OLN exists to reject.
- Activity feed as recognition — how the feed doubles as the surface for recognition (G-051) without becoming a volume leaderboard.
- Privacy — interaction with consumption-edge visibility (G-049): which activity is private, which is publicly attributable.
Related
- Entry 032 — the bridge strategy that surfaces this gap
- Entry 031 — the impact-echo mechanic that depends on delivery
- Entry 010 — LoreLines (the interpretive replies that need notifying)
- G-059 — gamified contribution (impact-echo source)
- G-060 — Fact review queue (outcomes that notify)
- G-051 — profile recognition & badge model
- G-049 — consumption-edge privacy & visibility