{"version":"2.1.269","anchor":"artifact-tool-schema-gains-read-page-data-capabilitiescont","canonical_anchor":"artifact-tool-schema-gains-read-page-data-capabilitiescont","heading":"Artifact tool schema gains read_page_data, capabilities\/contract, and typed-Artifact catalog fields","tier":"soon","area":"Artifacts","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.269\/e\/artifact-tool-schema-gains-read-page-data-capabilitiescont","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.269","markdown":"### Artifact tool schema gains read_page_data, capabilities\/contract, and typed-Artifact catalog fields\n\nArtifact tool schema adds a read_page_data action plus capabilities, contract, and typed-catalog fields\n\n**What**\n\nThe schema that defines the artifact tool's parameters was rewritten and now documents several new pieces:\n\n- `read_page_data`, an action that validates a page's declared data against a named interaction schema\n\n- a reserved `preflight.js` file convention at the artifact root\n\n- `capabilities` and `contract` fields for declaring what an artifact can do at runtime\n\n- `type_query`, `type`, `type_url`, and `auto_open` fields for browsing and creating artifacts from published \"types\"\n\n- a `label` field for named publishes\n\n**Why**\n\nThis expands what an artifact can declare about itself and how it can be validated, browsed, and published, building on the previously introduced `preflight.js` hook and republish-deadline mechanism.\n\n- Area: Artifacts\n- Names: `read_page_data`\n- Tier: Nothing to try yet\n- Useful: 3\/5\n- Signal: 3\/5\n- Present in the build but not switched on"}