Compleet
33 lines
1.3 KiB
Markdown
33 lines
1.3 KiB
Markdown
# Roadmap
|
|
|
|
The roadmap protects the editorial heartbeat from product sprawl.
|
|
|
|
## Now: authored foundation
|
|
|
|
- Establish the masthead, author identity, domain, and book details.
|
|
- Publish the weekly briefing and a sustainable original-story cadence.
|
|
- Bring the existing podcast archive and transcripts home.
|
|
- Launch three genuinely useful field guides.
|
|
- Publish a clear correction log and recent-maintenance ledger.
|
|
- Build an editorial buffer before promising a public weekly rhythm.
|
|
|
|
## Next: useful archive
|
|
|
|
- Add annotated links only when the weekly workflow can sustain them.
|
|
- Render passage-level Git history without turning articles into issue trackers.
|
|
- Introduce confidential correction intake and measured public challenge handling.
|
|
- Add durable topic and relationship navigation after real reporting reveals the useful shapes.
|
|
|
|
## Later: participation
|
|
|
|
- Contextual contributor signals, never global scores.
|
|
- Small events or correspondence formats before a community platform.
|
|
- Professional briefing only after the free editorial rhythm is demonstrably sustainable.
|
|
|
|
## Explicit non-goals
|
|
|
|
- No accounts, comments, likes, follower counts, global karma, or vendor marketplace.
|
|
- No database until a proven reader need requires one.
|
|
- No public reporting notebook or confidential-source material.
|
|
- No claim that Git history makes reporting true.
|