Under the hood
A new internal checklist spells out what artifact metadata should document
What
A new internal guidance string lists what documentation for an artifact (a generated file or output) should cover:
- purpose
- key decisions made while producing it
- the repo, branch, and commit it came from
- data sources used
- how fresh the snapshot of data is
- known limitations and suggested next steps
Why
This is guidance text used internally when generating or describing artifacts, so it helps ensure the documentation attached to an artifact is consistently thorough.