{"version":"2.1.260","anchor":"artifact-type-instantiation-now-requires-a-title-and-store","canonical_anchor":"artifact-type-instantiation-now-requires-a-title-and-store","heading":"Artifact-type instantiation now requires a title, and store-backed types get their own fill guidance","tier":"use","area":"Artifacts","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.260\/e\/artifact-type-instantiation-now-requires-a-title-and-store","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.260","markdown":"### Artifact-type instantiation now requires a title, and store-backed types get their own fill guidance\n\nStarting an artifact from a published type now requires a title.\n\nStarting a new Artifact from a published type now requires passing a `title` (what the user called it, or a short descriptive name) alongside `type_url`, in addition to the type's own instructions being returned. The tool description was also reworded to distinguish types filled through their own data store from ones filled with page\/data files: for store-backed types, the model should call the store-write path or `run_script` rather than publish files.\n\n- Area: Artifacts\n- Names: `type_url`\n- Tier: Use it now\n- Useful: 2\/5\n- Signal: 1\/5"}