Work packages
Select a milestone
What changed from the original roadmap?
- Original Kafka stations and target notes preserved for reference, but status is not asserted. The web-write consumer is proposed to target a Postgres publication contract rather than ChatterActivityService.
- Chatter/SEO stubs replaced with concrete archive, historical-media delivery, runtime, Next and release milestones. Retained Salesforce Files versus S3 requires access/delivery proof; public content independence does not mean TBC/DRM org retirement.
- All original 33 task IDs retained and traceable. Existing data can be validated/adopted rather than re-imported. Likes are conditional; basic search no longer depends on their migration. Browse categories depend on retained product scope.
- Runtime tasks cover uploads, queues, badges, tokens/provisioning, moderation, SQL bulk proof and release operations. Original final Next umbrella is decomposed; no assertion that these tasks are equal-size tickets.
- Source files and records remain unchanged. No migration, deployment, flag change, credential retirement or deletion is authorized by this roadmap.
Search proposal: OpenSearch with Searchinator as a candidate integration; Searchinator source/contracts are unverified. Historical media: Salesforce Files and S3 remain alternatives until Chatter-independent access and withdrawal are proven.
Evidence and assumptions
Inputs: original ROADMAP_SUBWAY_MAP.html; tbc-chatter-migration-graph-2026-10-26.json; forums-to-tbc/docs analysis; inspected Rails/Slack/Next source; session architecture decisions. Production scope, mapping health, media coverage, enabled schedules, cache behavior, legal attachment policy and withdrawal SLA still require confirmation.
Original roadmap (unchanged) · Original 33-task tree · Extraction options research
Framework evidence: Next 16.2.12 self-hosting · QAPage eligibility · Connect tables.