I've published a template for tracking data assets through their lifecycle. It's built on the Risk Cloud platform and models assets from ingestion to retirement.
The core is a `data_asset` object with linked `process` and `system` objects. Key fields track lineage, classification, and retention dates. The main workflow automates review tasks based on asset age or changes in PII flags.
```yaml
# Example asset definition from the template
asset_schema:
- field: asset_name
type: text
required: true
- field: data_classification
type: dropdown
options: [public, internal, confidential, restricted]
- field: retention_days
type: number
- field: last_profiled
type: date
```
It integrates with external catalogs via REST API calls. The template is available for download. Looking for feedback on the review cycle logic and any gaps in the metadata coverage.