Living product specification

Implementation

• Maintain an authoritative product spec (vision, corpus, technical notes) that stays close to the code.
• Link spec sections to epics and tasks on the board where helpful.
• Spec is authoritative for this repository only—no dependency on legacy HTML, predecessor apps, or assets outside the repo.
• Add questions to this task where the spec is unclear.
• Ensure spec is easily readable by non-technical stakeholders - except for the technical and non-functional requirements.
• Use Markdown rendered through mdsvex (plain Markdown + MDX-style composition when needed).
• Specification routes should be accessible from the roadmap and vice versa.
• Create a sticky toc that is always visible and allows the user to navigate to different sections of the spec.
• Single-user product only—one person uses the app to prep and play; no multiplayer.
• v1 rules math stays client-side only; no server-side authoritative validation required on the roadmap.
• First release targets Dungeons & Dragons 5th edition (5e).
• Living product spec source: src/routes/product/ProductSpec.svelte.md.

Questions

None yet.