
Introduction
The Supply Chain functionality in the Cranium platform provides a powerful way to manage and share AI System artifacts with other organizations. AI Cards are exportable collections of artifacts you share with other organizations, such as AI Bills of Materials and Compliance Frameworks. An AI Card can also share a summary of the vulnerabilities found in the Bills of Materials on the card. The platform allows you to choose specific artifacts to include when publishing your AI System and request AI Cards with customized artifact requirements. You can also define the Compliance Frameworks (e.g., EU AI Act or NIST AI RMF) and indicate whether sharing a Bill of Materials is required.
These features facilitate seamless collaboration across organizations and simplify compliance practices, allowing you to demonstrate transparency and showcase your AI systems' security posture. The Supply Chain features are organized into five tabs within the AI Manager section: My AI Systems, My Vendors, Incoming Requests, Outgoing Requests, and Published AI Cards.
Note: For information about publishing AI Cards from your AI Systems, see the My AI Systems section of the knowledge base. Published AI Cards are representations of AI Systems and are managed through the My AI Systems tab.

Quick Actions
All three Supply Chain tabs include Quick Actions buttons at the top of the page:
- Create AI System: Initiate the development of a secure AI system to enable system-level tracking
- Request AI Card: Acquire an AI Card from third-party vendors, ensuring it complies with predefined criteria
- Publish AI Card: Distribute an AI Card to various organizations to effectively communicate the system's specifications and capabilities
These actions provide quick access to common supply chain workflows regardless of which tab you're viewing.
My Vendors
The My Vendors tab provides an aggregated view of the AI Cards you have received from external organizations. For full documentation of this tab, see the My Vendors Overview article.
Review AI Card
When an AI Card has a status of Pending or Changes Requested, a Review AI Card button appears in place of the standard View Details button. Click Review AI Card to open the Review AI Card drawer. The drawer is organized into two sections:
Requested Section:
- Request Details
- Compliance Frameworks requested
- Bill of Materials requirements
- Additional Documentation requirements
AI Card Response Section:
- AI Card Name
- Bill of Materials included
- Additional Documentation included
At the bottom of the review panel, you have three action options:
- Decline: Reject the AI Card
- Request Changes: Send feedback requesting modifications to the AI Card
- Accept AI Card: Accept the AI Card as provided
Incoming Requests

The Incoming Requests tab displays all pending requests from other organizations for your AI Cards. This table view shows requests you've received asking you to provide AI transparency documentation.
Incoming Requests Table
The Incoming Requests table displays:
- Name: The AI System name being requested
- From: Requesting organization name and user email
- Due Date: The deadline for responding to the request
- Details: Brief description or notes about the request
- Status: Current status of the request (e.g., Pending, Completed, Approved)
- Action: "Review Request" button to respond to the request
Responding to Requests
Click the "Review Request" button in the Action column to respond to an incoming request. This opens the request review interface where you can view the specific artifacts being requested and prepare an appropriate AI Card response. For detailed information about responding to requests, see the "Responding to an AI Card Request" article.
Outgoing Requests

The Outgoing Requests tab displays all requests you've sent to other organizations asking them to provide AI Cards. This table view tracks the status of your outbound requests for AI transparency documentation.
Outgoing Requests Table
The Outgoing Requests table displays:
- Name: The AI System name you're requesting information about
- To: The organization name and user email receiving the request
- Date Sent: When you sent the request
- Due Date: The deadline you set for the response
- Details: Brief description or notes about your request
- Status: Current status (e.g., Pending, Completed)
This table allows you to track which organizations have received your requests, monitor response deadlines, and see the current status of each request. You can sort by any column to organize your outgoing requests by date, recipient, or status.
Managing Outgoing Requests
Use the table to monitor the progress of your requests and identify which organizations still need to respond. The status column provides quick visibility into whether your requests are pending, have been completed, or require follow-up action.
Published AI Cards
The Published AI Cards tab displays a searchable, filterable grid of all AI Cards you have published to other organizations. Each card shows:
- AI Card Name: The name of the published AI Card
- AI System: The AI System the card represents
- Date Sent: When the AI Card was published
- Recipient: The organization the card was sent to
- Status: Current status of the published AI Card
- Artifacts: Visual breakdown of included artifacts with counts for BOMs, Compliance Frameworks, and Documents.
- Vulns (N): Shown when the card shares vulnerability data. The total number of shared vulnerabilities, with a model chart (Critical, High, Medium and Low) and a technology chart (Critical, High, Medium, Low and None).
Published AI Card Statuses
Published AI Cards can carry the following statuses: Accepted, Up-to-Date, Outdated, Pending, Deactivated, Rejected, and Deleted. Cards with an Outdated status display as "Out of sync" with an Update button, prompting you to republish when your AI System's content has changed since the card was last sent.
A card that shares vulnerability data is also marked Out of sync when a vulnerability assessment completes for one of its Bills of Materials. Shared vulnerability data refreshes only when you select Update. Until then, the recipient keeps the earlier snapshot and is not told that newer results exist.
Viewing Published AI Card Details
The AI Card detail view shows everything a published card shares, so you can check exactly what the recipient sees. Click View Details on any card to open it. You and the recipient see the same views. The view is organized into tabs. Every card has Overview, Artifacts and Governance tabs. A card that shares vulnerability data also has Model Vulnerabilities and Technology Vulnerabilities tabs.
- Overview: Summarizes the card. It shows the AI System name and Artifacts (N), the total number of artifacts with a bar and count for each type: BOMS (Bills of Materials), COMP (Compliance Frameworks), REP (Vulnerability Reports) and DOCS (Documents). On a card that shares vulnerability data, a Vulnerabilities (N) card shows how many findings are resolved under each chart, with a legend and See All.
- Artifacts: Shows a card for each included artifact, with its type label, name, creation date and time, and status (such as Completed or Failed). Vulnerability report PDFs attached to cards published before shared vulnerability data was available remain here, and recipients can still view and download them.
- Model Vulnerabilities: Lists the shared model findings by severity.
- Technology Vulnerabilities: Lists the shared technology vulnerabilities by severity. It includes an AI column and a Show AI vulnerabilities only filter, the same as the main Vulnerabilities page.
- Governance: Shows the information recorded about the AI System, grouped into sections. System Information holds Purpose, Date of Initial Deployment, Last Updated and Next Regular Update. Values holds Value Statement and Link to Organizational Value. Data holds Description, Data Provenance and Data Protection. Fields left blank show Not provided.
Until vulnerability data has been captured, both vulnerability tabs show No vulnerability data has been shared yet.
The shared vulnerability data is a snapshot taken when the card is published or updated. It includes CVEs, model findings, resolved findings and their resolution reasons. It does not include who resolved each finding, the AI System, the project name or the repository name. Recipients cannot act on findings.





