Ullrich Schäfer 96de8831cf

poi-index: Grafana dashboard/alert, docs, privacy manifest

- planner dashboard: replace Overpass panels with POI index freshness +
  serving panels (age, rows/category, import status, API request rate/errors)
- alerts: replace overpass-upstream-unhealthy with poi-index-stale (>6 weeks)
- architecture.md: POI data flow now the self-hosted index
- privacy manifest (DE+EN): Overpass is Journal-surface-backfill-only;
  Planner POIs served same-origin from /api/pois
- self-host-overpass README + roadmap: superseded for POIs by poi-index
- poi-extract README: self-hoster story (optional pipeline, regional extract,
  graceful empty index)
- map-core tsconfig: exclude *.sync.test.ts from tsc to keep it zero-dep

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

2026-07-12 22:54:51 +02:00

4.7 KiB

Raw Blame History

Roadmap

Strategic view of what ships when and why. For implementation detail, see the linked OpenSpec changes in openspec/changes/. For exploratory ideas not yet in a change, see docs/ideas/.

Launch readiness

Five changes must ship before public announcement:

Change	Why it blocks launch
`route-sharing`	Per-user sharing (view/edit), forking, contributor tracking. (Visibility levels already shipped via `public-content-visibility`.)
`social-federation`	The platform is described as federated — launching without it would be misleading. ActivityPub, WebFinger, inbound Mastodon follows.
`visual-redesign`	Design system not yet implemented. Current UI is unstyled Tailwind. Must land before any public-facing announcement.
`wahoo-production-cutover`	Wahoo sandbox rate limits make the integration unusable at scale. Ops task, not a feature, but launch-blocking.
`changelog`	Public `/changelog` is part of the launch narrative — how we communicate "here's what just shipped" to early users on day one.

Phases

Phase 1 — Feature complete

Implement all launch-blocking changes above. There are no dependencies between them — social-federation's former dependency on route-sharing was satisfied when public-content-visibility and social-feed shipped (public routes/activities, public profiles, IRI-keyed follows). All four can proceed independently:

social-federation (prerequisites already shipped)
route-sharing
wahoo-production-cutover (ops, can run in parallel)
changelog

Phase 2 — Polish sprint

After features are stable, run a dedicated UI/UX review pass:

Walk every user-facing flow end-to-end in a real browser
Implement visual-redesign if not already complete (this change may span phases 1–2)
Fix rough edges: empty states, loading states, error messages, mobile layout
Review copy and i18n strings for consistency
No new features during this phase — polish only

The polish sprint is its own phase because it requires a stable feature set. Polishing during active feature development is expensive churn.

Phase 3 — Soft launch / beta

Invite 10–20 real users before public announcement:

Watch Sentry for crashes and unhandled errors
Watch Grafana for performance regressions
Watch for federation interop issues (Mastodon follow/unfollow, object delivery)
Collect structured feedback on onboarding and core flows
Fix anything critical; defer cosmetic issues to post-launch

Phase 4 — Public announcement

Announce once beta feedback is resolved:

Changelog entry for launch
Social post / blog post

Post-launch

These changes are scoped and designed but not blocking launch:

Change	Notes
`route-discovery`	Spatial map-based route exploration. The text `/explore` page covers the gap at launch.
`activity-photos`	Photo uploads for activities. Enriches content but not a day-one requirement.
`mobile-app`	React Native unified app. Substantial scope; explicitly post-launch.
`route-federation`	Routes as federated objects: Invite/Accept mirroring, cross-instance Planner edits. The collaboration half of the federation vision; depends on `social-federation` §6 + `route-sharing`.

Ideas (exploratory, not yet in a change)

See docs/ideas/ for pre-spec explorations:

mobile-activity-recording/ — GPS tracking and activity logging from a native app
mobile-nearby-sync/ — BLE-based proximity discovery
self-host-overpass/ — Self-hosted Overpass API (superseded for POI overlays by the shipped poi-index; revive only if we need Overpass QL or to own the surface-backfill upstream)
instance-administration.md — admin role, registration toggle, suspend/ban, federation blocklists, reports
social-interactions.md — local likes + comments (the foundation the federated kudos/comments attach to)
activity-participants.md — tag co-riders on shared activities, confirm/decline, federated mentions
multi-day-collections.md — activity collections for multi-day trips (architecture open question #1)
fediverse-enhancements.md — post-v1 federation: map images in Notes, fediverse kudos, comments, Events/Mobilizon, Wanderer interop, federated explore
split-domain-handles.md — @bob@example.com handles while the journal runs on a subdomain (Hollo/Mastodon-style; Fedify supports it natively)

4.7 KiB Raw Blame History Unescape Escape