SCHOOL CONTACT

Tag: identity anchor

  • Cross-State Enrollment Without the Paperwork Flood

    The Challenge

    A family relocates across state lines, and a receiving district needs to confirm a student’s enrollment history, grade level, and any applicable accommodations before placement — usually a slow, paperwork-heavy process that can leave a student in limbo for weeks while records requests move between districts.

    The School Contact Solution

    Because the student’s identity anchor and its attestations persist across the transfer, the receiving district can submit a scoped query confirming current enrollment status and — flagged as one of the open legal-review items in the white paper’s appendix — any applicable accommodation status, alongside confirmation from the relationship layer that the accompanying adult currently holds guardianship rights.

    Within seconds rather than weeks, the attestation is returned and independently verifiable, without either district needing standing access to the other’s underlying student records. The student can be seated in the correct classroom on day one, and the paperwork that would otherwise need to survive a records flood becomes unnecessary for the initial placement.

    Demonstrates the federated attestation model replacing a centrally issued national number and the relationship layer’s guardianship confirmation, consistent with the open legal questions on cross-state data sharing.

  • The Four-Layer Identity Model, Explained

    Earlier drafts of the Contact Initiative proposed a single, centrally issued national identifier — a ten-digit number assigned at enrollment and later released back into a national pool for reassignment. Technical and legal review flagged two serious risks: a reassigned identifier can carry forward old associations, and a single national identity store is one high-value breach target for an entire population’s personal data at once.

    Version 5 replaces that design with a federated, four-layer model that delivers the same fast lookup and clear tiering — without either risk.

    The Four Layers

    • Identity anchor — a locally issued, opaque identifier for each person, controlled by the state or district (K–12) or institution/federation (higher ed). Never reused — retired and archived instead.
    • Federation / attestation layer — short-lived, cryptographically signed claims (“this anchor currently maps to an enrolled student”) held by the national registry. No bulk personal data.
    • Alias layer — the human-facing address people actually use day to day, freely rotatable without touching the anchor beneath it.
    • Relationship / authorization layer — a mutable table of who currently holds guardianship or delegated authorization for a given anchor.

    This separation is what lets the system handle situations the old single-number model couldn’t: a custody change becomes an update to the relationship layer, not a reissued child identity; a name change updates the alias without disturbing the anchor; and one person — say, a parent who is also a graduate instructor — can hold multiple independently scoped attestations under a single anchor.

  • Why American Schools Need a Verified Identity Layer

    The United States runs the largest and most decentralized education system in the world — roughly 13,000 K–12 school districts and several thousand colleges and universities, each building its own communication and identity infrastructure independently, platform by platform. No shared layer of verified identity connects any of it.

    The result shows up in ordinary moments that should be simple. A parent can’t always confirm that a message claiming to be from their child’s teacher is genuine. A receiving school can’t instantly verify a displaced student’s enrollment history. A voice assistant or classroom MI tool has no authoritative way to resolve an instruction as basic as “email my teacher.”

    Not Just an Inconvenience

    This fragmentation is the underlying condition that makes phishing, impersonation, shadow IT, and slow emergency response possible at scale across American education. Reported industry research indicates that a large majority of K–12 schools have experienced a cybersecurity incident in recent years, and that most publicly disclosed K–12 breaches trace back to a compromised vendor rather than the district itself.

    Beneath the statistics sits a simple structural gap: no unified framework exists to verify the identity of a sender in K–12 communication. A phishing email can convincingly imitate a district’s branding. A caller can claim to be a parent with no way for office staff to check the claim. A bad actor can register a fake teacher-style address and message students directly.

    School Contact proposes treating identity — for students, parents, teachers, and administrators alike — as shared infrastructure: persistent, verifiable, and portable across every transition in a person’s path through the education system. Read the full architecture in our White Paper Overview.