{"version":"2.1.242","anchor":"artifact-document-paths-capped-at-15-path-segments-down-from","canonical_anchor":"artifact-document-paths-capped-at-15-path-segments-down-from","heading":"Artifact document paths capped at 15 path segments, down from 31","tier":"notice","area":"Artifacts","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.242\/e\/artifact-document-paths-capped-at-15-path-segments-down-from","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.242","markdown":"### Artifact document paths capped at 15 path segments, down from 31\n\nArtifact collection paths are capped at 15 segments, down from 31, so deeper ones are rejected.\n\n**What**\n\nEvery check and description of artifact document paths now allows at most 15 slash-separated segments in a collection path. Collections nested deeper than that, which were previously accepted up to 31, are rejected.\n\n**Details**\n\n- each segment may use letters, digits and `_ - . ~ : @ +`; `.` and `..` stay reserved; the document id is still a single segment\n- the note listing saved documents now tells Claude that a `~` in a document id is written as `@` on disk\n\n**Evidence**\n\n`'collection must be a path of 1-15 \"\/\"-separated segments and doc_id one segment (letters, digits, _ - . ~ : @ + per segment; \".\" and \"..\" reserved)'`\n\n- Area: Artifacts\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5"}