saascode
education & learning·run 237 · Jun 2026

DistrictGate

A K-12 governance workspace that inventories AI systems, maps reviewed state and European applicability separately, runs evidence-based vendor review, and assembles correctable board packets.

Genesis score6.38/10
Make DistrictGate real.0/500
500 more votes and DistrictGate is authorized for build.
0%500 to authorize
Backing is the vote. When an idea crosses 500, we pull it into the build pipeline and ship it for real — the votes decide what gets built next, not an editor.
The opportunity
2Confirmed 2026 policy milestones
0Dedicated district products found
The case

Ohio required covered public-school entities to adopt an AI policy by July 1, 2026, and the supplied European transparency milestone arrived August 2, 2026. Both dates have passed as of authoring. DistrictGate maintains current policy, system inventory, vendor evidence, applicability decisions, exceptions, disclosures, review dates, and board reporting. It does not assume an Ohio district is subject to European rules, turn a vendor score into legal compliance or student safety, or infer practice from contract claims. Each requirement retains authority, jurisdiction, covered entity, effective version, qualified reviewer, and expiry. Vendor assertions, contract terms, technical observations, district deployment, classroom use, incidents, approvals, and outcomes remain separate. The single verified rostering interface requires a commercial subscription and does not prove access to vendor security or AI behavior. Student, family, and staff data is minimized; the product never evaluates teacher or student performance.

Who pays — and why

The superintendent's office, technology, privacy, procurement, legal, curriculum, or board-governance leader at a covered K-12 district.

Market signalValidate by district, systems, and review workloadEnterprise governance packaging is an observed market reference, not fixed product pricing
What it unlocks
A district AI-system register linking vendor, contract, purpose, users, data, decision role, integration, owner, approval, deployment, disclosure, incident, and review.
A requirement and evidence matrix that separates source law or policy, applicability candidate, qualified decision, vendor assertion, supplied artifact, technical observation, gap, remediation, exception, and expiry.
A board packet preserving policy version, reviewed inventory, component findings, approved uses, open risks, incidents, community input, decisions, corrections, and publication scope.
How Genesis scored it
6.38across seven criteria
tension 7temporal 8blindspot 5buyer 8leverage 6convergence 5why-not 5
8
Temporal window

Confirmed July and August 2026 milestones create current-state review pressure.

8
Buyer persona

District technology, privacy, procurement, legal, and board leaders have a concrete policy and vendor-review workflow.

5
Why nobody did it

New district policy duties and AI adoption expose the gap, while vendor governance is familiar.

Why it scored well

Confirmed deadlines, a clear district buyer, one usable interface, and an empty dedicated product category support a timely governance workspace.

What's holding it back

Both deadlines have arrived, no vendor-behavior interfaces were verified, law and policy vary, human review is substantial, and horizontal governance vendors can enter.

Signals detected3 sources crossed
SignalState education authority

SignalEuropean authority

SignalGap research

Direction briefdistrictgate.md
districtgate.md
Want this pointed at your vertical?Point Genesis at your own market and constraints — it invents adjacent, fork-ready ideas, private to you before they hit the public feed.

Discussion

?

No comments yet — be the first to weigh in.