Appearance
Assets & Documents
Modulos keeps living documents and audit proof apart. This lets teams work together and the audit record stays correct.
- Assets are living documents: narratives, system descriptions, model cards, and procedures that you change as the AI System changes.
- Evidence is proof: files that show that a Control is done. Modulos locks an Evidence item while a Control that uses it is Executed.
What this is
An Asset is a document card in an AI System. Assets are for:
- daily documentation that changes
- work by more than one person, with an Owner and a formal Review
- downloads of the content as a Markdown file
Evidence is different. If you must show proof in an audit, attach an Evidence file to the Control that it applies to.
For the end-to-end governance model, see Governance Operating Model.
Where in Modulos
AI System → Assetsto see and create Assets. The list has the columns Name, Type, Nature, Value, Created, Modified, Owner, and Status. Search by name or code, and filter by Type and Nature. The download icon of a row saves the content of the Asset as a Markdown file.- Open an Asset to see the tabs Asset and Comments and Logs. On the Asset tab, you edit the content, then select Save or Download File. The Info panel shows Type, Nature, Value, Owner, Status, Assigned To, and Reviewer(s).
AI System → Evidenceto manage the audit proof (files)
Who can do what
Permissions
- All members of an AI System can see its Assets, their history, and download them.
- AI System Owners and Editors create and edit Assets, and they can request a status change.
- Only AI System Owners can be reviewers of a Review request. The reviewer selects Approve or Reject, and the decision goes into the history of the Asset.

An Asset is a living document. You edit it on the Asset tab and request a Review when a status change needs approval.
- Asset Shows the code and the name of the Asset.
- Request status change Starts a Review request. An AI System Owner approves or rejects it.
- Asset Keep model cards, dataset cards, and procedures current here.
- Status Shows the status and the users who keep the Asset current.
How it works
Asset cards as living docs
You use Assets for documentation such as:
- system descriptions and notes about the architecture
- documentation of a model, a dataset, or the instructions to a model
- operating procedures and runbooks
Assets have an Owner, an assigned user, comments, notifications, and Review requests.
New Asset opens the Create New Asset dialog, for AI System Owners and Editors:
- Asset Name: up to 50 characters.
- Asset Type: General Card, Model Card, or Dataset Card. You cannot change the type later.
- Nature: Intangible (the default) or Tangible.
- Value (optional): a monetary value in the currency of the organization.
Save creates the Asset and opens it. The Owner of an Asset is the user who created it. While the Asset is In Progress, Edit Info on the Asset page changes the name, the nature, and the value.
An Asset is In Progress, In Review, or Completed. While an Asset is not In Progress, its content, its Assigned To field, Edit Info, and new comments are locked. To change the status, select Request status change. For the Review procedure, see Reviews & Statuses.
Evidence files as audit artifacts
You attach Evidence files to Controls as proof. While a Control that uses the proof is Executed, the proof cannot change. See Evidence.
Other documents
Modulos keeps other documents in other locations:
- Vendor documents belong to a Vendor (for example DPAs, SOC reports, and questionnaires). See Vendor Documents.
- Exports are snapshots of an AI System at one point in time. See Reports & Exports.
How to use it
- Write narratives as Assets Keep system descriptions, procedures, and model cards as living documents.
- Assign the Asset Set Assigned To while the Asset is In Progress. The Owner is the user who made the Asset.
- Request a Review Request a status change when a document needs formal approval.
Important considerations
- Keep proof and narrative apart. If an auditor needs proof, attach Evidence to the Control.
- Use Assets to keep "why we do this" and "how we do this" current, mainly for the documentation of the AI system.
- Keep documents in Assets with a clear Owner, and not in many external tools.