Bookmark Platform

BOOKMARK Roadmap Checklist

BOOKMARK is the July 2026 platform roadmap for a standalone digital comics and prose product built to compete with legacy storefronts while returning 85% of each sale to the author.

FaithEngine: 100-179
Bookmark: 200-279
Revenue Split: 85/15
Policy: Human-Anchored
First-50 Complete: 40

Blueprint

Date: July 2026

Mission: Build Bookmark as a standalone creator-first storefront and reading platform, with FaithEngine powering the internal publishing stack.

Architecture: C# and Python distributed microservices for panel segmentation, multi-language translation, and Stripe Connect payouts.

Target: 24 highly granular system components across ingestion, rendering, localization, synchronization, ethics, and revenue operations.

Human-Anchored Policy

Performance Anchor: Human performance remains mandatory for core character narratives.

Tier 1 Narrative: Lead character performances, core narration, and emotional story beats require human voice talent.

Tier 2 Utility: Licensed, ethical AI voice tools may support scratch reads, background assets, localization review, and internal iteration.

Human-Anchored Audio: QA certification signals that the emotional core of a narrative release was crafted by professional human talent.

Automation Dividend: AI-driven production savings are reinvested into human talent.

Verified HITL: High-impact narratives require verifiable human-in-the-loop certification.

Operational Balance: Automation is default, but visual manual override remains mandatory for final presentation control.

Strategic Conclusion

Monetization: No mandatory creator subscription. Default model is an 85/15 transaction split in favor of the author.

Localization: Claude 3.5 Sonnet plus retrieval-backed story bibles preserve tone, idiom, and suspense framing.

Immediate Timeline

Prototype path: Software scaling runs alongside proprietary comic and novel drafting.

Execution order: Use founder-authored assets to produce the first working motion-comic prototype before external studio expansion.

Operating Model

Transaction Velocity: Count successful reader purchases and order events before trying to forecast a headline revenue number.

Creator Retention: Returning creators, new releases, and repeat campaigns prove the platform is not a leaky bucket.

GEO Visibility

Generated Answers: Odyssey Universe assets should help Bookmark appear in AI-synthesized recommendations for independent comic publishing platforms.

Break-Even Target: Month 12 success means server, tooling, and human talent costs are covered by real platform activity.

Unchecked Internal Production System

Public Surface: Bookmark's public-facing platform is checked off.

Remaining Work: The real internal production system still needs layered motion prep, creator approval, voice certification, payout/accounting, localization, and automated publishing.

Why It Sits Under 240-279

Workspace: Items 240-259 cover the creator/operator tools for motion prep, approvals, release gates, and publishing handoff.

Services: Items 260-279 cover extraction, segmentation, localization, payouts, policy automation, observability, and final blueprint validation.

200-219 Site

  1. 200 Lock the public Bookmark narrative around comics, prose, and game lore on one transaction-driven platform.
  2. 201 Define the site architecture for landing, catalog, title, creator, roadmap, and support pages.
  3. 202 Publish the roadmap page and downloadable PDF tied to the sealed blueprint.
  4. 203 Build the release shelf with status, reading-order, and monetization controls.
  5. 204 Add title pages with cover, metadata, preview assets, and reading-order context.
  6. 205 Add creator and Human-Anchored production-note surfaces.
  7. 206 Add searchable release indexing.
  8. 207 Add responsive media support for covers, previews, trailers, and downloads.
  9. 208 Add preorder or purchase-intent capture tied to a real workflow.
  10. 209 Add consistent availability states across the catalog.

220-239 App

  1. 220 Define whether Bookmark is a reader app, creator app, or hybrid.
  2. 221 Lock the app shell for library, current reading, downloads, account, and settings.
  3. 222 Add authentication only if cross-device state truly requires it.
  4. 223 Add a library view with owned, followed, in-progress, and completed states.
  5. 224 Add a release viewer with cover, interior pages, and issue metadata.
  6. 225 Add reading-position memory, bookmarks, and resume behavior.
  7. 226 Add notes or highlights only if they support the core user.
  8. 227 Add offline download and sync rules.
  9. 228 Add release notifications for followed titles.
  10. 229 Add purchase, preorder, or entitlement handling tied to the catalog contract and 85/15 logic.

240-259 Workspace

  1. 240 Create Bookmark as a first-class built-in FaithEngine workspace.
  2. 241 Define project metadata for titles, volumes, acts, releases, and publishing state.
  3. 242 Add a workspace dashboard with active titles and blockers.
  4. 243 Add a title editor for covers, summaries, contributors, and sequencing.
  5. 244 Add asset lanes for covers, preview pages, PDFs, and promo art.
  6. 245 Add preview generation for site cards and title pages.
  7. 246 Add PDF export for the public roadmap and title packets.
  8. 247 Add publishing actions that push approved assets into the website output safely.
  9. 248 Add status gates to block incomplete releases.
  10. 249 Add draft, review, scheduled, live, and archived states.
  1. 250 Workspace Motion now defines motion-comic asset prep lanes for segmented panels, characters, bubbles, effects, and background plates; service automation remains open.
  2. 251 Add creator review tools for manual visual override after automated segmentation or translation passes.
  3. 252 Add lore and prose continuity binding so FaithEngine can coordinate story beats, captions, and motion timing from one source of truth.
  4. 253 Add human voice-performance ingestion, review, and release gating for all core narrative roles.
  5. 254 Add automation-dividend accounting that tracks production savings and required reinvestment into human talent.
  6. 255 Add motion-comic publication packaging that unifies still, motion, subtitle, and audio assets for Bookmark delivery.
  7. 256 Add release certification checks that reject missing human-performance or manual-override requirements on impacted titles.
  8. 257 Add multi-language subtitle and dubbing attachment rules that preserve lore-safe continuity across localized motion releases.
  9. 258 Add creator and operator audit views for segmentation edits, voice approvals, and publication sign-off.
  10. 259 Add a final workspace handoff that publishes the approved motion-comic package into Bookmark without manual file shuffling.

260-279 Services

  1. 260 Define the distributed service boundary between C#, Python, and FaithEngine orchestration.
  2. 261 Add asynchronous raster extraction for CBZ, CBR, and layered archive ingestion.
  3. 262 Add computer-vision panel segmentation with JSON structural output.
  4. 263 Add prose document ingestion for DOCX, PDF, EPUB, and long-form manuscript parsing.
  5. 264 Add continuity mapping metadata on PostgreSQL JSONB.
  6. 265 Add the cinematic frame-by-frame player.
  7. 266 Add the adaptive multi-layout manager.
  8. 267 Add the reflowable text presentation core.
  9. 268 Add the universal real-time state synchronizer.
  10. 269 Add the dynamic script-to-frame coordinator.
  1. 270 Add contextual localization services with retrieval grounding and glossary controls.
  2. 271 Add Stripe Connect payout flows for the 85/15 split.
  3. 272 Add payout accounting, audit trails, and settlement recovery paths.
  4. 273 Add a Human-Anchored policy engine.
  5. 274 Add verified HITL certification workflows for high-impact narratives.
  6. 275 Add automation-dividend reporting tied to human talent reinvestment.
  7. 276 Add sustainable-employment matching workflows.
  8. 277 Add manual visual override wherever automation affects publishable output.
  9. 278 Add observability, failure handling, and replay tooling for service jobs.
  10. 279 Freeze the Blueprint contract only after all layers validate together.