Product Features — Notion database (raw pull)¶

Source: Notion database "Product Features" — https://app.notion.com/p/fueled/e9f4dccd9d8b8315b895816213227423?v=c374dccd9d8b8377abea88d02fc0892c Database id: e9f4dccd-9d8b-8315-b895-816213227423 · Data source id: 7e74dccd-9d8b-834c-aa2f-0764f36f8ab3 Pulled: 2026-06-29 · Rows: 34

Verbatim distillation of the CS Lewis build feature backlog. Primary source; do not edit to reflect later decisions — supersede in .context/ instead.

Schema¶

Feature (title), Short Description (text), Category (select), Discipline (select), Priority (select), Quarter (select), Sprint (select), Estimate Days (number), Start/End Dates (date), Design Review Status (status), Test Build Status (status), Link to Designs (url).

Category: 33 Feature, 1 Research
Discipline: 20 Front End, 7 Back End, 4 Content Design, 2 BE + FE, 1 Growth
Priority: 23 High, 8 Medium, 2 Low, 1 Backlog
Design Review Status: 34 Not Started
Test Build Status: 34 Not Started
Quarter / Sprint / Estimate Days / Start-End / Link to Designs: all empty across 34 rows (not yet sprint-planned/estimated as of pull).

Features by discipline¶

Back End (7)¶

Audio Reading / voice clone pipeline · Medium
Trigger ElevenLabs voice clone generation from within a content piece in CMS; store and attach resulting audio file to piece; rollout priority queue (short pieces first); distinct from podcast player — this is listen-to-this-reading, not play-a-podcast

CMS Foundation · High
Payload (or equivalent) installation, hosting and environments; headless content API with caching strategy and rate limits; admin roles and access (editor, admin, viewer); media and asset management (audio hosting, CDN); draft and preview mode — the continuous platform pour that all editorial tooling sits on

Content data model + CMS · High
Piece schema (title, type, body, audio_url, theme_tags, read_time, buy_link, ai_interpretation, has_audio). Journey schema (title, description, colour, portal_shape, portal_icon, chapters[]). Chapter schema (name, opening_question, pieces[]). Theme taxonomy as finite controlled vocabulary. CMS or admin interface for authoring.

Journey / Portal editor · High
CRUD for Journey/Portal objects; chapter slot ordering and piece references (opening Q slot, primary reading slot, supporting content slots); per-chapter reflection override; journey metadata: name, copy, colour, icon, portal shape enum, opening question, featured flag

Podcast content type · High
CMS entry for podcast episodes: embed link (externally hosted), duration, transcript field, theme tags; separate shape from text content piece; no voice-clone pipeline

Tag-overlap graph computation engine · High
Backend service that indexes content pieces by theme tag combinations and computes piece-to-piece connection edges; deterministic and reproducible; result cached/indexed for fast graph queries; powers Explore traversal and related content surfaces

User data model (saves, progress, completion) · High
Saves table (user_id, piece_id, prompt_text, user_response nullable, saved_at). Journey progress table (user_id, journey_id, chapter_id, last_piece_id, last_opened_at). Journey completion table (user_id, journey_id, completed_at). Prerequisite for all Journey and Profile features.

BE + FE (2)¶

Account creation + unified gate flow · High
Three entry points (first save, Journey embark, chapter complete) share one account creation flow.

Push notifications infrastructure · Backlog
Device token registration (APNs + FCM), notification send pipeline, per-user preference storage. Only build if at least one notification type is confirmed shipping. Settings section is omitted entirely if not building.

Front End (20)¶

App shell + navigation · High
Native splash screen (iOS/Android asset config). Bottom tab bar (Home / Journeys / Explore / Profile). App-wide navigation stack, routing, and deep-link handling.

Audio playback · Medium
Conditional listen affordance on reading screen (shown only when piece has an audio version — per-piece flag in content model). Tapping opens inline player with play/pause and scrub, coexisting with text scroll without replacing the screen.

Auth — sign up + log in · High
Email/password registration and sign-in. Session management, token storage, form validation and error states.

Between chapters beat · Low
Transitional moment between chapter completion and the next chapter: completion acknowledgment, Journey position, next chapter title and opening question, and exit option. May be its own screen or an overlay state on chapter complete — TBD.

Chapter complete beat · High
End-of-chapter screen: reflection question, free-text input (skippable), save-to-soul-map action, account gate for guests. Writes chapter completion to progress model. Last chapter variant navigates onward to Journey complete instead of next chapter.

Chapter menu · High
Chapter position display, ordered piece list with content type and approximate length, begin/continue CTA into guided sequence. In-progress state tracks which pieces are read; continue resumes at correct piece. Scales from 2-piece to ~8-piece chapters.

Explore browse · High
Theme block grid — tappable, navigates into theme detail view. Theme detail has two content states: sparse (few pieces) and full (needs hierarchy). Curated 'start from a piece' row with content type and read-time metadata.

Explore inline search · High
Live in-place filtering of themes and pieces as user types into search bar — no separate results screen. Content reflows within the same screen. Animated browse-to-search state transition. Clear resets to default browse.

First-save → soul map creation moment · Medium
Custom intercept when a guest saves for the first time. Account creation flow runs, then save is applied and user lands on Profile with the first soul map entry. Distinct redirect path from standard sign-up flow.

Forgot password / reset · Medium
Password reset via email link. Covers: reset request form, email send, link validation, new password form. Standard flow, MVP-deferrable.

Guest mode · High
Unauthenticated app state throughout. Gate checks at three points — save to soul map, Journey embark, chapter complete — all redirect to account creation.

Guided reading sequence · High
Reading screen in Journey context: chapter progress indicator, piece-to-piece auto-advance prompt. After final piece, transitions to chapter reflection. Side links available but deprioritised vs. chapter flow.

Home feed · High
Modular scrollable feed with section components: Featured Journey hero (two states: new user editorial pick vs. returning user in-progress Journey with resume), More Journeys, What's New, Podcasts. Data model must support adding section types without an app update.

Journey complete screen · Medium
End-of-Journey screen shown once after the last chapter complete. Displays completed chapter trail, related Journey suggestions, onward navigation (Explore, Home, any chapter). Journey marked finished in data model but always re-enterable. Two states: first completion and revisit.

Journey landing · High
Journey identity header, editorial description, ordered chapter list with per-chapter state (not started / current / complete). Embark/continue CTA with account gate. Four screen states: guest, not started, in-progress, finished (includes related Journey suggestions).

Portal · High
Portal card component (CMS-assigned shape/colour/icon, Journey name, chapter count) rendered on Home and Explore. Custom tap transition animation into Journey landing. Portal shape is drawn from a preset family assigned per Journey in the CMS.

Profile / Soul Map · High
List of user saves, each showing piece title, reflection prompt, and user response if written. Tap entry navigates to that reading screen. Theme pattern section computed from tag distribution across all saves. Three states: guest (no data), sparse (1 entry), established (multiple entries).

Reading screen — standalone · High
Text reading surface for passage/letter/essay. Header (title, content type, read time), full body text, reflection prompt + save action (account gate if guest), engagement count, tag-ranked related content links, external buy CTA. Journey context variant replaces related links with next-chapter CTA.

Settings · High
Full-screen sub-page accessed via gear icon on Profile. Sections: Account (edit name, sign out with confirmation), Support (external links), Legal/About (webviews). Delete account. Notifications section only rendered if that feature ships. Guest state replaces account section with sign-up CTA, removes delete option.

Wandered off — persistent way-back UI · Medium
When user follows a side link mid-Journey, Journey context persists. Persistent UI element on subsequent screens shows current Journey and offers one-tap return to chapter position. Must survive arbitrary navigation depth.

Content Design (4)¶

Content tagging taxonomy and editorial guidelines · High — Research
Define the tag axes (themes, motifs, life stage, register, tone depth, etc.), populate the controlled vocabulary lists for each axis, and produce tagging guidelines for editors; prerequisite for CMS vocab tool, AI tagging, and graph engine — nothing downstream can be built or trained until this is locked

Deeper Meaning generation and QA workflow · Medium
AI generates interpretive annotation per content piece; result held in editorial draft state; editor reviews and approves before field goes live in app; separate from AI tagging — this is a per-piece annotation, not tag classification

Deeper reading (AI interpretation) · Low
Expandable section on reading screen, collapsed by default. Content is a stored text field per piece — no runtime AI. Expand/collapse interaction only.

Tag-overlap recommendation engine · Medium
Given a piece's theme_tags, return ranked list of related pieces and Journeys by shared tag count. Drives related links on reading screen and Journey suggestions on Journey complete. Pre-computed at content publish or fast runtime query.

Growth (1)¶

Engagement tracking · High
Deduped view event per user per piece. Aggregate count stored per piece and surfaced on reading screen.