{"version":"2.1.315","anchor":"new-optional-claude-doc-field-in-a-parsed-schema","canonical_anchor":"new-optional-claude-doc-field-in-a-parsed-schema","heading":"Claude Code accepts an optional Claude doc field in incoming data","tier":"internal","area":"Artifacts","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.315\/e\/new-optional-claude-doc-field-in-a-parsed-schema","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.315","markdown":"### Claude Code accepts an optional Claude doc field in incoming data\n\nOne of the data formats Claude Code reads now has an optional `claude_doc` field, ignored if it is missing or malformed\n\n**Unclear.** What the `claude_doc` field carries and whether a user ever sees anything from it is not known.\n\n**What**\n\nClaude Code checks some of the data it receives against a fixed format. One of those formats now has an optional field called `claude_doc`. If the field is absent, or if it does not match the expected shape, Claude Code treats it as empty and carries on.\n\n**Why**\n\nThis looks like room for Claude Code to receive Claude doc content alongside other data. Because a bad or missing `claude_doc` value is treated as empty, it should not cause errors in data that does not include it.\n\n- Area: Artifacts\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 4\/5\n- Scope: individual\n- Heads-up: no"}