Browse pages
Overview
The Learn pages explain LiteSpec, the standard for building one business application from written rules that tools check, to a reader who is new to it: the problem it solves, how its parts fit, how to read the standard, and how a team adopts it. They apply to every project and role, and they state no rules of their own: each rule lives on the standards page they link to. Technical leads and developers read them in order below when they evaluate or adopt LiteSpec, before opening any rules page.
Reading Order#
- Why LiteSpec Exists: the problem LiteSpec solves, for a team that is deciding whether LiteSpec fits.
- How LiteSpec Works: the standard, the records, the model, and the tools, traced through one Claimwick use case.
- Read the Standard: project selections, page arrangement, and provision IDs; how to find the rules that apply to a project.
- Records and the Project Model: the four layers, what a project writes down, where each record lives, and what the model builder computes.
- Reading Tracks: which records to read in which order: why before how, one journey end to end, one module end to end, and the structural words.
- How the Tools Fit Together: the CLI, the analyzers, and the site, in the order one change moves through them.
- How LiteSpec Compares: LiteSpec beside ten other approaches to spec-driven development, and when each fits.
- Lineage: the practices LiteSpec borrows from, the words it takes from each, and what it does differently.
- Work with Agents: how an agent finds the rules, what it decides alone, and what it brings back.
- Adopt LiteSpec in Steps: adopting LiteSpec by conformance level: the record model at
records, traceability attraced, and the full contract atfull, with the records path through the tutorial.
Next#
When you are ready to build, follow Start a Consumer Repository.