Skip to Content
📚 MyStoryFlow Docs — Your guide to preserving family stories

MyStoryFlow Architecture Documentation v1.1

Current Version: 1.1 Last Updated: 2025-01-29


Quick Start

New to the project? Start here:

  1. Read the Quick Reference - One-page summary of key decisions
  2. Review the v1.1 UX Roadmap - Full implementation plan
  3. Understand our Competitive Position - Why we’re different

Core Concept: Story = Chapter

The most important architectural decision: A story IS a chapter.

When you add a story to a book, it becomes a chapter. There is no intermediate layer.

Voice/Conversation → Story → Book ↑ ↑ ↑ artifacts the unit ordered (preserved) of content collection

Document Index

Active Documents (v1.1)

DocumentPurposeWhen to Read
Quick ReferenceOne-page decision guideBefore making any changes
v1.1 UX RoadmapFull implementation planPlanning implementation
Implementation Gap AnalysisCurrent vs target state gapsStarting implementation
Competitor AnalysisIndustry researchUnderstanding positioning
Database Schema v1.1Database designDatabase changes

Key Decisions Summary

DecisionChosen OptionRationale
Content ModelStory = ChapterIndustry standard, reduces complexity
Naming”Story Projects”Preserves storyteller_name semantics
Dialog LibraryRadix (not Headless UI)Already in codebase
EditorTipTap with progressive disclosurePower + simplicity
Artifactssource_recording_ids[], source_conversation_ids[]Preserve original voice
Book Structurebooks.story_ids[] arraySimple ordering

Implementation Phases

PhaseFocusStatus
1Foundation & NavigationNot Started
2Unified Content CreationNot Started
3Story-Centric Data ModelNot Started
4Editor Progressive DisclosureNot Started

Current Database State

Based on actual database validation (2025-01-29):

FeatureStatusNotes
books.story_ids UUID[]EXISTSAlready implemented
stories.source_conversation_ids UUID[]EXISTSAlready implemented
stories.source_recording_ids UUID[]MISSINGMigration needed
books.section_breaks JSONBMISSINGMigration needed
book_chapters tableActiveTo be deprecated

Version History

VersionDateDescription
1.1.12025-01-29Added implementation gap analysis, current vs target state
1.12025-01-29Story = Chapter model, competitor analysis, schema updates
1.02025-01-29Initial architecture + UX review combined