- Executive Summary
College Contact proposes a national identity and communication framework for higher education, adapting the K–12 School Contact model to adult rights-holders, contested faculty rank, and concurrent institutional affiliation. Both College Contact and School Contact are proposals from the Department of Technology. As the opening post, it frames the identity problem this whole series addresses. The next post, Terminology Statement, explains the paper’s core vocabulary choice: MI over AI.
- Terminology Statement
Following the Executive Summary, this section explains why College Contact writes MI instead of AI throughout the paper, and introduces MIA, the Machine Intelligence Assistant discussed later in Section 7.3. It sets up the vocabulary used in every post that follows, starting with the next one, which introduces the higher-education identity problem itself in full.
- 1. Introduction
Building on the terminology set out in the previous terminology, this introduction describes how a single instructor’s identity gets scattered across email systems, LMS platforms, and payroll records at multiple institutions. It sets up the deeper dive that follows: the next post examines exactly how higher education’s identity problem differs from K–12’s, in detail.
- 2. The Higher Education Identity Problem
This section unpacks four ways higher-education identity differs from K–12: adult FERPA rights, contested faculty rank, concurrent institutional affiliation, and impersonation risk. It expands on the fragmentation introduced in the prior post and sets up the next one, which lays out College Contact’s proposed vision for solving each of these specific problems.
- 3. The College Contact Vision
Having diagnosed the problem previously, this one introduces College Contact’s proposed trust layer connecting students, instructors, departments, and institutions, plus its four foundational objectives: identity, verification, communication, and MI readiness. The next post grounds these objectives in eight concrete Core Principles the whole architecture must follow going forward.
- 4. Core Principles
We list the eight principles governing College Contact’s design, from identity-before-access to human governance over consequential decisions. These principles constrain the vision described just before it, and directly shape the next post, which turns them into a concrete, layered identity architecture spanning person, role, affiliation, rank, and communication identity.
- 5. Proposed Identity Architecture
This part lays out the conceptual hierarchy from person to authenticated, authorized action, showing how one identity can carry multiple concurrent institutional affiliations. It operationalizes the principles from the prior post. The next post applies this architecture to a specific communication layer: the proposed domain and email portfolio in full detail.
- 6. Communication Architecture
The longest section in the series, this part details the proposed domain portfolio, the reserved MI beta-testing tier, and the split between human-facing mail domains and public verification domains. It builds directly on the architecture in the prior post and leads into the next post, which covers MI readiness and MIA tutoring assistants directly.
- 7. MI Readiness
This post explains how MI systems should resolve identity rather than guess it, why MI should not replace academic governance, and introduces MIA, the persistent tutoring and mentoring assistant. It depends on the domain and identity infrastructure from the prior post, and precedes the next post’s look at cybersecurity implications for higher education.
- 8. Cybersecurity
This short section covers how verified role and domain infrastructure could reduce phishing and impersonation, while noting it would not eliminate insider threats or credential theft on its own. It follows directly from the MI readiness discussion and leads into the next post’s focus on privacy and FERPA-specific data governance.
- 9. Privacy and Data Governance
This post applies the paper’s authenticate-more-expose-less principle to adult students under FERPA and to faculty professional information. It follows the cybersecurity discussion and sets up the next post, which explains how College Contact should connect to existing systems rather than duplicate the data it just described protecting so carefully.
- 10. Interoperability
A brief part explains that College Contact should sit alongside student information systems, LMS platforms, and existing SAML or Shibboleth federations rather than replace them outright. It follows the privacy discussion and leads into the next post’s three-phase roadmap for actually building and piloting this interoperable trust layer over time.
- 11. Implementation Roadmap
This post lays out the three-phase path from research and alignment, through pilot, to contingent scaling across research universities, teaching colleges, and community colleges. It turns the interoperability commitments from the prior post into a timeline, and precedes the next post, which addresses who governs the framework at each phase.
- 12. Governance
This section argues governance must be independent and avoid concentrating control of root domains in one commercial operator — including the Department of Technology, which holds no governance authority of its own — naming the stakeholders who should hold that authority instead. It follows the roadmap’s phases and precedes the next post, which works through the specific risks that this governance model is meant to mitigate.
- 13. Risks and Counterarguments
This part works through five risks, including rank-verification disputes, centralization, cost, MI misresolution, and data consolidation, pairing each with a mitigation. It stress-tests the governance model from the prior post and leads into the next post’s description of the pilot program meant to test these risks against real evidence.
- 14. Pilot Program
A short post defining what a pilot should actually measure: phishing resistance, impersonation detection, concurrent-affiliation handling, and MI identity-resolution accuracy across research universities, teaching colleges, and community colleges. It responds directly to the risks named just before it and leads into the national policy recommendations that follow next.
- 15. National Policy Recommendations
This part lists seven concrete policy steps, from forming a working group to explicitly not pursuing mandatory adoption until pilot evidence supports it clearly. It turns the pilot design from the prior post into action items, and precedes the next post’s broader argument for why this work matters at a national scale.
- 16. A National Imperative
Stepping back from the specific recommendations before it, this post situates College Contact within international competition over MI capability, arguing that trusted identity infrastructure is one small but real piece of a much larger national effort. It sets up the final post, the Conclusion, which ties the whole series together.
- 17. Conclusion
This part closes the series by restating how College Contact adapts School Contact’s core architecture, persistent identity, verified role, and human-governed MI, to higher education’s adult rights-holders and concurrent affiliations. It follows the national-imperative argument and points readers to the Appendices for reference tables, open questions, and a short glossary.