### Annex 2: Product Development Methodology Scalus is a product, not a project. The distinction matters: a product evolves continuously, shaped by the people using it, through repeated cycles of ship, learn, adjust. The milestones are the initial high-level plan, what the platform delivers and when. Within those milestones, specific feature priorities, implementation choices, and component sequencing adapt based on what we learn from real users. That said, larger course corrections at the milestone level remain possible, particularly within Milestones 3 and 4, where the longer horizon makes adaptation more likely. We will reprioritise when user feedback, new opportunities and use-cases, or R&D findings warrant it. **Working from user feedback.** Lantr's product decisions are shaped by direct conversations with the teams building on Scalus today and the wider Cardano builder community (facilitated by Scalus Club). Pain points reported by users can override speculative roadmap choices. **Early testable versions**. Each capability ships first as a working preview: usable, but not yet polished. Users build with it, report what works and what doesn't, and the team folds the learning back into subsequent iterations. **Monthly iterations.** We practice trunk-based development (on average 45-50 commits/week), so new code reaches the main line daily. New features are activated for users every month, not at quarter-end, this compresses feedback loops and prevents large-batch failures. Three years of continuous Scalus delivery have run on this methodology. Quarterly reports make the reprioritisations visible to the oversight board and the public.