Stand-up notes — IA / sprint prep (2026-06-30)¶
Internal Fueled stand-up (not a client call). Source: Granola "[INT] CS Lewis: Daily Stand-Ups", 2026-06-30. Distilled into 02-product-domain.md, 04-mvp-scope.md, 05-feature-backlog.md, 06-content-migration-risk.md. Transcript (Granola): https://notes.granola.ai/t/09084763-bf20-472c-9188-096dc2c3fba6
These are the team's working assumptions as of this stand-up, not client-confirmed decisions. Several items are explicitly TBD or awaiting client confirmation.
Information Architecture Overview¶
- Splash-to-account flow removed: entry is now a single threshold-passing animation into the home screen
- Home screen is editorially curated, not algorithmic:
- Featured passage, featured themes, featured journeys (horizontal carousels)
- "What's new" module below, not an infinite content feed
- Hero slot always a passage or quote; other featured slots can be any content type (editor's choice)
- Themes are finite (~19 moods: courage, wonder, etc.):
- Each gets bespoke portal imagery and color scheme
- Taxonomy-driven, not editorially curated per theme page
- Architecture should support adding themes in v2 via CMS, even if not in v1
- Journeys are editorial vehicles grouping content into chapters:
- Chapters are ordered reading lists; any content type can appear
- Users can have multiple journeys in progress simultaneously
- Journey detail page shows title, overview, chapter list, and length
- Progress gated behind account creation (to save state)
Content Types and Structure¶
- All content pieces share: topic tags, theme tags, a "thought provoker" question, bookmarking, and reflections
- Passage/quote: the core product unit
- Audio playback via cloned Lewis voice (trigger mechanism TBD)
- "Deeper meaning" interpretation (CMS text block, AI-assist optional): likely deprioritized as client has no editorial team yet
- Source always shown: essay or letter links to full text; books show cover, synopsis, and publication date (with future Amazon CTA)
- Essays: standalone content pieces, ingested from Substack, featurable on home or in journeys
- Letters: short standalone writings, subtype of Lewis's works; whether to hold in app needs client confirmation
- Books: source reference only in v1, not full e-reader; cross-sell opportunity
- Podcasts: planned for a later phase
- Related content: acknowledged as a gap, deprioritized for now
Sprint Planning Prep¶
- Sprint ideally starts tomorrow (1st July) to align with delivery timeline; otherwise pushed significantly later
- Before tomorrow's sprint planning call, team needs to:
- Review Lina's existing backlog (epics already built) with IA context now understood
- Add acceptance criteria to all UI tickets (integration tickets can be bare-bones with a backend link)
- Link to current Figma designs (even if not final)
- Harish and Bavia to self-assign and divide tickets; estimates added by engineering, not Lina
- Starting with 3-5 well-defined tickets is fine; more added iteratively
- Sprint velocity: 30 points per sprint; estimates needed before tickets can be pulled in
- Lesson from Christianity Today: AC must live on the UI ticket, not just the epic
Content and Tech Stack¶
- Client meeting today (2026-06-30) to collect raw content; noted it won't map cleanly to Lina's schema yet
- Plan to manually shape a few sample pieces to validate the content model
- Tech stack recommendation to go to client; not expected to push back given non-technical nature
Next Steps¶
- Add acceptance criteria and Figma links to sprint-one UI tickets (Lina) — before tomorrow's sprint planning call; 3-5 tickets minimum to start.
- Assign, estimate, and divide all current Linear tickets (Bavia, Harish) — engineering owns estimates; divide subtasks before tomorrow's session.
- Collect raw content from client and map to IA schema — meeting today; shape a few sample pieces to validate the content model.
- Confirm with client whether letters should be held in the app — currently assumed yes, but not yet validated.