What problem does it solve? It gives developers and AI assistants the full functional context of the Toollab school management platform, so any change request can be correctly situated within the end-to-end business flow instead of being treated in isolation. ## Core Features & Use Cases - Complete role-based journey: Maps the flows of super-admin, director, registar, teacher, and family from school creation through enrollment, payment, attendance, decisions, and year rollover. - Business rules reference: Documents enrollment replace rules, payment validation (422 on overpayment), decision types per cursus, and year-closing behavior (409 on writes to closed years). - Explicit non-features: Lists what does not exist (no student portal, no online payment, no automatic re-enrollment, no soft delete) to prevent wrong assumptions. - Use Case: When asked to modify the enrollment screen, consult this Skill to understand that enrollment follows a replace rule per cursus and type, snapshots pricing, and requires a student UserRole on the family. ## Quick Start Explain where the family payment feature fits in the overall Toollab user journey and what rules apply to it.
