Submit an official source URL
Suggest a public university AI policy, teaching guidance, academic integrity, privacy, procurement, or security-review source.
Contribution intake
Submit evidence into a review queue
Contributions help expand coverage, but they do not create canonical policy facts directly. Every source URL, correction, translation fix, or course-level submission starts as a review task with privacy, copyright, source-language, and evidence checks.
Contribution paths
The first live intake channel is GitHub issue templates, so submissions are visible, auditable, and reviewable before publication.
Report a policy change
Report that an existing tracked source changed or that a university added, moved, removed, or blocked an AI policy source.
Submit an institution correction
Request correction of an institution name, source attribution, review-state interpretation, or canonical page metadata.
Submit a course AI policy
Submit structured course-level AI policy evidence. Course data remains pending until moderation, rights, and claim/evidence review are complete.
Submit a translation or evidence-display correction
Correct localized display text while preserving the original-language evidence as canonical.
Report a dataset or API issue
Report broken JSON, stale links, checksum issues, field-shape problems, or inconsistency between public pages and public JSON.
What a submission can and cannot do
This is the publication boundary for all contribution types.
- Submissions create review tasks, not canonical facts.
- Every published claim must keep source URL, source language, evidence snippet, confidence, and review state.
- Confidence and review state remain separate.
- Original-language evidence remains canonical; localized display is helper text only.
- Institution corrections preserve audit history.
The tracker is not legal advice, not academic integrity advice, and not an official university statement unless a linked source is the university's own official page.
Course-level submissions
Course-level policy submissions are useful, but they are handled as evidence records, not as open comments.
Course records must reuse the same claim/evidence structure as university records: entity, term, source type, claim, original-language evidence, source language, review state, and moderation status. Do not paste full syllabi, LMS content, private student information, or non-public instructor data.
Contribution API metadata
Machine-readable intake policy for agents, developers, and contributors.
Contribution index
Contribution workflows, required fields, GitHub issue template URLs, safeguards, and publication rules.
Review policy
Review queues, publication gates, moderation rules, and contribution review boundaries.