A lightweight operating model keeps the framework maintainable without turning it into a paperwork exercise — a shared header on every document, and a short review workflow.
Each artifact should start with a simple header so its type, owner, and visibility are unambiguous.
Document Title: [Title] Document Type: [Policy / Profile / Service Card / System Card / Model Card / Review] Primary Audience: [Users / Governance / Public / Auditors] Visibility: [Public / Institution-wide / Restricted Internal / Confidential] Owner: [Office / Team] Approver: [Role / Committee] Version: [x.y] Review Date: [YYYY-MM-DD]
Five steps move a document from draft to published, with visibility checked at the points where it matters.
What counts as a material change. For a shared platform, review is continuous rather than one-time: a material change includes enabling a new model, modality, tool, or integration, or opening up a new category of downstream use. Any of these re-triggers the workflow before it goes live.
The framework is both a transparency tool and a governance operating model.
The result is a documentation stack that lets institutional users understand what AI tools exist and how to use them, while giving reviewers and auditors enough internal evidence to assess risk, controls, and accountability.
Suggested use: publish this site as a framework overview, then attach detailed templates and supporting documents as appendices or linked source artifacts.
Read the whole framework as a formal whitepaper, or walk the seven layers starting from the hierarchy.