| name | kmp-baseline-validation-blueprint |
| description | Tracks the validation of explicitly defined end-to-end user journeys in the application. |
User Journey Validation
This document contains a rigorous, multi-layered testing plan tailored precisely to the actual end-state functionality of the application. Journeys represent the final shipping product, not intermediate development steps (e.g., validating a navigation graph with empty placeholder screens).
Execution Protocol
- Agent Validations: The AI agent will first execute any programmatically verifiable tests, scripts, or inspection to confirm the behavior.
- User Validations: The AI agent will then prompt the User to manually navigate the application UI to functionally experience the journey.
- Bug Tracking: If a journey fails validation, the AI agent must abort the validation process, update the appropriate phase in
kmp-baseline-guide-task with a new **Agent Action**: Fix bug [...], and resolve the issue before re-attempting validation.
Journey 0: KMP Baseline (Joke App)
Goal: Verify that the core KMP stack (Calf, Room, Nav 3, Ktor, Gemini, Material 3) is working together correctly before adding app-specific features.
Journey 1: Writer's Room
Description: Verify that the user can generate, fine-tune, edit, and persist a strictly formatted script.
Actions:
Journey 2: Recording Studio
Description: Verify that the user can record video using the front-facing camera while following the teleprompter.
Actions:
Journey 3: Editing Studio
Description: Verify that the user can precisely define sections of the recorded video to trim and recover.
Actions:
Journey 4: Publishing Studio
Description: Verify that the user can seamlessly share the generated and edited video to external channels.
Actions:
Journey 5: Archives
Description: Verify that users can see past projects and restore an archived project to active status.
Actions:
Notes for Blueprint
- Philosophy Shift: Validation tasks must focus exclusively on end-state functionality representing the final shipping product, not intermediate development steps (e.g., "Phase 1: Core Navigation" with empty screens).
- Journey 1 (Home Screen): Focus on thematic consistency (background images, readable text contrast, non-default colors) and dynamic state routing (Active project routing vs. "Start New Video"). Remove intermediate placeholder UI tests. Ensure "Archives" is always accessible.
- Writer's Room: Added strict formatting validation requirements for the LLM output. The script must ONLY contain teleprompter words and timestamps (e.g., "0s-5s: Hello..."), stripping conversational filler or background context.
- Editing Studio: Collapsed "Phase 5 (Polish)" requirements into the core Editing Studio journey. The validation must explicitly check for 0.1s granularity seeking, visual indicators of skipped segments (red blocks), the "Preview without Skipped Frames" feature, and accurate native trimming logic.
- Archives: Explicitly added an Archives journey to ensure the user can see past projects and restore an archived project to active status.