Human-agent trust for education
The detector wars ended. Turnitin's AI flag has a 14% false-positive rate. GPTZero recanted its accuracy claims. The only durable answer to "did the student do this work?" is not detection — it is a cryptographic record of how the work happened. That is what Manav offers schools.
The new honor code
The honor code is no longer "do not use AI." It is "declare how you used AI, and prove it." The first half is policy. The second half needs infrastructure. Manav supplies the infrastructure: a Trust Score, an attestation chain, and a role declaration — authored, supervised, or directed — that the student signs at submission and the institution can later audit.
The three roles, reframed for school
Authored means the student wrote the work; an AI may have suggested edits but the words are the student's. Supervised means the student directed an AI to produce a draft and meaningfully revised it. Directed means the AI produced the bulk and the student approved. Each carries a different academic weight; the policy assigns the weighting, the infrastructure makes the declaration verifiable.
What lands in the audit log
The student signs the submission with their Manav DID. The submission carries a manifest: which AI tools were used, which prompts (hashed, not plaintext), how many revision rounds, the role declared. The instructor can verify the student is real (not a stand-in), the timestamps are authentic, and the role declaration is consistent with the editing pattern Manav fingerprints during the writing session.
Anti-proxy: the "ghost-writer" defense
The single most under-discussed academic-integrity threat today is not AI; it is the contracted human ghost-writer. Manav's behavioral biometric layer fingerprints typing cadence, edit patterns, and pause distributions during the writing session and ties them to the registered student's prior baseline. A ghost-writer's session shows up immediately because the writing pattern does not match the student's baseline — and the instructor sees a single yellow flag, not a drama.
What schools can demand without getting sued
Three things, all defensible. The student's Manav DID for submission identification. A role declaration on each submission. The behavioral baseline, captured at orientation under disclosed terms. Critically, schools should not demand the student's full attestation chain across other classes or other universities. Selective disclosure means the student presents only what's needed for this submission, in this course, this term.
What this enables for students
Portable academic credentials. A graduate's Manav DID, signed by the institution, lists every course, role declaration, and Trust Score earned. Recruiters verify cryptographically; the student keeps the diploma forever, even if the institution closes. The diploma becomes the audit log.
Common objections
The two pushbacks we hear from this vertical: integration risk — addressed by phased rollout starting with the audit trail (lowest risk, highest evidence-to-effort ratio), and internal politics — addressed by anchoring the project to a regulator deadline or a security-questionnaire deal-blocker, where the political question answers itself.
Frequently asked questions
What is the first integration to ship? The signed audit trail. It costs least, satisfies the most regulators, and produces the evidence everything else builds on. Every vertical we have integrated started here.
How does this affect end-customer experience? Invisibly, by design. The customer sees the same UI; the difference is in the audit log behind it. The latency added is single-digit milliseconds. The trust gain is structural.
What's the buying motion — security, compliance, or the line? Compliance writes the check; security signs off; the line of business sets the timeline. The strongest deals start with a regulator deadline; the next-strongest start with a deal-blocking security questionnaire.
Where to start
The first integration we recommend in this vertical: proof of human work, then resume fraud ai era. Both are deployable inside a quarter; both produce regulator-grade evidence; both unblock procurement conversations the rest of the stack depends on.
What the registrar's office gets out of this
The registrar's office is the unsung beneficiary of the academic-integrity substrate. Today, the registrar fields requests for transcripts, certifications, and verification letters across every channel — phone, email, fax, in-person — at a labor cost the institution rarely models accurately. A Manav-bound transcript answers the verification question without the registrar's involvement; the verifier checks the signature, the institution's issuance, and the student's consent in seconds. The registrar's caseload drops by an order of magnitude on transcript requests. The reallocated capacity goes to higher-value work the office was perpetually under-resourced for: graduation planning, credential evaluation for transfer students, accreditation reporting. The substrate is therefore not just an integrity tool; it is a labor-saving infrastructure for the office that pays for it. We have made this case to registrars in pilot conversations and it has been more persuasive than the integrity case. The dual benefit is real and quantifiable.
The post-detector era of academic integrity runs on signatures, not suspicion.