From 81ba2d5de3507a418e8bcadbc13726a9307b2b9f Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Ullrich=20Sch=C3=A4fer?= Date: Sat, 6 Jun 2026 13:16:06 +0200 Subject: [PATCH] =?UTF-8?q?docs:=20fix=20stale=20route-sharing=20=E2=86=92?= =?UTF-8?q?=20social-federation=20dependency?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit The roadmap claimed social-federation depends on route-sharing for public routes, but that prerequisite shipped independently via public-content-visibility (2026-04-24) and social-feed (2026-04-25): visibility columns, public profiles, and IRI-keyed follows are all in place. Reorder Phase 1 to reflect that federation can start now. Also flag route-sharing's proposal as needing re-scoping: tasks 1.1-1.3 and 3.1 duplicate already-shipped visibility work, and the proposed enum contradicts the shipped text-column design. Co-Authored-By: Claude Opus 4.8 (1M context) --- docs/roadmap.md | 14 +++++++++----- openspec/changes/route-sharing/proposal.md | 9 +++++++++ 2 files changed, 18 insertions(+), 5 deletions(-) diff --git a/docs/roadmap.md b/docs/roadmap.md index eb9c1f7..d87a6ca 100644 --- a/docs/roadmap.md +++ b/docs/roadmap.md @@ -10,7 +10,7 @@ Five changes must ship before public announcement: | Change | Why it blocks launch | |---|---| -| [`route-sharing`](../openspec/changes/route-sharing/) | Visibility levels (private / public / shared-link) and forking. Federation depends on it. | +| [`route-sharing`](../openspec/changes/route-sharing/) | Per-user sharing (view/edit), forking, contributor tracking. (Visibility levels already shipped via `public-content-visibility`.) | | [`social-federation`](../openspec/changes/social-federation/) | The platform is described as federated — launching without it would be misleading. ActivityPub, WebFinger, inbound Mastodon follows. | | [`visual-redesign`](../openspec/changes/visual-redesign/) | Design system not yet implemented. Current UI is unstyled Tailwind. Must land before any public-facing announcement. | | [`wahoo-production-cutover`](../openspec/changes/wahoo-production-cutover/) | Wahoo sandbox rate limits make the integration unusable at scale. Ops task, not a feature, but launch-blocking. | @@ -22,12 +22,16 @@ Five changes must ship before public announcement: ### Phase 1 — Feature complete -Implement all launch-blocking changes above, in dependency order: +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: -1. `route-sharing` (no dependencies) -2. `social-federation` (depends on route-sharing for public routes) +1. `social-federation` (prerequisites already shipped) +2. `route-sharing` 3. `wahoo-production-cutover` (ops, can run in parallel) -4. `changelog` (no feature dependencies) +4. `changelog` ### Phase 2 — Polish sprint diff --git a/openspec/changes/route-sharing/proposal.md b/openspec/changes/route-sharing/proposal.md index 09c57b9..a06c8c6 100644 --- a/openspec/changes/route-sharing/proposal.md +++ b/openspec/changes/route-sharing/proposal.md @@ -1,3 +1,12 @@ +> **⚠️ Needs re-scoping before implementation (noted 2026-06-06):** This +> proposal predates `public-content-visibility` (archived 2026-04-24), which +> already shipped route/activity visibility as a plain-text column with three +> values (`private | unlisted | public`), public detail pages, public profiles, +> and an owner-facing visibility selector. Tasks 1.1–1.3 and 3.1 are obsolete +> (and 1.1's enum approach contradicts the shipped text-column design — see +> `packages/db/src/schema/journal.ts`). The remaining scope — per-user sharing +> (view/edit), forking, contributor tracking — is still valid and unshipped. + ## Why Routes in the Journal are currently invisible to everyone except the owner. There