Product Documentation¶

Product documentation defines who we build for, what we build, and why — connecting the project vision to technical implementation through a traceable chain.

Traceability Chain¶

graph LR
    V[Vision] --> P[Personas]
    P --> US[User Stories]
    US --> PRD[PRDs]
    PRD --> RM[Roadmap]
    PRD --> TD[Technical Design]
    TD --> ADR[ADRs]
    TD --> Code[Implementation]

    classDef active fill:none,stroke:#1976D2,stroke-width:2px,color:#1976D2
    classDef special fill:none,stroke:#8E24AA,stroke-width:2px,color:#8E24AA
    classDef infra fill:none,stroke:#00C853,stroke-width:2px,color:#00C853

    class V,RM special
    class P,US,PRD active
    class TD,ADR,Code infra

Every feature should be traceable from a persona need through user stories and requirements to technical design and code.

Sections¶

Personas¶

Four personas representing the spectrum of Loryth users — from expert self-hosters to non-technical family members. Used in user stories and PRDs to ground features in real user needs.

User Stories¶

User stories organized by epic (one per service domain plus cross-cutting workflows). Each story follows "As a {persona}, I want {action}, so that {outcome}" format with acceptance criteria.

Requirements¶

Product Requirements Documents (PRDs) for each major service. Each PRD links personas, user stories, functional requirements, and acceptance criteria — with traceability to roadmap items and technical designs.

Quick Reference¶