Tag: terminology

  • Terminology Statement

    Why College Contact Uses MI

    Consistent with the School Contact Initiative, this proposal uses MI in place of AI wherever reasonably possible. MI is used to emphasize machine-based intelligent capability operating within a human-governed structure of identity, authorization, and accountability, rather than to suggest a system that acts independently of institutional and legal responsibility. AI is retained only when referencing an external source, an existing law or standard, or conventional terminology for clarity.

    This paper extends that terminology to a specific application discussed in Section 7.3: the Machine Intelligence Assistant, or MIA, proposed as the term for a persistent, personalized tutoring and mentoring assistant used by students and researchers. Other acronyms for comparable tools may exist or emerge elsewhere; College Contact has chosen MIA to remain consistent with, and to reinforce, its broader advocacy for MI over AI.

  • MIA, Explained: What a Machine Intelligence Assistant Is (and Isn’t)

    MIA stands for Machine Intelligence Assistant — a persistent, identity-aware tutoring and advising presence proposed in Section 7.3 of our white paper. Unlike a generic chatbot, an MIA is designed to operate inside the identity and authorization architecture described throughout the paper, meaning it knows a student’s verified affiliation and role before acting on their behalf.

    Just as important is what MIA is explicitly not: it isn’t a replacement for academic governance, human advisors, or faculty decision-making. Our MI Readiness section spells out the boundaries deliberately, because we think the appeal of a helpful assistant shouldn’t be allowed to quietly expand its authority over time.

  • Term of the Month: Why We Say “Verification Domain,” Not “Login Domain”

    Our white paper deliberately separates mail domains (where communication happens) from verification domains (where identity claims can be checked). A “login domain” framing suggests access is the point. A “verification domain” framing makes clear the point is proof — confirming that a claimed role or affiliation is currently accurate, independent of whether you’re logging in to do anything else.

    Section 6.3 of the white paper, Mail domains versus verification domains, goes through this distinction and why collapsing the two into one system would undermine the trust the whole framework depends on.