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-07-12
74
Features built
0
In progress
2
Planned
Beta Reader Manuscript Watermarking
Invisible watermarks are now embedded in every scene shown to beta readers. If a manuscript excerpt surfaces outside the platform, the watermark identifies both the original author and the specific reader who leaked it.
- ·Two complementary layers applied simultaneously — one detectable by AI text extraction, one by AI vision analysis of screen captures
- ·Watermarks encode both author name and reader identity
- ·Fully invisible to humans at all reading distances and in all rendered contexts
- ·Applied only to beta readers — general public readers see nothing
- ·A decode utility can forensically recover the full payload from any extracted copy
Beta Reader Comment Threads
Beta readers and authors can now have full conversation threads under each scene of a manuscript. Readers in the same campaign see each other's comments. The author can reply from the Write view without leaving the editor. Every comment records which scene revision it was made on.
- ·Comment threads appear below scene prose in the ReadingTree (reader view) and in an inline panel inside the Write view (author view)
- ·Author comments appear with a gold Author badge; any participant can reply to any top-level comment
- ·Same-campaign scoping: readers see only their own campaign's thread plus general author notes
- ·Author replies are automatically visible in the correct campaign thread without any extra configuration
- ·Each comment records the scene revision it was made on — visible as a small badge on the comment
- ·Cmd/Ctrl+Enter submits from any textarea; no page reload required
- ·Author notified in-app whenever a beta reader posts a comment
Beta Reads in The Hearth
Approved beta readers now see their active manuscripts directly in the Library (The Hearth). A new Beta Reads section surfaces above the reading list tabs, showing each campaign with a deadline countdown, state-aware CTAs, and a review prompt when reading is complete.
- ·New GET /api/beta-reads returns approved, completed, and expired applications with campaign title, author name, and review status
- ·Crimson rule section header matches the wing personality of The Stage
- ·Left border stripe encodes state: crimson (active), muted gold (completed), grey (expired)
- ·Deadline countdown turns crimson at ≤3 days remaining
- ·Active reads show Read → link to /beta/{id}/read
- ·Completed reads prompt Leave review → if not yet reviewed, or show Reviewed ✓
- ·Section invisible to users with no beta history — no empty state
Beta Campaigns: Launch from Studio
Authors can now initiate or manage a beta reading campaign directly from the Studio manuscript toolbar. The Beta button sits alongside Plan, Write, Review, Chat, and Export — and knows whether a campaign already exists for this book.
- ·No active campaign: '+ New Campaign' button (crimson-tinted) appears in the Studio toolbar
- ·Active campaign: 'Beta ↗' (subtle bordered) links to the campaign manage page
- ·Studio layout fetches bookId, betaId, worldName, and seriesName from the draft record
- ·New campaign URL encodes ?bookId, ?world, ?series — context appears as a line under the form header
- ·New campaign form auto-selects the matching Studio draft and skips to step 2 with title and book pre-filled
- ·Beta campaign manage page shows '← Manuscript' breadcrumb link back to the Studio plan view
Beta Campaigns: Studio Draft Support
Beta campaigns can now use a Studio draft as the manuscript source — not just uploaded files. Selecting a Studio draft in the campaign wizard auto-fills the linked book and target audience.
- ·Campaign creation lists Studio drafts alongside uploaded manuscripts
- ·Selecting a Studio draft auto-populates Linked Book and Target Audience
- ·Approved readers land on the public book page (ReadingTree) instead of the legacy file reader
- ·manuscriptSource field distinguishes studio vs. upload campaigns
Beta Reader: Real-time Deadline Enforcement & Reapproval
Access is checked against the live deadline at every entry point — no gap between expiry and the nightly cron job. Authors can reapprove expired readers to grant a fresh deadline.
- ·All read-access checks gate on deadlineAt > now in real time
- ·Campaign detail page shows expired status immediately when deadline passes
- ·Days remaining counter on the reader's campaign page (amber < 7 days, red < 3 days)
- ·Reapprove button in Dashboard → Beta → Applications for expired readers
- ·Reapproval sends a fresh approval email with a new deadline
Beta Reader: Inline Scene Comments & Threads
Beta readers and authors hold full threaded conversations under each scene of a manuscript. The author replies from the Write view. Comment threads are campaign-scoped so readers see only their own campaign's discussion.
- ·Comment threads appear below scene prose in ReadingTree (reader) and as an inline panel in the Write view (author)
- ·Author badge in gold; any participant can reply to any top-level comment (one level deep)
- ·Same-campaign scoping — reader sees their campaign thread plus general author notes
- ·Each comment records which scene revision it was made against
- ·Author notified in-app when a reader posts; readers notified when author replies (fan-out via insertMany)
- ·Cmd/Ctrl+Enter submits; no page reload
- ·Plan view amber dot on scenes with unaddressed comments newer than the latest revision
Beta Reader System
Authors run beta reading campaigns for manuscripts. Readers discover campaigns, apply, read, and submit structured reviews. Deadline tracking, nightly expiry cron, and admin config included.
- ·Campaign discovery at /beta with genre filter and pagination
- ·Structured review form: per-category star ratings, comments, strengths/weaknesses
- ·Nightly cron auto-expires past-deadline applications and sends warnings
- ·Admin → Beta Config: default deadline days, warning window, max extensions
- ·Manuscript revision history with reader notification on new upload
Beta Cancellation: Reader Email
When an author cancels a beta campaign, every approved reader now receives a personalised email alongside the existing in-app notification. The email is sent via the platform Resend key.
- ·betaCancelledEmail() template added to src/lib/email.ts
- ·DELETE /api/beta-requests/[id] now sends one email per affected reader before expiring their applications
- ·In-app notification still fires as before; email adds a second channel
This log tracks platform features, not individual content. For questions or feedback, get in touch.