Pending Features & Documentation Gaps

This document consolidates all features that are documented but not yet implemented, or have incomplete implementations. Generated from a comprehensive documentation-to-code sync review.

Summary

High Priority - Core Functionality Gaps

Print Ordering System

Status: 🔲 Not Implemented (documented, stub code only)

What’s documented:

• Order professional printed books
• Multiple book formats and sizes
• Binding options (hardcover, softcover)
• Shipping address collection

What exists:

• /orders/page.tsx contains only TODO comments
• No fulfillment integration
• No payment processing for orders

Recommendation: Either implement or remove from marketing/features.

Book Design Tools

Status: 🟡 Minimal Implementation

What’s documented:

• Cover customization
• Page layout options
• Typography controls
• Color scheme selection
• Template selection UI

What exists:

• Basic chapter management
• Story ordering within books
• Backend template support (no UI)

Missing:

• Cover design interface
• Layout editor
• Typography/color controls
• Template selection UI

Offline Capability

Status: 🔲 Not Implemented

What’s documented:

• Basic functionality works offline
• Local content caching

What exists:

• No service worker
• No IndexedDB caching
• No offline mode

Recommendation: Remove from features or add to roadmap with timeline.

Medium Priority - Feature Completeness

Content Preservation System

Status: 🔲 Design Only (1000+ lines of documentation)

What’s documented:

• Multi-level preservation (browser, client, server, backup)
• Keystroke-level recovery
• Page visibility preservation
• Conflict resolution
• Version history UI
• Rollback mechanisms

What exists:

• Basic Supabase auto-save
• No multi-layer preservation
• No conflict resolution
• No version history UI

File: /apps/docs-app/content/technical/content-preservation-system.mdx

Story Suggestions & Memory Additions

Status: 🔲 Not Implemented

What’s documented:

• Family can suggest new story topics
• Memory additions from family members

What exists:

• No suggestion UI
• No memory addition interface

Chronological Timeline

Status: 🔲 Not Implemented

What’s documented:

• Timeline view of stories by date
• Visual story organization

What exists:

• List/grid views only
• No timeline visualization

Real-Time Collaboration

Status: 🟡 Framework Only

What’s documented:

• See family contributions immediately
• Real-time updates

What exists:

• Supabase real-time capability
• No UI implementation for live updates
• Uses polling/refresh patterns

Low Priority - Future Enhancements

Multi-Factor Authentication

Status: 🔲 Planned (documented in architecture)

What’s documented:

• TOTP-based 2FA
• SMS verification
• Backup codes

What exists:

• Supabase Auth (Google, Apple, Magic Link)
• No MFA implementation

BroadcastChannel Cross-Tab Sync

Status: 🔲 Planned

What’s documented:

• Real-time session sync across browser tabs
• BroadcastChannel API usage

What exists:

• localStorage storage events (fallback method)
• Works but less robust than BroadcastChannel

Session Encryption

Status: 🔲 Planned

What’s documented:

• End-to-end encryption of session data
• Client-side encryption

What exists:

• Database-level encryption (Supabase)
• TLS in transit
• No E2E client encryption

Story Analyzer (Entire Product)

Status: 🔲 Design Phase Only

The Story Analyzer is fully documented as a future product but has zero implementation:

Documented features (43 total):

• F000-F043 feature specifications
• Monorepo setup plans
• Database schema designs
• AI analysis engine
• Genre detection
• Report generation
• Coach marketplace
• Beta reader network

What exists:

• Documentation in /apps/docs-app/content/analyzer/
• No analyzer-app directory
• No database tables
• No API endpoints

Recommendation: This is correctly marked as future product specification.

Content-OS Automation

Status: 🟡 Partially Implemented

What’s documented:

• Full Agent-OS pattern (spec → tasks → execution)
• 7 agent definitions
• Task orchestration
• Output assembly
• Claude Code integration

What exists:

• Agent definitions (markdown files)
• Image generation scripts
• Podcast audio scripts
• Workflow documentation

Missing:

• generate_spec.py - specification generator
• execute_tasks.py - task executor
• validate_output.py - output validator
• lib/ directory - core Python libraries
• Task orchestration layer

Alternative: JavaScript pipeline in /scripts/pipeline/ is functional.

API Documentation Gaps

Outdated Documentation

The API reference documents endpoints that don’t match implementation:

Undocumented Features (140+ endpoints)

Many implemented endpoints have no documentation:

• Achievements system
• Analytics tracking
• Conversations system (15+ endpoints)
• Import functionality
• Privacy/GDPR endpoints
• Recording management
• Reference data management
• TTS/STT integration

Documentation Accuracy Summary

Fixed in This Review

• Architecture docs: Role hierarchy corrected
• Architecture docs: MFA/BroadcastChannel marked as planned
• Architecture docs: Impersonation time limits corrected
• Features docs: Added implementation status indicators
• Features docs: Added Gift/Import/Achievements sections
• Content-OS README: Added honest implementation status
• Content Preservation: Marked as future feature
• API docs: Added status indicators
• Admin docs: Expanded with actual features

Still Needs Work

• API endpoints need comprehensive audit
• 140+ undocumented endpoints need documentation
• Campaign creation flow needs new documentation
• Family API structure needs documentation update

Recommended Priority Order

Immediate (blocks user workflows):

1. Remove print ordering claims OR implement
2. Update API documentation accuracy

Short Term (improves user experience): 3. Book design tools enhancement 4. Story suggestions feature 5. Chronological timeline view

Medium Term (product enhancement): 6. Content Preservation System 7. Real-time collaboration 8. Offline capability

Long Term (future products): 9. Story Analyzer (full product) 10. Content-OS orchestration completion 11. MFA and advanced security