Creating a DisclosureEnterprise
Attach a Living Disclosure to a use case, configure what it publishes, and activate it.
Before you start
A use case becomes eligible for a disclosure once it reaches the Mitigate stage, and stays eligible through Approval and Monitor. Creating a disclosure early is useful, since it lets you configure and preview it ahead of time, but it will not actually publish anything until the use case reaches Monitor. See Stage Transitions for the full lifecycle.
A use case can have only one disclosure. If a use case already has one, its row won't be offered again when creating a new disclosure. Open the existing disclosure instead to adjust it.
Creating a disclosure
Go to Governance > Living Disclosures and select the Disclosures tab.
Select Create Disclosure. You'll be prompted to choose a use case; only use cases that are eligible and don't already have a disclosure are offered.
You're taken to the disclosure's detail page, where you can review what it inherits and adjust overrides before activating it.
Configuring what it discloses
Every disclosure inherits its starting values from the applicable Disclosure Template for the use case's audience. From the disclosure's detail page, each disclosable attribute can be set independently:
| Setting | Effect |
|---|---|
| Inherit | Follows the template's current value. If the template changes later, this disclosure changes with it. |
| Disclosed | Always shown, regardless of what the template says. |
| Not Disclosed | Always hidden, regardless of what the template says. |
Attributes are grouped the same way they are in a template: Asset Identity, Model Details, Guardrails, Risk Classification, Use Case Details, Human Review, and Disclaimer. See Disclosure Templates for what each group actually reveals.
Use Preview disclosure on the detail page to see exactly what the public page will show with your current overrides applied, before activating.
Activating and deactivating
A disclosure does nothing until it's active. Use the Activate / Deactivate control on the disclosure's detail page:
- Activating makes the disclosure eligible to publish (still gated on the use case being at Monitor) and creates its public link.
- Deactivating immediately stops publication and invalidates the public link. Anyone who had it gets a not-found page. Nothing is deleted; reactivating restores the same disclosure and generates a new link.
The public link
Every active disclosure has a public page reachable without an Airia account. This is what the link header on API responses and the Slack governance footer point to. It's meant to be shared with the people the disclosure is about: end users, auditors, or regulators. Deactivating the disclosure invalidates every copy of the link that's already out in the wild.
Living Disclosures
Publish a machine-readable, self-updating AI disclosure at the point a governed use case is used, covering who built it, what model answered, and what controls apply.
Configurations
Manage governance frameworks, approvers, assessment templates, disclosure templates, and risk tolerance.