Leaty · Master’s capstone · Technical documentation
Technical evidence notes
Checkpoint: October 4, 2026. Later limitations reviewed: October 9, 2026. Page prepared: November 7, 2026.
This page summarizes an existing engineering checkpoint for attendance generation and academic priority behavior. It is historical evidence prepared for the capstone website. No fresh app, backend, device or student study was conducted to create this page.
The reported counts are focused test results. They do not measure extraction accuracy, total application test coverage, student satisfaction, grade improvement or learning outcomes.
1. Method and scope
The checkpoint combined automated backend tests, offline mobile parser and repository tests, and scoped backend inspection of three example courses. Attendance rules and schedules were checked against confirmed course context. The backend inspection compared generated occurrences and priority ordering before and after the relevant change.
Cases included recurring schedules, known and missing semester boundaries, local time and daylight-saving behavior, excluded dates, ambiguous or unconfirmed source evidence, and inactive courses. These case categories describe the focused implementation checkpoint; they do not imply exhaustive coverage.
| Evidence | Result | Interpretation |
|---|---|---|
| Backend tests | 271 passed across 15 focused suites. | Regression evidence for the attendance and priority work in that checkpoint. |
| Offline mobile tests | 70 passed across three parser and repository test files. | Data parsing and repository behavior; not device acceptance. |
| Backend course inspection | Three example courses inspected. | Attendance occurrence generation and priority selection observed through backend services and stored records. |
2. Observed course behavior
- Two courses with a confirmed five-minute attendance sign-in rule generated upcoming occurrences with the appropriate cutoff.
- A separate course whose policy required attendance each class generated class-start attendance occurrences without inventing a grace period.
- An earlier homework deadline remained the overall Home priority ahead of attendance scheduled for a later date.
The inspection used guarded, read-only backend snapshots and computations. It did not manually rewrite student records or make new model calls. Normal backend scheduling generated the saved occurrence rows. These findings are backend evidence, not a record of a student using the device interface.
3. Known limitations
- Full-suite baseline failures: the complete repository test run was not green. Existing failures were reproduced and documented; the focused passing counts must not be presented as a full-suite pass.
- Later unresolved cases: the October 9 engineering record includes unresolved source-selection and same-day priority behavior. The October 4 checkpoint does not resolve or override that later evidence.
- Device acceptance: backend and offline tests alone do not establish correct behavior across the full mobile experience.
- Notification delivery: future push-notification delivery was not exercised by this checkpoint.
- Student evaluation: no student-feedback results, usability-study findings or learning-outcome conclusions are reported.
4. Relationship to the demonstration
The website’s 65-second video is an edited product demonstration made from recorded Leaty screens with a stylized opening. It shows several example courses and interactions. It is not an uninterrupted live session, a benchmark, or evidence that every demonstrated path passed the technical checkpoint.
The walkthrough images show QA101 review and Home screens and a separate QA102 change review. The images preserve the recorded interface and illustrate the workflow; they are not live account data.
5. Next evaluation work
- Resolve the documented source-selection and same-day priority cases and retain regression evidence.
- Complete scoped device acceptance and verify notification delivery separately.
- Plan student feedback and outcome evaluation after the technical demonstration, with a defined method and clearly reported sample.
6. Documentation provenance
This public summary is derived from the project’s internal engineering records. Internal account identifiers, service identifiers, deployment details and credentials are excluded.
RULES_ONGOING_ATTENDANCE_IMPLEMENTATION_2026-10-04.json— focused test counts, implementation scope and backend inspection.LEATY_WORK_BOARD.md— October 9 limitations and November 7 capstone preparation handoff.LEATY_CONVERSATION_DIRECTION_2026-08-31.md— student confirmation and the separation of academic priority from preparation help.