An elected board, governing in the open — policy manual, minutes, named votes
A traditional public school is governed by an ELECTED board of a public district, and its meetings are public business. The governance engine runs the board’s policy manual (draft → adopted → superseded → archived, an immutable version sequence under a closed, fail-closed lifecycle law that refuses an out-of-order or unauthorized transition) and its meetings (agenda, minutes, motions with a quorum-floored tally, and NAMED, on-the-record roll-call votes recorded into the minutes for open-meeting / sunshine-law transparency). This is the deliberate opposite of a secret ballot: a board vote is a public act by public officials, so each member’s yea / nay / abstain is kept, openly, by name. The governance and roll-call engines are built and their routes are registered. Honest-off hold: the minutes-ADOPTION finalizer and the cryptographic e-sign seal are unprovisioned, so a meeting is not marked adopted until that human step is wired. Nothing here is legal advice.
Built & wired · adoption finalizer honest-off
A sunshine-law public portal — the record a resident reads with no login
Sunshine law makes a public board’s ADOPTED record public, so the public portal is unauthenticated by design — and fail-closed on everything else. It returns ONLY meetings whose status is ‘adopted’: a draft, in-progress, tabled, or unadopted meeting is NEVER exposed, and named roll-call votes ride along only for an already-adopted meeting. A resident, a reporter, or a board watcher reads the adopted agenda, minutes, and the named votes of their public officials with no account and no login. The public-portal read is built and wired as the read-only twin of the staff-gated management routes — it shares the same governance engine with no fork. Honest today: because the minutes-adoption finalizer is honest-off, the public portal reads an empty adopted record until a board adopts its first minutes through the wired step.
Built & wired · adopted-only, default-deny
The policy manual & a staff-acknowledgment compliance ledger
A district’s board policy manual is a living, versioned document, and its staff have to acknowledge the policies that bind them. The policy engine publishes immutable adopted-text versions (you cannot silently rewrite an adopted version), walks each policy through its lifecycle under the closed law, assigns a per-requirement acknowledgment, and keeps the compliance ledger: who has acknowledged which policy version, and whose acknowledgment is still outstanding. A staffer reads the published manual and clears their own outstanding acknowledgments; a governance officer reads the cross-staff compliance ledger (a rep or teacher is hard-denied at the management surface). Persistence is durable and tenant-scoped (RLS deny-by-default). No money, no AI. The e-signature finalizer is an unprovisioned honest-off seam — never a fabricated signature.
Built & wired · durable, tenant-scoped
Attendance, ADA & membership — the math, honestly bounded
Attendance is recorded per class meeting, and the engine computes the state-reportable rollup a public school’s accountability runs on: a present/absent count, an average-daily-attendance ratio (NULL on a zero denominator — never a fabricated 0/0), and a distinct-student membership headcount. That is the honest arithmetic behind the numbers. What is HONEST-OFF: the STATE SUBMISSION channel. The export path stages and validates an extract but submits NOTHING, and the state-agency reporting code rides through as null until a per-state map is seeded and signed off. We do not file ADA to the state, do not calculate per-pupil funding or apportionment, and do not produce a named accountability report. The attendance and ADA/membership math is built; the submission channel is held.
Built math · state submission honest-off
District planning & accountability analytics — a built model, held for wiring
A public district plans and reports at the DISTRICT level: how many students will enroll next year, how its subgroups break down, and how its sites perform on the accountability indicators. The pure model is built — a deterministic enrollment projection over supplied history (it never fabricates a year that was not given), a subgroup breakdown with small-cell suppression (a subgroup with fewer than ten students is shown as ‘<10’, never an exact re-identifying count), an accountability dashboard (graduation rate, chronic absenteeism, achievement / attendance / discipline rollups), and a district-vs-site ranking. It is aggregate-only, district-scope, and reuses the platform’s FERPA small-cell wall. This is deliberately HONEST-OFF: the model consumes an INJECTED aggregate reader and is NOT wired to a live route yet; every indicator with no provisioned source reports off, never invented. The model is built; it is not surfaced live.
Built model · not yet surfaced (honest-off)
Open enrollment by right, a free records tier, and IDEA special education
A public school enrolls the students of its attendance zone BY RIGHT — there is no admissions decision and no lottery here (that is charterschool.network’s case, not this one). Register a resident student, finalize them onto the roster, and from there the records daily-driver carries a roster, a gradebook with GPA rollup, printable transcripts and report cards, and immunization-compliance tracking — and because a public school serves every student it enrolls, the IDEA special-education engine tracks compliance deadlines and logs service-minute delivery against what a plan requires. The student-records tier settles no money — records are the free tier. Honest scope: this is an enrollment-and-records daily-driver that COMPLEMENTS a district’s system of record; it is not a certified, full academic system-of-record, and its roster export is not an IMS/1EdTech-certified integration. Student plan data is minor PII — consent-gated, school-owned, and never made public.
Built · records tier free