Author: School Contact Iniciative

  • Identity Solves Half the Problem. California Associates Is Our Answer to the Other Half.

    It’s 7:40 a.m. and a parent is typing a message to her daughter’s teacher: she’ll be out Thursday, dentist appointment. Some AI-powered scheduling assistant sitting inside the district’s messaging platform is going to read that, figure out which daughter, which teacher, and whether the person typing has any standing to make that request — and then act on it.

    School Contact can already tell the school that message really came from that parent. That’s identity, solved. But nobody has answered the second question sitting right behind it: is the tool reading that message, and the twenty other tools plugged into the same system, actually built well enough to be trusted with it?

    That’s the gap this piece is about — and it’s the reason we’re proposing something we’ve deliberately chosen not to run ourselves.

    What School Contact does, and where it stops

    How California Associates connects vendors, government, and the Contact Initiative identity layer EdTech vendors and Government & funders both connect into California Associates, an independent nonprofit with three functions: vendor vetting, AI sandbox, and pilot programs. California Associates then approves vendors down into the existing verified identity layer. EdTech vendors Want to connect Government & funders California Associates Independent nonprofit (proposed) Vendor vetting Security audits AI sandbox Synthetic data Pilot programs Small, evaluated Approved vendors only Verified identity Contact Initiative layer

    School Contact gives a parent a verified way to know a message really came from a teacher. It gives a school a reliable way to confirm a caller’s claimed relationship to a student. It closes off the impersonation and phishing that currently thrives on nobody being able to check anyone’s claims.

    What it doesn’t do is vet the dozen-plus other tools a district plugs into that identity layer — the student information system, the learning platform, the classroom apps, the messaging tool, the scheduling assistant starting to lean on AI. School Contact can confirm who is asking. It has no mechanism — and shouldn’t be the one building one — for judging whether the tool asking is secure enough to be trusted with your child’s data in the first place.

    That gap is bigger than it sounds. A 2024 industry survey (Center for Internet Security / K12 SIX) found that the large majority of K–12 districts experienced some form of cybersecurity incident over the prior eighteen months, and vendor-side compromises — not the districts themselves — are consistently cited as a leading cause. Most districts now run dozens of third-party EdTech tools, typically vetted, if at all, by whoever happened to be doing procurement that year. Identity verification stops someone from pretending to be your child’s teacher. It does nothing about a vendor with weak security getting breached and taking your child’s data down with it.

    Why we don’t want to be the ones grading this homework

    There’s an obvious shortcut: have School Contact itself decide which vendors are trustworthy. We considered it and ruled it out on purpose.

    Any organization that both runs the identity layer and decides which commercial products get to plug into it has a conflict of interest baked into its business model. It has every incentive to wave through partners, go easy on vendors it already has relationships with, or quietly redefine “compliant” to fit whoever’s already integrated. Electrical products get certified by UL, not by the manufacturers whose products the certification governs. Payment processors answer to PCI-DSS standards set by an independent council, not by whichever bank benefits most from a lenient reading. Identity infrastructure for schools deserves the same separation — which is exactly why we’re proposing a second, independent nonprofit for this job instead of building it into School Contact.

    What California Associates is actually proposing

    California Associates would be a 501(c)(3) nonprofit sitting between schools, vendors, and government, with three specific jobs:

    Vendor vetting and compliance. An independent clearinghouse that audits EdTech tools against identity and security standards before they touch a district’s systems — instead of every district separately, unevenly, or never evaluating the same vendors on its own.

    A sandbox for AI, kept away from real student data. As AI tools take on requests like the Thursday-absence message above, something has to correctly resolve which daughter, which teacher, and whether the person asking has the standing to ask. The proposal calls for a bounded testing environment — separate domains, synthetic data only — where developers can work through exactly that problem without ever touching a real student’s real records.

    Coordinating pilots, transparently, before wider rollout. If any of this gets tested in real schools, it happens through funded, evaluated pilots — not a quiet expansion — with philanthropic, corporate, and federal research funding secured and disclosed up front.

    Where this stands today

    California Associates is a proposal, not an operating entity: no vendor has been vetted, no sandbox is live, no pilot is underway in any school. But a proposal that only exists as a document is easy to ignore, so we’ve already started building. Our beta test site is live now at california.associates — because we’d rather show up with something real to react to than ask people to take a governance model on faith. If you want to see where this is headed before it’s finished, that’s the place to look.

    The honest version of the hardest questions

    We’d rather answer these plainly and let you disagree with the answer than dodge them and ask for blind feedback.

    If you’re a parent or teacher: does an independent vetting body actually make you more confident in your school’s tools, or is it one more layer between a good idea and your classroom? Our answer: on its own, a vetting body is invisible to you day-to-day — you’ll only notice it in the incidents that don’t happen. The test isn’t whether you feel it; it’s whether the tools your kid’s school adopts next year have fewer of the vendor-side breaches that are already happening today. Tell us if you think that trade-off is wrong.

    If you’re a school or district administrator: does this respect the procurement control you already have, or does it ask you to give up more than it gives back? Our answer: it’s meant to be a resource you can point to, not a mandate that overrides your own review — a vetted-vendor list that saves your IT team from re-doing the same security diligence fifty other districts already did. If it starts to feel like a mandate in practice, that’s a design failure we want to hear about immediately.

    If you work in education technology or AI: is there a realistic, non-burdensome way to actually meet a standard like this, or does it look good on paper and collapse at the pace software ships? Our answer: we don’t know yet, and that’s precisely what the sandbox is for — a place to pressure-test the standard against real development cycles before it’s locked in as a requirement anyone has to live with. If the standard doesn’t survive contact with how you actually ship code, we need to know that before we finalize it, not after.

    Where to send feedback

    The full proposal — governance structure, the open legal questions around FERPA and COPPA, and the specific questions we’re putting to academia, government, and the technology industry — is at california.associates. It’s marked as an exploratory draft, not adopted policy, on purpose: the goal right now is to find out what’s wrong with it, not to defend it.

    School Contact makes sure the people talking to your school’s systems are who they say they are. California Associates is our answer to the harder question behind that one: making sure the systems themselves have earned that trust before they’re allowed to ask. We think both problems are real, we think they need independently accountable answers, and we think you should be able to watch us build the second one instead of just reading about it.

  • What If China Joins Us To Built Our Contact Initiative?

    How a National Education Numbering System Could Create a New Digital Trust Layer

    The future of educational identity may not require one global system — only a common language for trust.


    1. What If China Moved First?

    Somewhere in the world, a country will be the first to build a national identity and communication architecture purpose-built for an education system operating alongside machine intelligence. It does not have to be the United States.

    The Contact Initiative — a proposal detailed in the white paper “The Contact Initiative: A National Framework for Verified Identity and Communication in American Education” — was designed to solve an American problem: fragmented, unverifiable identity across thirteen thousand independent school districts and thousands of colleges and universities. The paper is explicit that it is a draft for research, stakeholder consultation, and pilot design, not enacted policy, and that it carries no endorsement from any American regulator or federal body.

    But the architecture underneath that American proposal — persistent identity, institution-attested roles, federated verification, and machine-intelligence readiness — is not inherently American. It is a general answer to a general problem. This piece is a thought experiment: what would it look like if the People’s Republic of China built its own version, adapted entirely to its own numbering systems, administrative structure, and governance model, rather than importing America’s?

    To be unambiguous from the outset: China has not adopted the Contact Initiative. No government has. Nothing in this article should be read as a claim about existing Chinese policy, an existing Chinese pilot program, or an official Chinese numbering scheme. Every numbering structure, every layer, and every scenario described below is a hypothetical proposal offered for discussion — a “what if,” not a “what is.”


    2. China Already Understands the Power of Numbering Systems

    One reason this thought experiment is worth taking seriously is that China’s telecommunications infrastructure already demonstrates deep institutional fluency with structured, hierarchical numbering.

    China’s Ministry of Industry and Information Technology (MIIT) is the primary national regulator responsible for telecommunications numbering resources, working alongside provincial-level counterparts. <cite index=”3-1″>China’s major telecom operators apply for telephone numbers from the MIIT and its local counterparts, and telecoms operators apply to the MIIT for inter-provincial and international telecoms resources, or to the MIIT’s provincial-level counterparts for intra-provincial resources</cite>. This two-tier structure — national coordination paired with provincial administration — already mirrors, in the telecommunications domain, exactly the kind of layered governance an education identity system would need.

    China’s existing telephone numbering plan itself is geographically structured: fixed-line numbers are tied to specific administrative regions and combine a short area-code prefix with a longer subscriber number, a design that lets a recipient infer general geographic context from a number’s structure alone, before any call is even answered. <cite index=”9-1″>The complete national format for fixed-line numbers consists of a trunk prefix followed by a two-to-four-digit area code and a seven-to-eight-digit subscriber number, with two-digit area codes reserved for major metropolitan centers</cite>. Mobile numbering, by contrast, is non-geographic and tied instead to specific mobile network operators rather than location.

    None of this means China’s telephone numbers should be repurposed for education. They should not be, and this article does not propose touching the existing numbering plan in any way. What it does suggest is that China’s institutions already have decades of operational experience running exactly the kind of tiered, jurisdictionally coordinated numbering architecture that an entirely separate Education Contact Numbering Plan would require — a head start in institutional capability, not a claim about current policy.


    3. The Contact Initiative’s Central Idea

    Strip away the specific American implementation, and the Contact Initiative rests on a small number of governing principles: identity before access, authorization before action, rank and role are attested rather than self-declared, local and institutional control, vendor neutrality, and human governance.

    From these principles the white paper builds a structure with four pillars — identity (persistent, recognizable identifiers for every participant), verification (institution-attested confirmation of current role and affiliation, never a self-declared claim), communication (trusted, phishing-resistant channels built from short aliases layered over administrative detail), and MI readiness (identity and authorization context reliable enough that machine-intelligence systems can act on it safely and auditably).

    The most important idea to carry into a Chinese context is this: a Contact identifier was never meant to be the identity itself. It is a routing and verification anchor — a way for a system to know where to look and what kind of identity it is dealing with, before the deeper verification layer determines who the person actually is and what they are currently authorized to do. That separation — between the public-facing handle and the administrative truth behind it — is the architectural idea worth exporting, regardless of what numbering convention a given country uses to implement it.


    4. Why Education Needs Its Own Identity Layer

    The case for a dedicated education identity layer does not depend on any particular country’s politics. It depends on a structural fact common to essentially every national education system: schools, colleges, and universities have each built their own communication systems independently, platform by platform, with no shared verification layer connecting them. A parent cannot always confirm that a message claiming to be from a teacher is genuine. A receiving school cannot instantly verify a transferring student’s enrollment history. A university cannot easily confirm a visiting scholar’s current standing. And a machine-intelligence assistant asked to carry out even a simple instruction has no authoritative way to resolve who, exactly, it is dealing with.

    China’s scale makes this problem larger, not smaller. A national system spanning hundreds of millions of students, guardians, teachers, and researchers, distributed across provinces, autonomous regions, and municipalities with different local administrative practices, faces the fragmentation problem at a scale most countries never will. That scale is precisely why a deliberately layered, federated identity architecture — rather than a single flat database — would matter so much in this context.


    5. A Hypothetical China Education Contact Numbering Plan

    Call this, for the sake of discussion, the China Education Contact Numbering Plan — Conceptual Model. It is entirely hypothetical. It proposes no changes to any existing telecommunications numbering resource, and it does not claim to be under consideration by any Chinese ministry or agency.

    The underlying logic follows a simple hierarchy:

    Geography → education population → institution → individual identity → verification state.

    Conceptually, a Contact identifier could be structured in five layers:

    • Layer 1 — Administrative region. A code identifying the broad jurisdiction in which the identity originates — a province, autonomous region, or municipality directly under central administration.
    • Layer 2 — Education population. A category distinguishing the type of participant: government or institutional identity, school, teacher, administrator, student, parent or guardian, college faculty, university faculty, researcher, support staff, or verified vendor/technology identity.
    • Layer 3 — Institution. A code identifying the specific participating school, college, or university.
    • Layer 4 — Individual. A persistent identifier for the specific person, stable across their transitions through the education system.
    • Layer 5 — Verification state. Rather than encoding sensitive personal information directly into the number itself, this layer would point toward a verification service capable of confirming current enrollment, current employment, current role, current institutional affiliation, credential status, and authorization status.

    This is deliberately abstract. No actual digits, prefixes, or area-code-style values are proposed here, and none should be inferred from this article. The point of the model is the layering logic — geography, population, institution, individual, verification — not any specific numeric scheme.


    6. Geographic Identity and China’s Administrative Structure

    China’s existing administrative hierarchy — provinces, autonomous regions, municipalities directly under the central government, and the cities, counties, districts, and townships beneath them — offers a natural (though again, entirely hypothetical) foundation for the geographic layer of an education Contact system.

    A conceptual regional layer might, for illustration only, distinguish education identities originating in Beijing from those in Shanghai, Guangdong, Jiangsu, Zhejiang, Sichuan, Hubei, Shaanxi, Fujian, Shandong, or any other province, autonomous region, or municipality. This is offered purely as an illustration of the kind of geographic differentiation the model could support — not as a proposed numbering table, and certainly not as an adaptation of any real telecommunications area code. Any actual codes used in a real implementation would need to be defined independently by whatever body eventually governed the system, and would have no necessary relationship to existing telephone area codes at all.

    The deeper reason this geographic layer matters is administrative, not merely technical. China’s telecommunications numbering already divides authority between the MIIT nationally and its counterparts at the provincial level. <cite index=”8-1″>MIIT and its provincial Communications Administrations jointly license and regulate telecommunications activity within their respective jurisdictions</cite>. An education Contact system could conceivably mirror that same division of labor — a national body setting technical standards and top-level coordination, with provincial or municipal education authorities administering the identities and verifications within their own jurisdictions. This would keep the system consistent with the Contact Initiative’s principle of local and institutional control, rather than concentrating every identity decision inside a single national office.


    7. School Contact China

    A hypothetical School Contact China layer would extend to primary schools, middle schools, high schools, and vocational secondary education, covering students, parents and guardians, teachers, principals, and administrative staff.

    The core function would be the same one the American white paper describes for K–12: distinguishing legitimate teachers, schools, administrators, and guardians from impersonators, through institution-attested roles rather than self-declared claims. A parent’s relationship to a specific student would be a verified, revocable record — not a claim made once and trusted indefinitely. A teacher’s current employment at a specific school would be attested by that school, and would lapse the moment the school’s own records changed.

    Because minors are the population involved, the guardianship layer would need to carry real legal weight — mirroring the American paper’s treatment of parental rights, but built around China’s own family and education law rather than transplanting FERPA-style concepts wholesale.


    8. College Contact China

    Rather than force the American categories of “community college” onto a Chinese context where they do not map cleanly, a hypothetical College Contact China layer should be built around China’s own educational taxonomy: vocational colleges, teaching-oriented institutions, technical and applied-skills education, and adult or continuing education.

    The identity and verification logic would be similar in structure to School Contact but adapted for a population that is largely composed of legal adults, meaning the rights-holder for most verification and communication purposes becomes the student directly, rather than a guardian. Institutional attestation of enrollment, program, and credential status would remain the anchor, allowing employers, other institutions, and verification services to confirm a person’s current standing without relying on self-reported claims.


    9. University Contact China

    The richest and most complex layer, by direct analogy to the American paper’s University Contact framework, is where the concurrent-affiliation model becomes essential.

    A hypothetical University Contact China would need to accommodate professors, associate professors, lecturers, researchers, doctoral students, graduate students, visiting scholars, joint appointments, laboratory affiliations, university administrators, and — increasingly common in a research environment of growing scale and cross-institutional collaboration — researchers affiliated with more than one institution simultaneously.

    The design principle here is exactly the one the white paper establishes: one persistent identity, multiple independently verified and independently revocable affiliations. A researcher holding a primary appointment at one university, a joint laboratory affiliation at a national research institute, and a visiting-scholar status at a third institution should not need three separate identities. They should hold one stable Contact identifier, behind which sits a set of affiliation records that can each be verified, updated, or revoked independently, by the institution that issued them, without disturbing the others.


    10. Persistent Student Identity: A Hypothetical Example

    Consider a purely fictional illustration. No real person, no real government identification number, and no real Contact identifier is used here — only an illustrative narrative.

    Imagine a student beginning secondary school somewhere in Guangdong province. At enrollment, they receive a persistent Contact identity anchor — a stable identifier that, in this hypothetical model, is not tied to any specific school, city, or grade level, but simply to them as a person moving through the education system.

    • The student later transfers schools within the same city. The identity anchor does not change; only the institutional affiliation record behind it updates, attested by the new school.
    • The family moves to another city, and the student enrolls in a new secondary school there. Again, the anchor persists; a new institution attests a new affiliation, while the previous school’s record is archived rather than deleted.
    • The student graduates. The K–12 affiliation record closes, but the underlying identity anchor is not discarded — it becomes the same anchor the student carries into higher education.
    • The student enters university, and a university affiliation record is attached to the same persistent anchor, verified by the admitting institution.
    • The student becomes a graduate researcher, adding a laboratory affiliation and, later, a joint appointment at a second research institute — multiple concurrent, independently verified affiliations layered onto one identity.
    • Years later, that same person becomes a professor. The affiliation record updates once more, this time reflecting verified academic rank rather than student status, but the identity anchor established at secondary-school enrollment remains, in this hypothetical, the same one used throughout.

    The point of the example is narrow but important: the identity anchor can remain persistent while the verified affiliation changes. That persistence — portability across transitions that would otherwise fragment a person’s educational identity into a dozen disconnected records — is the single most valuable property the Contact Initiative’s architecture offers, in any country that implements it.


    11. Parent and Guardian Contact

    A Chinese adaptation of the guardian-relationship model would need to solve a specific problem: how does a school confirm that a message, a pickup request, or an enrollment action actually comes from an authorized guardian, without exposing the student’s entire education record to anyone who merely claims that relationship?

    The Contact Initiative’s answer, adapted conceptually, would look like this:

    Student identity → verified guardian relationship → authorized communication

    rather than the fragile default most systems rely on today:

    Parent phone number or email → unverified claim of guardianship.

    A verified relationship record would let a school confirm, before treating any inbound message as trustworthy, that the sender currently holds an attested guardianship relationship to a specific student — useful for routine notifications, parent-teacher communication, and enrollment, but essential in exactly the moments when it matters most: emergency communications, school transfers, disaster displacement, and pickup authorization. This is conceptual in every particular; no such verified guardian-relationship system currently exists as described.


    12. Emergency Communication and Disaster Displacement

    The value of identity infrastructure becomes most visible when normal systems fail. Consider a hypothetical large-scale emergency — a flood, an earthquake, a typhoon — that forces a group of families to relocate temporarily and enroll their children in a receiving school in another city or province.

    Under a Contact-style architecture, a receiving school could, in principle, verify a displaced student’s identity directly against their persistent Contact anchor rather than waiting for paper records to be located and transferred. The receiving institution could confirm current enrollment status and grade level through a federated verification request to the student’s prior school. The guardian relationship could be confirmed against the relationship layer before the receiving school treats an accompanying adult’s claim of guardianship as trustworthy. Emergency officials could reach verified, authorized contacts for affected families directly, rather than relying on unverified phone numbers gathered in the chaos of an evacuation.

    This should not be overstated. The Contact Initiative would not, by itself, resolve a disaster, coordinate physical relief, or replace emergency-management systems. What it could plausibly do is accelerate the verification and communication steps that currently take days or weeks when records are paper-based or siloed inside a single district’s or province’s systems — letting displaced students be seated in a classroom, and displaced families reach the people who need to reach them, faster.


    13. Cybersecurity

    A Chinese Contact architecture could, in principle, reduce identity ambiguity in ways that make several categories of attack structurally harder: phishing that imitates school or university branding, impersonation of teachers or administrators, fraudulent messages claiming to be from financial-aid or admissions offices, malicious vendors posing as legitimate technology partners, and social engineering that exploits the difficulty of verifying a claimed institutional role.

    The underlying concept, borrowed directly from the white paper, is straightforward: make verification part of the infrastructure instead of asking every individual to become a cybersecurity expert. Rather than training hundreds of millions of students, parents, and educators to individually recognize increasingly sophisticated fakes, a verified-identity layer shifts part of that burden into the system itself.

    This should be stated carefully. Such a system could reduce the effectiveness of certain impersonation techniques. It could make spoofed institutional communication more difficult to construct convincingly. It could provide an additional verification layer on top of existing cybersecurity practices, and it could improve institutional trust between schools, families, and universities that currently have no reliable way to check one another’s claims. It would not eliminate cybercrime, phishing, or fraud — no architecture accomplishes that, and any claim to the contrary should be treated with skepticism.


    14. Machine Intelligence and the Identity Problem

    This is where the stakes of the entire proposal come into focus. China’s machine-intelligence ecosystem is developing rapidly, and that development creates an identity problem that will only intensify as MI systems take on more responsibility inside education.

    Imagine a student telling an MI assistant: “Send my professor my research draft.” Without a verified identity infrastructure behind that request, the system has to infer an enormous amount: which university, which professor, which course or laboratory, whether the student is actually affiliated with that professor, whether the professor’s current role is genuine and current, whether the student is authorized to send the document at all, and whether the document is permitted to leave the institution in the first place.

    With a Contact-style architecture behind it, the same MI system could instead resolve the request through a clear chain: identity → affiliation → role → authorization → action. It would not need to guess which “professor” the student meant, because the system could confirm the student’s current, verified affiliation with a specific laboratory or course, cross-reference the professor’s currently attested rank and role, and confirm that both the relationship and the requested action fall within an authorized boundary — before taking any action at all, and with the action logged for later audit.

    The central argument here bears repeating because it is the most important idea in this entire discussion: the future of machine intelligence depends not only on the intelligence of the model, but on the trustworthiness of the identity and authorization infrastructure beneath it. A more capable MI system operating on ambiguous identity is not a safer system — it is a more dangerous one, because its errors and its authority both scale with its capability. Better identity infrastructure is not a constraint on MI progress. It is a precondition for deploying MI safely at scale.


    15. Centralization Versus Federation

    Any serious Chinese adaptation of this framework would need to make a foundational architectural choice between two models, each with real trade-offs.

    A centralized model would place core identity and verification infrastructure under a single national authority — plausibly the Ministry of Education working alongside the MIIT on the technical numbering and communication layer. The advantage would be consistency: uniform standards, a single point of technical authority, and simplified national-scale coordination. The risk is equally clear: a single point of failure, a concentration of sensitive data that becomes an attractive target for both cyberattack and misuse, and reduced flexibility for local institutions to adapt the system to their own conditions.

    A federated model would instead have schools, universities, and provincial or municipal education authorities maintain their own authoritative records, interoperating through shared technical standards rather than a shared database. This mirrors the two-tier structure China’s telecommunications numbering already uses, where <cite index=”3-1″>the MIIT handles inter-provincial and international resources while its provincial-level counterparts manage intra-provincial allocation</cite>. The advantage is resilience and local control — no single database to compromise, and institutions retaining authority over their own records. The disadvantage is complexity: more coordination is required to make federated verification actually work smoothly across jurisdictional boundaries.

    Neither model is automatically superior, and an honest treatment of this question should resist the temptation to declare a winner. The Contact Initiative’s own stated principle — local and institutional control — leans toward federation. But real national systems, in any country, often end up as hybrids: centralized technical standards and national-level coordination, paired with federated data custody and local administrative authority. That hybrid path is plausibly the most realistic outcome for a Chinese adaptation as well.


    16. Privacy and Governance

    None of the preceding sections matter if the governance rules surrounding the system are weak. A Chinese implementation of this framework would need serious, sustained attention to personal data protection, student privacy, parental rights, and the boundaries of institutional, governmental, and commercial access to identity and verification records — alongside data minimization, auditability, identity portability, cybersecurity, data retention limits, and the handling of any cross-border data flows involving international students, joint programs, or visiting scholars.

    These are not trivial questions, and building the numbering architecture does not automatically make any of them safe. A national identity system, built without careful governance, could just as easily become a tool for excessive surveillance, inappropriate data aggregation, or unaccountable access as it could become a tool for trustworthy verification. The technology is governance-neutral; the rules that surround it are not.

    The strongest single principle to carry into this design is this: a trusted identity system is only as trustworthy as the rules governing who can query it, what they can learn, and what they are permitted to do with the answer. A verification request should be able to answer a narrow question — is this person currently a guardian of this student? Is this person’s professorship currently active? — without exposing everything else in that person’s record. Minimal necessary disclosure, not maximal data collection, should be the design default, however the eventual governance and legal framework is structured.


    17. What China Could Gain by Moving First

    Setting governance questions aside for a moment, there are real — if not guaranteed — strategic advantages to being an early demonstrator of this kind of architecture. Among them: leadership in education cybersecurity practice; recognized expertise in large-scale digital identity infrastructure; an early, credible model of machine-intelligence governance built around verified authorization rather than inference; interoperability advantages for a large and growing population of students studying, researching, and collaborating internationally; stronger emergency-communication capacity during large-scale disaster displacement; improved student and researcher mobility across institutions and provinces; and meaningful early influence over whatever international technical standards eventually emerge for cross-border identity verification in education.

    These are potential advantages, not promised outcomes, and they say nothing about which political or economic system is better suited to realize them. A different country, with different institutions and a different governance model, could pursue the same architecture and realize a different mix of the same benefits. The point is not that China would “win” something by building this. It is that the country that does the hard, patient work of building trustworthy identity infrastructure — whichever country that turns out to be — will likely find itself with disproportionate influence over how the rest of the world eventually interoperates with it.


    18. How China Could Pilot the Concept

    A hypothetical, staged path — offered purely as a thought experiment, not a claim about any actual plan:

    Phase 1 — Research. Study China’s existing education-identity practices and telecommunications numbering infrastructure to understand what already exists and what a new layer would need to avoid duplicating.

    Phase 2 — Standards. Define identity, role, affiliation, authorization, and verification standards specific to Chinese educational institutions and legal requirements.

    Phase 3 — Pilot. Select a limited group of schools, vocational colleges, and universities willing to test the concept under real conditions.

    Phase 4 — Contact identifiers. Issue pilot-only Contact identifiers for the test population, entirely separate from any existing telecommunications numbering resource, with no disruption to the national telephone numbering plan.

    Phase 5 — Verification directories. Build the authoritative verification services that let institutions confirm one another’s attestations.

    Phase 6 — Trusted communication. Connect verified Contact identities to authenticated communication channels.

    Phase 7 — Emergency systems. Test the architecture against simulated emergency and displacement scenarios before relying on it during a real one.

    Phase 8 — MI sandbox. Build a bounded, separate environment where machine-intelligence identity resolution can be tested safely before being connected to live production identities.

    Phase 9 — Expansion. Grow participation gradually, preserving local and institutional control at each stage rather than forcing rapid, top-down adoption.


    19. International Interoperability

    The most ambitious possibility this thought experiment raises is not that China would adopt America’s system, or that any one country’s numbering scheme would become a global standard. It is that many countries could build entirely different systems — an American Contact identity built on the white paper’s proposed national numbering plan, a hypothetical Chinese Contact identity built on its own administrative geography, a European education identity shaped by its own privacy regime, an African national system built around its own institutions, an Indian system built around its own scale and structure — and still find a way to trust one another’s answers to a common set of questions.

    Those questions would not require a shared database. They would require shared methods for answering: Is this identity authentic? Which institution attests it? What role does it currently hold? Is the credential valid? Is the affiliation current? What authorization exists? And can another institution, in another country, verify that assertion without either side surrendering its underlying records to the other?

    That is the concept worth naming explicitly: interoperable trust without universal centralization. No single global identity database. No single national numbering scheme extended worldwide. Instead, a shared technical language that lets sovereign, differently designed national systems ask one another trustworthy questions and receive trustworthy answers.


    20. Conclusion: The Number Is Only the Beginning

    The Contact Initiative began with an American problem. But the underlying problem it describes is universal: every modern education system must eventually answer who a person is, what institution recognizes them, what role they hold, whether that role is current, what they are authorized to do, who is authorized to communicate with them, whether another institution can verify the answer, and whether a machine-intelligence system can safely act on that information.

    China does not need America’s numbering architecture to answer these questions. It could build its own — using its own geographic and administrative structure, its own institutions, its own governance traditions, and its own legal framework for privacy and data protection. Nothing about the underlying principle requires copying the specific implementation of any single country.

    But the principle itself would remain constant wherever it was built: identity should be infrastructure. Not an email address. Not a database field bolted onto a learning-management platform as an afterthought. A foundational layer, engineered deliberately, that connects verified identities to verified institutions, verified roles, verified authority, and accountable machine action.

    The Contact Initiative is one proposal for building that future, written for one country’s education system. China could choose to build an entirely different version, suited to its own conditions. And if it did, the value of the experiment would not be confined to China alone — it could help the rest of the world see, concretely, what becomes possible when a nation treats educational identity not as an incidental technical detail, but as national digital infrastructure for the age of machine intelligence.

  • If America Waits, the World Doesn’t Have To

    How the Contact Initiative Could Become a Global Blueprint for Trusted Education


    There is a question that every education system on Earth will eventually have to answer, whether its leaders realize it yet or not: when a message arrives claiming to be from a teacher, a professor, a parent, or a school office, how does anyone — human or machine — actually know it’s true?

    Today, in almost every country, the honest answer is: they don’t. Not with certainty. Identity in education has been assembled piecemeal, one learning-management platform and one email domain at a time, by thousands of independent institutions that were never asked to talk to one another. The result is a kind of structural fog — a condition in which impersonation is easy, verification is hard, and the machine-intelligence systems now arriving in classrooms and administrative offices have no reliable way to know who anyone actually is.

    The Contact Initiative, a proposal developed in the United States and detailed in the white paper “The Contact Initiative: A National Framework for Verified Identity and Communication in American Education,” was written to address that fog inside one country’s education system. It is, by its own description, a starting framework for research, stakeholder consultation, and pilot design — not enacted policy, and not a system that any government body has adopted. It does not claim endorsement from the FCC, from NANPA, from any accreditation body, or from the federal government.

    But the problem the Contact Initiative names is not an American problem. It is a structural condition of modern education itself, and it will confront every country that tries to bring verified identity, trustworthy communication, and safe machine intelligence into its schools, colleges, and universities.

    This is the case for why the Contact Initiative’s architecture — not necessarily its numbering plan, its domain names, or its specifically American legal scaffolding, but its underlying logic — deserves serious attention well beyond the United States. If the United States adopts it first, that would be valuable, and it would give the rest of the world a working example to study. But if the United States moves slowly, hesitates, or declines to act, the idea should not be forced to wait for one government’s timeline. Another country can build its own version. Several can build their own versions, in parallel, learning from one another as they go.


    1. The Problem Is Bigger Than America

    The white paper documents, in stark terms, what unmanaged identity fragmentation costs an education system that has none of the infrastructure this framework proposes. Citing figures for K–12 alone, it notes that 82% of K–12 schools reported a cybersecurity incident between July 2023 and December 2024, and that 55% of publicly disclosed K–12 data breaches since 2016 trace back to compromised vendors. It observes that the average American school district now works with nearly three thousand distinct education-technology tools each year, most unvetted at the federal level, and that when ransomware succeeds, the average recovery cost and timeline are severe.

    These numbers describe the American system specifically. But nothing about the underlying cause is uniquely American. Every country that operates schools, colleges, and universities faces some version of the same structural gap: a proliferation of digital tools and communication channels, layered on top of one another over decades, with no shared identity fabric connecting them. A parent in Nairobi has the same difficulty confirming that a message is really from their child’s teacher as a parent in Ohio. A university in Manila faces the same challenge verifying a visiting lecturer’s current standing as a university in Massachusetts. A machine-intelligence assistant asked to “email my professor” is exactly as confused in Seoul as it is in San Diego, because the confusion is not a failure of the assistant — it is a failure of the identity infrastructure beneath it.

    Wherever an education system has grown institution by institution, platform by platform, without a common verification layer, the same vulnerabilities emerge: phishing that is difficult to distinguish from legitimate correspondence, guardians and administrators who cannot easily check a claimed relationship or role, students whose records do not travel cleanly when they transfer or graduate, and an emerging generation of MI tools that must guess at identity rather than verify it. This is the condition the Contact Initiative was built to address, and it is a global condition.


    2. What the Contact Initiative Actually Proposes

    At its core, the Contact Initiative is not a single piece of software or a single domain scheme. It is an architecture built on a small number of governing principles, stated plainly in the white paper: identity before access, authorization before action, rights follow the population, rank and role are attested rather than self-declared, local and institutional control, vendor neutrality, and human governance.

    From those principles, the framework builds three interlocking components:

    • Identity — persistent, recognizable identities for every student, parent, faculty member, and staff member, so that a person’s identity does not have to be reconstructed from scratch every time they interact with a new system or institution.
    • Verification — institution-attested confirmation of a person’s current role, rank, and affiliation, replacing the self-declared claims (“I’m his uncle,” “I’m the substitute teacher”) that currently underlie so much of education’s daily communication.
    • Communication — trusted, phishing-resistant channels, built around short human-facing aliases layered over administrative addresses that carry the compliance-grade detail underneath.
    • MI readiness — reliable identity and authorization context, so that machine-intelligence systems can act on a person’s behalf only inside a verified, auditable boundary, rather than guessing.

    Crucially, the framework insists on a distinction that will matter enormously to any country considering it: verified rank and role, not self-declared claims. A person does not get to assert that they are a teacher, a guardian, or a department chair. An institution attests to it, that attestation is checked before access or communication proceeds, and the person’s authority is only as current as the institution’s own records say it is.


    3. Why Identity Must Become Infrastructure

    The white paper’s most important conceptual move is treating identity not as an application feature but as infrastructure — something that sits underneath every platform an institution uses, the way electricity or water sits underneath a building, rather than something bundled inside any one vendor’s product.

    This distinction matters because it explains why the fragmentation problem cannot be solved by any single school district, university, or software company acting alone. A learning-management system can verify identity within its own walls. It cannot verify identity across a school transfer, a district boundary, or an international exchange. Only a shared, interoperable identity layer — one that institutions can plug into rather than each attempting to build in isolation — can do that.

    Treating identity as infrastructure also reframes who is responsible for it. It is not a burden to be placed entirely on individual teachers, parents, or students to “be more careful” about phishing and impersonation. It becomes a structural property of the system itself, engineered rather than merely taught.


    4. The Three-Layer International Model

    The Contact Initiative divides its American implementation into three companion frameworks, each adapted to a distinct population:

    1. School Contact — built for K–12 education, anchored by a national numbering plan, a guardian-identity layer that lets parents authenticate using aliases keyed to a verified relationship, and protections designed around the reality that minors’ rights are held by their guardians.
    2. College Contact — adapted for community colleges and teaching-focused higher education institutions, where the population is largely adult and rights transfer to the student directly.
    3. University Contact — built for research and doctoral universities, where a single person may hold multiple, independently verified, and independently revocable affiliations at once — a joint appointment here, an adjunct role there, an emeritus title at a third institution — and where academic rank itself (Professor, Associate Professor, Lecturer, Adjunct, Visiting Professor) carries different authority that a flat, undifferentiated identity system cannot capture.

    This three-tier logic is not merely an American organizational convenience — it reflects a distinction most national education systems already recognize in some form: a K–12 population governed by guardianship and legal minority, a vocational or teaching-focused post-secondary tier, and a research-university tier defined by complex, overlapping institutional affiliations.

    Hypothetically, a country adapting this model would not need to reproduce the American tiers exactly. A nation with a strong vocational-education track distinct from academic upper-secondary school might need a fourth tier. A country where doctoral research is concentrated in a small number of national institutes rather than dispersed among hundreds of independent universities might collapse “College” and “University” into one verification layer with internal sub-tiers. The number of layers is less important than the underlying insight: different populations carry different rights, different guardianship structures, and different verification needs, and a single undifferentiated identity system will fail all of them at once.


    5. How Another Country Could Adopt the Framework

    No country needs to attempt a national transformation on day one. The white paper itself frames the Contact Initiative as a draft for research, stakeholder consultation, and pilot design — and that same caution should govern any international adaptation. A workable path might unfold in stages:

    Stage 1 — National consultation. Bring education ministries, schools, universities, cybersecurity authorities, privacy regulators, educators, parents, students, technology vendors, and civil-society groups into the same conversation before any technical design begins.

    Stage 2 — Identity mapping. Document how student, teacher, guardian, faculty, staff, institutional, and credential identities currently exist — and where they currently fail to connect.

    Stage 3 — Pilot selection. Choose a small, representative group of schools, colleges, and universities willing to test the framework under real conditions rather than in a lab.

    Stage 4 — Verification layer. Build the institution-attested identity and role-verification mechanism first, before any communication feature depends on it.

    Stage 5 — Trusted communication. Introduce verified communication aliases and lookup directories, layered on top of the verification work already in place.

    Stage 6 — Federated interoperability. Allow participating institutions to verify one another’s identities across institutional boundaries — a school confirming a transferring student’s guardian, a university confirming a visiting lecturer’s standing at another institution.

    Stage 7 — Emergency applications. Extend the system to the highest-stakes use cases: disaster displacement, emergency notification, and rapid school transfers, where verified identity has the most immediate, tangible payoff.

    Stage 8 — Machine-intelligence readiness. Only once identity and authorization are demonstrably trustworthy should machine-intelligence systems be permitted to act against those identities — never before.

    Stage 9 — National scaling. Expand deliberately, while preserving the local and institutional control that made the pilot trustworthy in the first place.

    This sequence matters as much as any individual stage. A country that tries to deploy MI-driven automation (Stage 8) before it has built a functioning verification layer (Stage 4) will simply automate the same guesswork and impersonation risk that already exists — at greater speed and scale.


    6. Hypothetical Examples of National Adaptation

    None of the following examples describe an existing program in any country. They are offered strictly as illustrations of how the same architecture could bend to different national conditions.

    • A highly centralized education system might operate the verification layer through its national education ministry directly, issuing institution attestations from a single authority rather than distributing that power across thousands of independent districts.
    • A federated country, with education governed at the state, provincial, or regional level, might distribute verification authority accordingly — mirroring the Contact Initiative’s own preference for local and institutional control rather than a single national chokepoint.
    • A country with a mature government digital-identity infrastructure might connect educational identities to that existing system as an additional verified attribute, rather than building a separate identity stack from nothing.
    • A country with strong privacy protections and a strong cultural expectation of data minimization might design its version of the framework around selective disclosure — verifying only the specific fact a request requires (“is this person currently a guardian of this student?”) without exposing any other information.
    • A country with significant experience of natural-disaster displacement might prioritize the emergency-transfer and guardian-verification components first, ahead of routine daily communication features, because that is where the most acute, life-affecting failures currently occur.
    • A country with a large international student population might emphasize portable academic identity and concurrent institutional affiliation above all else, since its highest-friction problem is not domestic fragmentation but cross-border recognition.

    The point of these examples is not that any one of them is correct. It is that the architecture is genuinely modular: identity, verification, communication, and MI-readiness can each be implemented differently depending on a country’s existing infrastructure, legal tradition, and administrative culture, without abandoning the underlying design.


    7. Cybersecurity and Trusted Communication

    The white paper is explicit that the Contact Initiative addresses cybersecurity structurally, not merely through user education. It identifies three mechanisms in particular: verified, role-based identity so that every user holds a unique, authenticated identity; persistent, institution-level logging that creates a traceable communication record; and never exposing the underlying administrative address, so the alias system shrinks the available target for spear-phishing.

    None of this should be overstated. Structural verification could reduce the effectiveness of impersonation attacks and could make certain categories of phishing meaningfully harder to execute at scale. It could provide an additional layer of defense on top of existing cybersecurity training, not a replacement for it. It would not eliminate phishing, ransomware, or fraud outright — no architecture does. What it could do is shift the burden of defense away from asking every teacher, parent, and student to individually recognize a well-crafted fake, and toward a system where fakes are structurally harder to construct in the first place.

    For any country evaluating this approach, that shift is the real argument: cybersecurity built into the plumbing of an identity system, rather than cybersecurity as an unending training exercise asked of millions of individual users who will, inevitably, sometimes get it wrong.


    8. Privacy, Sovereignty, and the Danger of Centralization

    This is the point at which any serious international discussion of the Contact Initiative must slow down, because the objections are real and deserve to be taken seriously rather than waved away.

    An international identity framework for education could, if designed carelessly, become exactly what its critics would fear: a centralized surveillance apparatus, a single point of failure, a new avenue for commercial exploitation of student data, or a mechanism that quietly expands government tracking of children and young adults under the banner of “safety” and “efficiency.” These are not hypothetical risks invented for the sake of balance — they are the predictable failure mode of any large identity system that concentrates too much data in too few hands.

    The Contact Initiative’s own core principles are, not coincidentally, a partial defense against exactly this risk. Local and institutional control means authority does not have to sit with one central body. Vendor neutrality means no single commercial platform becomes an unavoidable chokepoint through which all student data must flow. Human governance means machine-intelligence systems operate under human-set boundaries rather than autonomous authority. Federated authorization means institutions verify one another’s attestations without needing to pool their underlying records into a shared database.

    That last point deserves to be one of the strongest arguments in this entire discussion: interoperability does not require centralization. A federated model allows a school in one country, or one district, to confirm a fact asserted by a school in another — “this student is currently enrolled,” “this person is a currently attested guardian” — without either institution surrendering its underlying records to a shared global repository. The verification is federated; the data stays local. An international Contact Initiative, done correctly, would not require placing the world’s student and teacher records into one database anywhere. It would require agreement on how systems ask one another trustworthy questions and receive trustworthy answers.

    Any country pursuing this framework should treat privacy and sovereignty not as an afterthought bolted onto the architecture, but as a design constraint from the very first stage of consultation.


    9. The Machine-Intelligence Imperative

    The white paper offers a deceptively simple illustration: a student asks an MI assistant to “email my professor about the extension.” Without reliable identity infrastructure, the system has to guess — which course, which professor, which current section, and whether the student asking is actually enrolled in it. The Contact Initiative’s proposal is that such requests should be resolved against verified identity, role, and current-affiliation records, rather than inferred from probability and context.

    This example scales into something much larger than one email. As machine-intelligence systems take on more administrative, educational, and communication tasks, the cost of ambiguous identity rises with their capability. A system that occasionally guesses wrong about which “professor” a student means is an inconvenience. A system with broader authority — one capable of accessing records, issuing communications, or coordinating an emergency response — operating on an ambiguous or spoofable notion of identity is a serious risk.

    The core argument, stated plainly: the more capable machine-intelligence systems become, the more dangerous ambiguous identity and authorization become. A more capable model does not need better guessing. It needs better grounding — a way to resolve exactly who someone is, what role they hold, who attested to that role, and what they are currently authorized to do, before it acts.

    This reframes the entire conversation about “AI safety in education.” The long-term issue is not simply building smarter AI systems. It is building better identity infrastructure beneath AI — infrastructure so that intelligence, however capable it becomes, always acts against a verified and auditable foundation rather than an inferred one.


    10. The Country That Moves First

    If the United States adopts something like the Contact Initiative, it would have real advantages: a large, well-resourced technology sector, a large education market to pilot within, and the ability to set an early example other nations could study. But adoption is not guaranteed, and even where the appetite exists, large decentralized systems move slowly by nature — the white paper itself describes roughly thirteen thousand independent K–12 school districts in the United States alone, each with its own procurement, governance, and technology decisions.

    If the United States does not move first, or moves slowly, another country could. And there would be real, if not guaranteed, advantages to being that country: an early claim to cybersecurity leadership in education technology; a demonstrated model of digital-identity infrastructure that other governments could study and adapt; influence over whatever international interoperability standards eventually emerge; safer early deployment of educational MI systems; stronger emergency-communication capacity during disasters or displacement events; improved student mobility across institutions; and potential economic opportunity for the domestic technology companies that help build the pilot.

    These should be understood as potential advantages, not promised outcomes. Early adoption of any complex infrastructure project carries real costs and real risk of missteps. But the upside case is serious enough that no country with a functioning education ministry, a cybersecurity authority, and the political will to run a careful pilot should assume this opportunity belongs only to the United States, or that it must wait for an American decision before acting.


    11. Toward International Interoperability

    None of this requires inventing a single global Contact Initiative organization, and no such body currently exists. What it does suggest is the possibility of a future, more modest form of coordination: countries agreeing on common technical principles for how systems verify one another, while each retains full sovereignty over the things that matter most — identity issuance, education records, privacy law, institutional accreditation, credentialing standards, access policy, and the pace and shape of national implementation.

    This is a familiar pattern in other domains. Countries do not need a single global banking database to make international wire transfers trustworthy; they need agreed technical standards for how banks verify and authenticate one another’s claims. The equivalent for education identity would be an interoperability standard — a shared answer to the question of how one country’s verified institutional attestation can be recognized as trustworthy by an institution in another country, without either country handing its underlying student and staff records to anyone else.

    Reaching that kind of standard would take years of careful, deliberately unglamorous technical and diplomatic work. But the destination is worth naming clearly, because it reframes what “international adoption” actually means. It does not mean one country’s system becoming the world’s system. It means multiple countries building their own sovereign implementations of a shared architecture, and eventually finding the technical common ground that lets those implementations talk to one another when it matters — a study-abroad student’s credentials recognized abroad, a displaced family’s enrollment record verified across a border, a visiting researcher’s rank confirmed at a foreign university.


    12. A Call to Policymakers and Education Leaders

    For any education minister, university leader, cybersecurity official, or technology policymaker reading this outside the United States, the invitation is not to wait and watch. It is to ask, inside your own country’s institutions and legal framework, the same handful of foundational questions the Contact Initiative asks:

    Who are you? What role do you hold? Who has verified that role? What are you authorized to do? Who is authorized to contact you? Can another institution verify your identity? Can a machine-intelligence system safely act on your behalf? Can that action be audited? And can all of this happen without creating an unnecessary centralized surveillance system?

    Those nine questions are the philosophical backbone of this entire framework. A country does not need America’s ten-digit numbering plan. It does not need America’s domain-naming conventions. It does not need to reproduce the specific institutional structure of American school districts and universities. It needs to build its own honest answers to those nine questions, using its own national identity infrastructure, its own privacy law, and its own educational governance — and then, eventually, find the technical common ground that lets its answers be recognized by other countries doing the same work.

    A serious pilot does not require new legislation on day one. It requires a willing ministry or region, a handful of willing institutions, and a commitment to run the consultation and identity-mapping stages honestly before building anything. That is a realistic, near-term starting point for almost any country with functioning education and technology institutions.


    13. Conclusion — The World Should Not Have to Wait

    The Contact Initiative began as an American proposal because the white paper it comes from was written to address fragmentation inside American education — its numbering plan modeled conceptually on the North American Numbering Plan, its legal grounding built around FERPA and COPPA, its scenarios drawn from American school districts and universities. None of that should be minimized or obscured.

    But the problem underneath all of it is not American. Every country eventually faces the question of how a digital system knows who a person is, what role that person holds, what authority they currently possess, and whether a machine is permitted to act on their behalf. That is the universal problem. The Contact Initiative is one proposed architecture for answering it — not the only possible answer, and not a finished one, but a serious and detailed attempt to work through what verified identity, trusted communication, and safe machine intelligence could actually look like inside an education system.

    If the United States adopts the Contact Initiative, or something like it, that would be a genuinely valuable outcome, and other countries would have a working example to study, critique, and adapt. If the United States delays, or chooses a different path, or simply moves at the pace that a system of thirteen thousand independent school districts naturally moves, the idea should not be held hostage to that timeline. Another country can run the consultation. Another country can map its identities, choose its pilot schools, and begin building its own verification layer. Several countries can do this independently, learning from each other’s early mistakes, and converge later on the interoperability standards that let their systems recognize one another.

    The goal was never to build one world’s database of every student and teacher on Earth. The goal is to build a world in which institutions — wherever they are, under whatever laws they operate — can trust one another’s assertions about identity, role, affiliation, and authorization. The Contact Initiative begins with a simple proposition: identity should be infrastructure.

    If one country hesitates, another country can lead. The world does not have to wait for permission to start asking the right questions — it only has to start asking them.

  • Map

    Contact Initiative Domain Map — Complete Overview

    Complete Domain Directory for K–12 Schools, Colleges, and Universities

    Production, in use today
    MI beta, for testing only
    K–12 Schools

    location_citySchools

    elementary.school
    elementaryschools.email

    schoolStudents

    highschool.email highschools.email
    middleschool.email middleschools.email

    cast_for_educationTeachers

    teacher.contact technologies.contact
    teachers.email technology.email
    schools.email

    badgePrincipals

    principal.email principals.email

    family_restroomParents / Guardians

    parent.email parents.email

    account_balanceAcademies (Charter / Private)

    academy.email academies.email

    verified_userK–12 Verification

    school.contact technologies.contact
    Colleges (Teaching / Community)

    schoolStudents

    college.email colleges.email

    personFaculty

    faculty.college professors.college
    professor.college professors.colleges

    co_presentLecturers

    lecturer.college lecturers.college

    verified_userCollege Verification

    college.contact technologies.contact
    Universities (Research / Doctoral)

    schoolStudents

    university.email universities.email

    personFaculty (Ranked / Tenure-Track)

    professor.university professors.university

    co_presentLecturers (Non-Tenure Track)

    lecturer.university lecturers.university

    verified_userUniversity Verification

    university.contact technologies.contact
    Department of Technology

    account_balanceDepartment / Administration

    department.technology
    technology.email
    technology.contact

    groupsTechnology Personnel

    technology.email technologies.email

    verified_userVerification Services

    technology.contact technologies.contact

    computerMI Sandbox (System-Wide)

    For testing and development only

    principals.email teachers.email parents.email professors.colleges professors.university lecturers.college lecturers.university technologies.email technologies.contact universities.email colleges.email middleschools.email highschools.email elementaryschools.email academies.email
    Cross-Category Services

    shield_personGlobal Verification Endpoints

    school.contact
    college.contact
    university.contact
    teacher.contact

    mailCommunication Aliases (Global Patterns)

    parent.email
    students.email
    teacher.email
    professor.email
    principal.email
    lecturer.email
    faculty.email

    publicWeb / Infrastructure Roots

    elementary.school
    academy.email
    department.technology

    Domain Glossary

    What each domain does, grouped to match the map above.

    K–12 Schools

    elementary.school

    Standardized web-hosting root for elementary school sites and content management.

    elementaryschools.email

    MI sandbox mirror of the elementary school domain pattern, for testing only.

    highschool.email

    Verified alias domain for enrolled high school students.

    highschools.email

    MI sandbox mirror of the high school student alias pattern.

    middleschool.email

    Verified alias domain for enrolled middle school students.

    middleschools.email

    MI sandbox mirror of the middle school student alias pattern.

    teacher.contact

    Query-response endpoint confirming a teacher’s current, attested role.

    technologies.contact

    MI sandbox verification endpoint for testing automated vendor and technology lookups.

    teachers.email

    Verified communication alias for classroom teachers.

    technology.email

    Verified alias for a school or district’s operational technology staff.

    schools.email

    District-level alias for operational and administrative staff coordinating across school sites.

    principal.email

    Verified communication alias for a school’s principal.

    principals.email

    MI sandbox mirror of the principal alias pattern.

    parent.email

    Retired-never-recycled guardian alias used for verified guardian-school communication.

    parents.email

    MI sandbox mirror of the guardian alias pattern.

    academy.email

    Verified alias domain for charter and private academy communications.

    academies.email

    MI sandbox mirror of the academy alias pattern.

    school.contact

    Query-response endpoint confirming a school’s identity and current status — not a browsable directory.

    Colleges (Teaching / Community)

    college.email

    Verified alias domain for enrolled college students.

    colleges.email

    MI sandbox mirror of the college student alias pattern.

    faculty.college

    Verified alias for a college’s general teaching faculty.

    professors.college

    MI sandbox mirror of the college faculty alias pattern.

    professor.college

    Verified alias for an individually attested college professor.

    professors.colleges

    MI sandbox domain for testing cross-institution professor lookups.

    lecturer.college

    Verified alias for a non-tenure-track college lecturer.

    lecturers.college

    MI sandbox mirror of the college lecturer alias pattern.

    college.contact

    Query-response endpoint confirming a college’s identity and current status.

    Universities (Research / Doctoral)

    university.email

    Verified alias domain for enrolled university students.

    universities.email

    MI sandbox mirror of the university student alias pattern.

    professor.university

    Verified alias for ranked, tenure-track university faculty.

    professors.university

    MI sandbox mirror of the university professor alias pattern.

    lecturer.university

    Verified alias for a non-tenure-track university lecturer.

    lecturers.university

    MI sandbox mirror of the university lecturer alias pattern.

    university.contact

    Query-response endpoint confirming a university’s identity and current status.

    Department of Technology

    department.technology

    Root administrative domain for the Department of Technology.

    technology.contact

    Query-response endpoint confirming the Department of Technology’s identity and its personnel.

    technologies.email

    MI sandbox mirror of the technology-personnel alias pattern.

    Cross-Category Services

    students.email

    Global verified alias pattern for students, used across all institution types.

    teacher.email

    Global communication alias pattern for teachers across all institution types.

    professor.email

    Global communication alias pattern for professors across all institution types.

    lecturer.email

    Global communication alias pattern for lecturers across all institution types.

    faculty.email

    Global communication alias pattern for general faculty across all institution types.

    history
    Proposed Special Area Code Concept A three-digit prefix — 111 for institutions, 222 for teachers and principals, 333 for operational staff, and the 444/555/777/999 block for students — carried role and population directly in the address itself, removing the need to cross-reference a separate directory just to know whether a sender was a district office, a credentialed educator, or an enrolled student. The reserved 199–899 sandbox block served the same purpose for machine intelligence testing: developers could build and test MI tools against realistic-looking identifiers without any risk of touching live student or staff communication.

    K–12 National Numbering Plan & Parent Recycling Protocol

    Legacy Five-Tier Area Code Structure (Pre-V5 Draft)

    Production tier
    Reserved — MI sandbox

    account_balanceInstitutions & Agencies

    111

    Assigned to the institution itself (district, state, or federal agency), not an individual. Local districts use their 7-digit NCES Federal District ID; agencies use a 2-digit Federal State ID. This tier explicitly includes the Department of Technology, utilizing the 111 prefix.

    Associated domain:department.technology

    cast_for_educationClassroom Teachers & Principals

    222

    Classroom teachers and principals, split across @teachers.email and @principals.email, built from a state ID plus the educator’s state-issued credential number.

    Associated domains: teachers.email principals.email

    groupsClassified & Operational Staff

    333

    IT, facilities, human resources, and paraprofessional personnel — e.g. @lausd.schools.email.

    Associated domain:schools.email

    schoolK–12 Students (Primary Pool)

    444 555 777 999

    A unified student block, backed by six expansion pools, for a total capacity of roughly 80,000,000 identifiers against about 54.6 million enrolled U.S. students.

    Associated domains: highschool.email middleschool.email elementary.school

    Expansion pools

    499 599 799 488 588 788

    computerReserved — MI Research & Development

    199 299 399 699 799 899

    A non-colliding sandbox that mirrors the production tiers, so developers can test MI-driven tools without any possibility of touching live school communication.

    flag
    MI Research area codes can be released into K12 Primary pool if needed.

    family_restroomParent Identity Recycling Protocol

    Parents and guardians bring their own verified mobile number as their handle. This is a human-facing mail identity for school parents. Once their child graduates high school, the email is recycled for future use by other parents — unless the parent still has a younger, not-yet-school-aged child, in which case the address is retained for that pending enrollment.

    Associated domain:parent.email
  • The Contact Initiative in Action

    The Contact Initiative white paper lays out the architecture: a federated identity anchor and attestation model instead of a single national ID, query-response verification instead of a browsable directory, and a Machine-Intelligence Authorization Layer that governs every MI-initiated action with scoped grants, audit logging, and human oversight. The six scenarios below show what that architecture looks like in practice.

    Every scenario is hypothetical and illustrative. None describes a system that currently exists or has been adopted by any school, district, institution, or government body. Scenario 5 extends further than the others, into location-sensing capability the white paper does not specify — it’s flagged throughout as a candidate for separate privacy and governance review, not a solved feature.

    1. Fixing a District’s Vendor Bottleneck

    School Contact — When a faulty vendor update takes down hero images across every school homepage in a district, the web administrator’s attested operational-staff identity grants scoped, logged access to the hosting environment — not standing access to every district system. Instead of hunting for the vendor’s current contact info, the admin runs a query-response check against the vendor’s verified support channel and gets a same-day rollback.

    Read the full scenario →

    2. Resolving an MI Scheduling Conflict

    University Contact — A student asks their MI assistant to email “my biology professor,” but the student has both a course instructor and a lab director. Because the MI Authorization Layer only ever holds a single-message, time-limited grant — never standing access to the student’s full record — it can’t quietly guess. Two different verified roles resolve to two different people, which trips the human-approval threshold: the assistant asks which one is meant, then logs the scoped credential and lets it expire.

    3. Stopping a Phishing Attack on Families

    School Contact — A phishing campaign spoofs a district’s branding to demand a fake “transportation fee” from parents. Mandatory domain authentication (DNSSEC, SPF, DKIM, enforced DMARC) means the spoofed mail never delivers as genuine in the first place. And because parents use a retired-never-recycled guardian alias, the school can check any reply against current, active guardianship before trusting it.

    Read the full scenario →

    4. Cross-State Enrollment After a Disaster

    School Contact — After a hurricane displaces hundreds of families, a receiving district can verify a child’s grade level, enrollment history, and — subject to the IEP/Section 504 legal review the white paper flags — accommodation status in seconds, through a signed request to the sending district. No centralized database, no records rebuilt from paper, no student waiting weeks to be seated in the right classroom.

    Read the full scenario →

    5. Active Campus Threat and MI-Coordinated Response

    School Contact & MI Authorization Layer — A verified call from an attested staff alias triggers a pre-scoped emergency grant — configured and revocable by a human administrator in advance, since a live approval step isn’t viable when seconds matter. The assistant issues an authenticated, campus-wide alert and relays verified caller data to 911, with every step logged for later review.

    This scenario is presented with more caveats than the others: real-time location sensing of students is a significant, separate capability the white paper doesn’t currently specify, and it would need its own dedicated privacy, security, and legal review before any real deployment.

    Read the full scenario →

    6. Community-Led Enrollment After Wildfire Displacement

    School Contact — When wildfire displaces an entire neighborhood, families use their existing guardian aliases to enroll together at a receiving school, coordinate housing and transportation among themselves on a separate parent-to-parent channel, and — because each student’s identity anchor persists and is never reassigned — kids stay reachable to their existing friends after the move.

    Read the full scenario →

    Where This Goes Next

    None of this replaces the legal, privacy, and governance review the white paper calls for before any real deployment. See our thinking on costs, governance, and the road to a pilot and the risks we’re taking seriously. Questions? Check the FAQ or get in touch.

  • Risks We Took Seriously — And How We’re Addressing Them

    Version 5 of the white paper incorporates the findings of an external red-team review conducted against the prior draft. Each identified risk is paired with who is likely to raise it and the specific mitigation now built into the architecture.

    • Identifier reassignment could misdirect sensitive communication to the wrong person — mitigated by retiring, never reissuing, identity anchors and parent aliases.
    • A centralized breach target would concentrate an entire population’s identity data — mitigated by a federated model where the national layer holds only short-lived attestations, and personal data stays with local systems of record.
    • Directory enumeration would turn a browsable list of verified educators into a target list — mitigated by query-response verification only, rate-limited to prevent scraping.
    • Guardianship and custody changes are common and were unaddressed in earlier drafts — mitigated by a separate, mutable relationship/authorization layer.
    • MI agent overreach would create a new insider-threat class — mitigated by scoped, short-lived, human-revocable credentials.
    • Perception as a national tracking database — mitigated by explicit statutory scope limits, sunset and oversight clauses, and consistent public framing as an interoperability standard, not a database.
    • Vendor lock-in via domain ownership — mitigated by a public-trust or licensing structure for domains, overseen by a multi-stakeholder body.
    • Unfunded mandate resistance — mitigated by strictly opt-in participation, a phased pilot, and an explicit funding-model proposal.

    Publishing the risks alongside the mitigations, rather than only the finished architecture, is intentional — it’s the same standard the framework asks legal reviewers and pilot districts to hold it to.

  • Costs, Governance, and the Road to Pilot Programs

    Costs Are Hypothesized, Not Assumed

    The white paper is explicit that any future ROI or savings projection must come from real pilot data and should never be presented as established fact before that data exists. Hypothesized benefit categories — reduced breach costs, reduced help-desk burden, faster emergency response — are named as things to be measured, not claimed in advance.

    Governance With Built-In Limits

    The proposed multi-stakeholder oversight body sits at a national layer while local and institutional systems remain the system of record for day-to-day identity issuance, attestation, and revocation — preserving the local control emphasized throughout the framework. Critically, the oversight body’s authority and the registry’s scope are proposed to be subject to periodic legislative or regulatory review, not open-ended by default.

    A Phased, Opt-In Path Forward

    Policy recommendations call for establishing the Contact Initiative as a voluntary interoperability standard endorsed — not mandated — by federal education authorities, preserving state and local control. Any adopting state or district would be required to complete the open legal-review items before handling real student data, and initial pilots would be funded through a competitive grant mechanism rather than an unfunded mandate, with results published regardless of outcome.

  • Rebuilding School Communities After Wildfire Displacement

    The Challenge

    Following a wildfire, residents of a single neighborhood are displaced to a nearby, overwhelmed county. Parents face re-enrolling their children in an unfamiliar school district while managing insurance claims and housing logistics. Without a unified system, information sharing is fragmented, and children risk being separated from their existing peer groups during a high-stress transition.

    The School Contact Solution

    The same retire-never-recycle guardian alias used to defeat phishing attacks also simplifies this transition. Displaced parents use their existing verified guardian aliases to coordinate with the receiving school and with one another.

    • Coordinated enrollment — because each student’s identity anchor is already linked to their guardian’s alias, a whole group of neighborhood families can independently enroll their children at the same receiving school, with the registrar verifying each family’s guardianship attestation.
    • Real-time information loop — a verified channel delivers authenticated district updates, while a separate parent-to-parent channel — never conflated with the school’s own broadcast alias — lets neighbors share transportation and housing information.
    • Continued peer connection — because each student’s identity anchor persists and is never reassigned, children can keep reaching established classmates through existing aliases after relocating, with no new accounts and no lost history.

    Demonstrates the relationship layer linking guardian and student identity anchors, and the persistence-without-reassignment principle at the center of the whole architecture.

  • Coordinated Emergency Response with Verified Communication

    The Challenge

    A coordinated incident begins at a large, multi-building high school campus. In a traditional environment, the first moments are defined by chaos: frantic calls from unverified numbers yield conflicting reports, staff struggle to trigger building-wide alerts, and first responders arrive without knowing which areas are secured.

    The School Contact Solution — With Caveats

    This scenario illustrates how the architecture’s reasoning could extend to emergency response, and it’s presented with more caveats than any other in our scenarios collection: real-time proximity or location sensing of students is a significant, separate capability the white paper does not currently specify, and it would require its own dedicated privacy, security, and legal review before any real deployment.

    • A staff witness places a call using her attested operational-staff alias to the school’s verified institutional line.
    • A pre-scoped, human-configured emergency grant — not a discretionary decision made in the moment — lets the MI assistant act only when a call originates from a verified alias and specific trigger language is used.
    • Once triggered, the assistant issues an authenticated, campus-wide alert, notifies the assigned officer, and relays verified caller and location data to 911 — every step logged for later review.
    • Any device-based, opt-in proximity capability is flagged as requiring its own separate consent model, strict retention limits, and independent privacy review before it could ever be built.

    Responders arrive with verified, authenticated information about where the alert originated and what has already been communicated — without this document making any claim about detecting, tracking, or neutralizing an intruder, which fall outside the scope of an identity and communication framework.

  • 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.

  • Stopping a Phishing Attack Before It Starts

    The Challenge

    A phishing campaign targets parents at a local high school. Bad actors send SMS messages and emails spoofing the school’s branding, claiming an active emergency and demanding a “transportation fee” to safely bus students to a reunification site.

    The School Contact Solution

    Under School Contact, the attack fails structurally rather than depending on parents noticing something is wrong. Every domain the district uses carries the mandatory email-authentication baseline — DNSSEC, SPF, DKIM, and enforced DMARC — so a spoofed message impersonating the district’s domain simply doesn’t deliver as genuine mail. The district pushes an authenticated, one-way broadcast confirming the earlier messages were fraudulent.

    Because parents communicate using their retired-never-recycled guardian alias, the school’s system can check any inbound reply against the relationship layer — confirming both that the alias is active and that the sender currently holds guardianship rights for a specific enrolled student — before treating it as trusted. And because the verified channel was never publicly browsable, it was never a target the attackers could spoof in the first place.

    Demonstrates the domain security baseline, the retire-never-recycle guardian alias policy, and query-response verification working together against a real attack pattern.

  • From Chaos to Clarity: Fixing a District’s Vendor Bottleneck

    The Challenge

    At a mid-sized K–12 district, the IT department wakes up to a flood of help-desk tickets: hero images aren’t displaying on any school homepage. In a legacy system, the web administrator would have to log into a dozen disparate content management systems, verify credentials for each school’s sub-vendor, and troubleshoot each domain individually.

    The School Contact Solution

    The district has unified its digital presence under the elementary.school hosting root. The lead web administrator logs in using their identity anchor, attested to the “Classified & operational staff” tier, and reachable at their institution-issued alias. Because the attestation layer is federated across the district’s hosted sites, this single verified login grants scoped, logged access to the hosting environment — not standing access to every system the district owns.

    The administrator traces the outage to a third-party design plugin’s faulty overnight update. Instead of hunting for the vendor’s current contact information, they submit a query-response verification request confirming the vendor’s registered support channel — a confirm/deny lookup, not a browsable listing. The vendor, seeing a digitally signed request from an attested sender, pushes a rollback patch. The hero images are restored across every elementary school site within minutes.

    Demonstrates the alias/attestation pattern and query-response vendor verification, not a browsable directory.

  • Building an Accessible System for Every Family

    Because the Contact Initiative is proposed as infrastructure that every parent, student, and educator must be able to use — not an optional convenience layer — accessibility is treated as a design requirement, not an enhancement to add later.

    • All public-facing verification and directory interfaces should conform to WCAG 2.2 AA at minimum, consistent with Section 508 obligations.
    • Alias-based communication should support non-email channels, such as SMS-based verification, for households without reliable email or broadband.
    • Verification and recovery flows should not assume a smartphone, a specific browser, or continuous internet access; a low-bandwidth, assisted in-person recovery path through a school registrar should always exist.
    • Materials and interfaces should be available in the languages a district or institution already serves, consistent with Title VI obligations.
    • Any biometric or novel authentication mechanism should be evaluated for disparate accessibility impact before adoption, not after.

    None of this is presented as solved. It’s presented as a checklist the architecture is required to satisfy before any real deployment — the same standard the white paper applies to legal compliance and cybersecurity.

  • Privacy, FERPA, and COPPA: What Families Should Know

    This section of the white paper does not provide legal advice, and nothing in it should be read as a completed compliance determination. Every mechanism described is a proposed approach, offered for review by qualified counsel and the relevant regulators before any pilot handling real student or family data proceeds.

    FERPA

    FERPA governs both halves of the initiative, in different directions. K–12 School Contact is designed around FERPA’s district-defined, opt-out directory-information framework. Higher-education College and University Contact treat the adult student as the default rights-holder, consistent with FERPA’s transfer of rights at eighteen or postsecondary enrollment.

    COPPA

    COPPA is proposed to be addressed in K–12 through a front-end tokenization pattern, so vendors receive a scoped token rather than a student’s actual identity or record — offered as a mitigation pattern requiring review against COPPA’s specific verifiable-parental-consent requirements, not a claim of current compliance.

    IDEA, Section 504, ADA, and State Law

    A national student-identity system will necessarily touch special-education status and accommodation records for some students, and this paper flags that IDEA, Section 504, and the ADA apply and have not yet been reviewed against the proposed architecture. State student-privacy laws vary and are often stricter than federal law, so any national architecture must accommodate the strictest applicable state requirement in a given jurisdiction — a significant open design question. See our FAQ for more.

  • Cybersecurity by Design: The Contact Initiative Approach

    The Contact Initiative treats cybersecurity as an infrastructure-level property, not an add-on, through a defined set of controls:

    • Verified, role-based identity for every user, separate from any reassignable number.
    • Zero-trust access to the resolution layer — no standing access for any relying party, vendor, or MI agent.
    • Non-enumerable, rate-limited query-response verification, preventing bulk scraping of the identity graph.
    • Mandatory DNSSEC, SPF, DKIM, and enforced DMARC on every issued domain.
    • Aliases that hide the administrative address, shrinking the target for spear-phishing.
    • Scoped, short-lived credentials for vendors and MI agents instead of raw record access.
    • Persistent, tamper-evident logging at both the institution and national-registry level.
    • Mandatory dual control for high-impact actions like bulk data export or identifier retirement overrides.
    • A public security-disclosure and bug-bounty commitment for the registry and its reference implementation.

    That vendor-focused control matters most: reported research indicates a majority of disclosed K–12 breaches trace back to a compromised vendor, not the district itself. Tokenized, scoped, short-lived vendor credentials are aimed squarely at closing that pathway.

  • Machine Intelligence and the Future of School Communication

    Consider a simple instruction given to an MI assistant: “Email my professor about the extension.” Without reliable identity infrastructure, the system has to guess which course, which professor, which section, and whether the requester is even enrolled — and it sometimes guesses wrong.

    Why “MI,” Not “AI”

    The Contact Initiative deliberately uses Machine Intelligence (MI) instead of Artificial Intelligence (AI) wherever reasonably possible, to describe capability that operates strictly within a human-governed structure — able to act only after a person or institution is verified, and only within limits a human governance body has set and can revoke at any time.

    How the Authorization Layer Works

    Before an MI assistant can act, it must request a scoped grant limited to the specific task at hand — never standing access to a person’s full academic or communication record. If a request is ambiguous, a human-approval threshold is triggered and the assistant asks for confirmation instead of guessing. Every credential is short-lived, and every action is logged for audit.

    This is also the foundation for the Machine Intelligence Assistant (MIA) — a proposed persistent, personalized tutoring and mentoring assistant for students and researchers, operating entirely within these same scoped, revocable, and auditable boundaries.

  • How Aliases Protect Students and Parents from Phishing

    Earlier drafts of the Contact Initiative imagined a public, browsable directory where anyone could look up a verified teacher or administrator. Review identified an obvious problem: a browsable list of every verified educator in the country is also a ready-made target list for harassment.

    Query-Response, Not Browsable

    Version 5 replaces the browsable directory with query-response verification. A relying party submits a specific claimed identity — “is this person currently a teacher at this school?” — and receives a confirm or deny answer, rate-limited to prevent bulk scraping. This preserves the entire anti-phishing benefit of the original idea while removing the enumeration risk.

    Aliases That Can Be Replaced Without Losing Identity

    Institution-issued aliases follow role-based, human-readable patterns and can be rotated or reissued at any time without affecting the underlying identity anchor or its attestation history. A compromised or leaked alias can simply be retired and replaced — no loss of identity continuity, and a much smaller practical target for spear-phishing.

    A Non-Negotiable Security Baseline

    Every domain issued under the Contact Initiative — production or sandbox — is proposed to carry DNSSEC and registry lock to prevent hijacking, enforced SPF, DKIM, and DMARC with a reject policy to stop spoofed mail from delivering as genuine, and a published, cryptographically signed list of real Contact Initiative domains so relying parties can spot look-alikes.

  • 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.