Release
Evidence that a decided change was delivered.
Link Decision and, when relevant, About (Content). Released At, Resource Version, Evidence and Run describe delivery. Run is text, not a link to an execution table in this base. Release tracking is manual in the reviewed scope.
Use and boundaries
Field names below are the current product labels. * and ° are UI markers, not database constraints. A preferred single-record selection is not a global cardinality constraint either. The related guide explains operational rules.
Fields
| Field | Storage | Source, options or boundary |
|---|---|---|
| Release # | Auto number | Generated by Airtable. |
| Decision | Linked records | Change Decision |
| Released At | Date and time | Stored value. |
| Resource Version | Text | Stored value. |
| About (Content) | Linked records | Content |
| About Type | Single select | Task, Procedure, Compliance Obligation, Milestone, Incident, Metric, Tool, Organization, Person, Membership, Other |
| About Key | Text | Stored value. |
| Evidence | Text | Text reference; not a linked record. |
| Run | Text | Text reference; not a linked record. |
| Tags | Linked records | op:tags · optional labels from the Core Tags catalog; classification only. |
Example and maintenance
Illustrative example: version v2 went live on the recorded date, with a decision link and validation evidence.
Use the existing fictitious records to inspect relationships in the guide. Before changing fields, check lookups, formulas, intakes and workflow contracts. This page documents structure; a field does not prove that an integration populates it.