{"version":"2.1.223","anchor":"artifact-explainer-must-justify-having-no-visual","canonical_anchor":"artifact-explainer-must-justify-having-no-visual","heading":"Artifact explainer must justify having no visual","tier":"soon","area":"Artifacts","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.223\/e\/artifact-explainer-must-justify-having-no-visual","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.223","markdown":"### Artifact explainer must justify having no visual\n\nArtifact explainers must now name a diagram type or spell out why there is no visual.\n\n**What**\n\nThe synthesis `visual` field can no longer simply be null; a missing visual has to state why. The activation state of this schema could not be resolved.\n\n**Details**\n\n- `visual` is now a discriminated union carrying a delta_diagram, flow, or before_after\n- the alternative is an explicit `{kind: \"none\", reason}` whose reason must be non-blank\n- renderers switch on `kind === \"none\"` instead of a null check\n\n**Evidence**\n\n`the no-visual reason must not be blank`\n\n- Area: Artifacts\n- Tier: Nothing to try yet\n- Useful: 2\/5\n- Signal: 2\/5\n- Present in the build but not switched on"}