{"version":"2.1.271","anchor":"artifact-type-description-telemetry-gains-a-declaration","canonical_anchor":"artifact-type-description-telemetry-gains-a-declaration","heading":"Artifact type description telemetry gains a 'declaration' \/ malformed-capabilities distinction","tier":"internal","area":"Artifacts","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.271\/e\/artifact-type-description-telemetry-gains-a-declaration","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.271","markdown":"### Artifact type description telemetry gains a 'declaration' \/ malformed-capabilities distinction\n\nArtifact-type telemetry now distinguishes a proper capabilities declaration from a missing or malformed one\n\n**What**\n\nWhen Claude Code describes an Artifact type internally, the telemetry it records now classifies the type's `capabilities` value into one of three states: not present, a valid capabilities object, or malformed. A new `declaration` field is included in the recorded detail when it's defined.\n\n**Why**\n\nThis should make it easier to notice and diagnose Artifact types with broken or malformed capability declarations, rather than lumping them in with types that simply have none.\n\n- Area: Artifacts\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}