Stream Facility
Development Log
A running record of what's been built, what's underway, and what's on the horizon. Updated as the platform grows.
Last updated 2026-09-01
99
Features built
0
In progress
5
Planned
Digital Product Delivery
Automated file delivery for digital shop products. On purchase, the buyer receives a signed, time-limited download link. Physical products gain shipping address collection and fulfillment tracking.
- ·Signed download URL generated on webhook confirmation
- ·Files stored in Vercel Blob; access logged per download
- ·Physical: shipping address collected at Stripe checkout
- ·Seller marks orders shipped; buyer notified with tracking info
Pro Tier Exclusive Features
Pro tier is defined and gated but exclusive features beyond AI Chat are not yet designed. Known candidates include manuscript editing tools, priority discovery placement, and advanced analytics.
- ·Manuscript editing and polish tools
- ·Priority placement in Lobby discovery
- ·Advanced analytics: read counts, time-on-page, completion rates
- ·Custom domain support for author profile pages
World Licensing — Fan Fiction & Collaboration
Authors will be able to license their world and codex to other users, allowing fans to write their own works set in that world. Five license types cover every arrangement from open community use to paid access with royalty splits. The originating author retains full control; licensees work in a snapshot copy with terms locked at clone time.
- ·Five license types: private (author-only), free (open/no royalty), access (one-time fee), access + royalty (fee plus revenue share), royalty-only (free to use, author earns from fan sales)
- ·Author sets royalty % from 0–50; platform caps at 50%; terms are snapshot at clone time and cannot be changed by either party retroactively
- ·Clone scope: world document + all codex entries only — no books, series, or studio drafts
- ·Discovery surfaced on the originating author's public profile and the world's public page
- ·Invite flow reuses the existing shop gift mechanism — direct grants to specific users without going through the public request flow
- ·New 'Licensed Worlds' tab in Dashboard → Worlds; fan's world picker includes licensed worlds
- ·Fan books carry a licensedWorldId reference — the hook for royalty tracking when manuscript sales ship
- ·Platform fee: flat amount (default $1), admin-configurable, applies to licensing transactions
Group Worlds — Multi-Author Collaboration
The world licensing system doubles as a multi-author collaboration mechanism. Authors can invite co-writers directly into their world using any license type — for pure collaboration, a private invite grants free read-only codex access and the ability to write books set in the shared world. The originating author is the world owner with full control; collaborators work alongside them without touching the source material.
- ·Built on the world licensing infrastructure — no separate collaboration system needed; the license type determines the terms
- ·Private invite-only worlds function as creative writing groups: the originating author hand-picks collaborators, no public listing, no fee
- ·Collaborators see the world in their Licensed Worlds tab and can set books as 'set in [world]'
- ·Codex entries from the licensed world are read-only reference — collaborators cannot edit the originating world's material
- ·Invite flow via the existing shop gift system — same UX as gifting a subscription key, no new UI required
- ·Depends on World Licensing phase being complete first
Messaging System Consolidation
Two parallel messaging systems currently exist in the codebase. This phase consolidates them, cleans up the orphaned routes, and enables author-to-author direct messaging — which is already built behind a feature flag.
- ·Active system (message_threads / thread_messages): powers /dashboard/messages with contact support and direct message thread types — fully functional for support tickets
- ·Orphaned system (conversations / messages collections): API routes built but no dashboard UI ever connected; effectively dead code to be removed
- ·Direct messaging is already built in the active system behind the directMessagingEnabled feature flag — enabling it is the main unlock
- ·Message button to be added to public author and reader profile pages to initiate a direct thread
- ·Orphaned routes and collections cleaned up after confirming empty in production
- ·The world licensing invite notification will use the existing thread system — no additional messaging infrastructure needed
This log tracks platform features, not individual content. For questions or feedback, get in touch.