Automated grade verification and homework accountability for parents. Pulls assignment data, detects grading errors, tracks submissions, and delivers daily reports to the whole family.

The problem it solves

Students' grades are scattered across disconnected school platforms. Teachers manually transfer scores between systems. When transfers fail (or students don't submit), parents have no way to verify what happened or when. Students who know their material score one hundred on quizzes and tests but earn C averages because five-point assignments slipped through unnoticed. The gap between "knows the material" and "has the grade" is almost entirely submission behavior, not ability — and that gap is invisible until it's too late to fix.

What it does

Every morning at 6 AM, an automated pipeline authenticates against the school's learning management system, pulls assignment metadata for each child, joins it against grading data from the gradebook, and produces three views of the same truth:

• For the student: a "What's Important Now" report in their Obsidian vault — due dates, progress bar, deep links to each assignment, and wins to celebrate. Auto-syncs to their phone.
• For the parent: a "did they do their homework?" summary delivered by Discord, email, SMS, or web dashboard. Submissions, new zeros, grade changes, in plain language.
• For the operator: the full forensic report — trends, zero patterns, screen-time correlation, delivery receipts, error alerts. Built for the parent who wants to see the whole picture before bringing it up at the dinner table.

The grading-error detection

Some learning management systems set a "submitted" timestamp the moment a student merely opens an assignment page, creating phantom submission records that look real to the parent and the teacher. Homework Forensics uses the authoritative submission signal from the underlying gradebook, not the optimistic timestamp from the LMS, and flags the discrepancies. This distinction was discovered when a parent caught two assignments incorrectly marked "submitted." It is now a core feature of the system.

The architecture

Two-repository architecture: an engine repository owned by Massfeller LLC containing the collection, formatting, and delivery pipeline; and per-family vault repositories owned by the families themselves containing their children's personal data and generated reports. The engine never persists student data — it fetches, formats, delivers, writes into the family's vault, and exits. Each family's vault is isolated with its own access controls. The pipeline runs daily before the school day starts.

Status

Currently in active family use. The architecture supports multi-tenancy — one vault repository per family, one engine for all — and may be extended to additional families if and when that demand emerges. Source remains private.

Privacy

Homework Forensics's privacy practices are governed by the umbrella Massfeller LLC Privacy Policy. Student data lives in private repositories on infrastructure controlled by the family operating the system. The engine sees data only long enough to format and deliver it; persistent student data is never written to LLC-owned infrastructure. We do not retain academic data outside the family's own vault.

Support

For questions about Homework Forensics, write support@massfellerllc.com.