Build Educamos
NOT REALLYback to the verdict
Before step 1
you will need
- Node and a local SQLite file
- Manual entry, or copy-paste from whatever the school actually sends you
- Nothing else, no school system access
Delivery order
Scaffold the smallest runnable application and document its commands.
done whenThe project starts from a documented command in a clean checkout.
Implement the primary data model and core workflow.
done whenThe main object can be created, read and changed end to end.
Add validation, safe failure states, and persistence.
done whenBad input is refused with a readable message and nothing is left corrupted.
Cover the critical path with automated tests.
done whenThe highest-risk behavior fails the suite when it breaks.
Exercise a clean install from the README and fix every missing step.
done whenA fresh clone reaches the first successful workflow using only the README.
That is the whole plan for Educamos. What it deliberately does not cover is below · check the gaps before you call it a replacement.
- Authoritative data: teachers enter grades and attendance in Educamos, not in your app
- Two-way messaging with teachers and the school office
- Official documents: report cards, absence justifications, enrolment and billing flows
- Timetable, room and substitution updates that come from the school's own scheduling
- Everyone else on it: the school, other parents, the administration staff
Need the files? The project pack on the verdict page hands your agent the whole brief · more education.