Asset Metadata

The filename tells you what the asset is. The metadata tells you everything else: when it was generated, what prompt produced it, what style version was applied, what quality scores it received, who approved it, and where it is currently deployed.

The metadata JSON lives alongside every asset in the library. Required fields: generated_at (ISO timestamp), prompt (the full generation prompt), style_version (which style specification was used), quality_scores (dimensional adherence, cross-output consistency, intent fidelity), approved_by (critic agent or human reviewer), deployed_to (array of locations where this asset is currently in use — blog posts, landing pages, social feeds).

The deployed_to field is the most operationally critical. When a style version changes and old assets need replacing, the deployed_to array tells you exactly which pages, posts, and platforms will be affected. Without it, finding every instance of an outdated asset requires a manual audit across every touchpoint — a task that scales quadratically with the size of your content library.

{
  "generated_at": "2026-02-22T14:23:17Z",
  "style_version": "v2.0.0",
  "prompt": "Dark background (#000000) with neon cyan ...",
  "quality_scores": {
    "dimensional_adherence": 8.7,
    "cross_output_consistency": 0.91,
    "intent_fidelity": 9.2
  },
  "approved_by": "RENDER-critic",
  "deployed_to": [
    "/courses/agent-teams",
    "/signal/clawmander/orchestration-report"
  ]
}