Appearance
Are you an LLM? You can read better optimized documentation at /platform/governance/operating-model.md for this page in Markdown format
Governance Operating Model
Governance in Modulos is a continuous procedure: set the scope, complete Controls, collect Evidence, and keep each decision on the record while the AI System changes.
What this is
Modulos governance keeps obligations and the work that satisfies them apart:
- Frameworks tell what applies.
- Requirements keep the structure of the source document and tell what you must satisfy.
- Controls tell how you satisfy Requirements. You can use one Control for Requirements of more than one framework.
- Evidence attaches to Controls as proof.
- Comments and Logs record each status change and each decision, but a framework update that archives a Requirement makes no log entry. Assets also have formal Reviews.
Where in Modulos
Governance work happens in AI Systems:
AI System → Requirementsto monitor obligations and fulfillmentAI System → Controlsto complete Controls and set their statusAI System → Evidenceto upload Evidence and use it for more than one ControlAI System → Assetsto keep documents current and download them as MarkdownAI System → Settings → Frameworksto add frameworks and update their versionsAI System → Dashboardto monitor the Controls that the AI System needs at its lifecycle stage, and to export the AI System PDF
Who can do what
Permissions
- AI System Owners set up frameworks and access, select Requirement Owners, and remove blockers.
- Editors complete Controls, attach Evidence, and keep work items current.
- Viewers can see the work, the Evidence, and the history. They can add comments, but they cannot change the work.
Each work item also has an owner:
- The Control Owner does the work of the Control and sets its status. The owner of a mapped Requirement can also set the status, and selects the Control Owner.
- The Requirement Owner marks the Requirement as Fulfilled when all its mapped Controls have a final status.
How it works
Object model and traceability
Modulos makes an audit trail from the links between work items:
- Framework What applies
- Requirements The obligations, in the structure of the source document
- Requirements map to Controls
- Controls How you satisfy the Requirements
- Evidence The files that prove the work
- Policies The published Policies that the Control links to
- Comments and Logs Each status change and each comment
One Requirement can map to more than one Control, and one Control can map to Requirements of more than one framework. Requirements also have Comments and Logs. The AI System PDF has the Comments and Logs of each Control, but not those of the Requirements.
Modulos keeps two records apart:
- the status of a work item (its current condition)
- the decisions about the work item: comments, the fulfillment decision of the Requirement Owner, and the Reviews of Assets
This keeps the work fast and the record complete for an audit.
Controls: status changes
A Control is Not Executed until its work is done. The usual sequence is:
- Do the work: the Control Owner writes the report and attaches Evidence.
- Set the status: the Control Owner sets the status to Executed. There is no reviewer approval. Modulos logs who changed the status and when.
- Requirement Review: when all mapped Controls of a Requirement have a final status, the Requirement is ready for review. The Requirement Owner examines the work and marks the Requirement as Fulfilled.
- Locking: while a Control has a final status, its content is locked.
When an Executed Control goes back to Not Executed and a mapped Requirement is Not Fulfilled and ready for review, Modulos makes you type why. This comment keeps the cause of the reopened work for auditors. The status rules are on Reviews & Statuses.
Requirements: readiness and fulfillment flow
Requirements are obligations. Their status goes from Not Fulfilled to Fulfilled.
In Modulos, fulfillment is a decision that a person records:
- A Requirement is ready for review when all its mapped Controls have a final status.
- The Requirement Owner then marks the Requirement as Fulfilled. This records the decision that the obligation is satisfied for the scope of this AI System.
This makes the responsibility clear:
- Control Owners do the work and attach the proof
- Requirement Owners record that the obligation is satisfied
See Requirements for the readiness signal and the fulfillment procedure.
Evidence: use and locking
You attach Evidence to the Evidence section of a Control. One Evidence item can be attached to more than one Control, and each Control shows the Evidence that it uses.
While a Control that uses an Evidence item is Executed, Modulos locks that Evidence item. Then nobody can change the proof after the work is done. See Evidence.
How to use it
- Set the scope Add the frameworks that apply to the AI System. When a framework has a new version, update it when you are prepared for the scope changes.
- Select owners Select a Requirement Owner for each Requirement, then Control Owners.
- Complete Controls Write the reports, attach Evidence, and keep them current.
- Set Control statuses The Control Owner sets each completed Control to Executed. A Control that does not apply goes to Out of Scope.
- Mark Requirements as Fulfilled When a Requirement is ready for review, the Requirement Owner marks it as Fulfilled.
- Export and audit Export the AI System PDF when the scope and the statuses are stable.
Governance continues after the first audit. Start again at step 1 when the AI System, its vendors, its data, or its frameworks change.
Important considerations
- Divide the duties where possible: Editors complete Controls, Requirement Owners examine Requirements and mark them as Fulfilled, and Viewers monitor.
- Write a clear name and description for each Evidence item. Then each Control shows clearly what its proof is.
- Near the end of an audit, an Organization Admin can freeze framework updates. Then the scope does not move.