{"version":"2.1.269","anchor":"new-guidance-string-for-artifact-metadata-content","canonical_anchor":"new-guidance-string-for-artifact-metadata-content","heading":"New guidance string for artifact metadata content","tier":"internal","area":"Artifacts","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.269\/e\/new-guidance-string-for-artifact-metadata-content","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.269","markdown":"### New guidance string for artifact metadata content\n\nA new internal checklist spells out what artifact metadata should document\n\n**What**\n\nA new internal guidance string lists what documentation for an artifact (a generated file or output) should cover:\n\n- purpose\n\n- key decisions made while producing it\n\n- the repo, branch, and commit it came from\n\n- data sources used\n\n- how fresh the snapshot of data is\n\n- known limitations and suggested next steps\n\n**Why**\n\nThis is guidance text used internally when generating or describing artifacts, so it helps ensure the documentation attached to an artifact is consistently thorough.\n\n- Area: Artifacts\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}