{"version":"2.1.224","anchor":"artifact-tool-gains-document-store-read-and-write","canonical_anchor":"artifact-tool-gains-document-store-read-and-write","heading":"Artifact tool gains document-store read and write","tier":"soon","area":"Artifacts","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.224\/e\/artifact-tool-gains-document-store-read-and-write","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.224","markdown":"### Artifact tool gains document-store read and write\n\nArtifacts get document read and write operations with separate remembered consent for each.\n\n**What**\n\nNew read and write operations address documents by page address, collection path and document id, with errors for a bad address, an over-long composed path and a missing document id. Consent is remembered separately for reads and writes, and again separately for approvals given by a person in plan mode.\n\n**Details**\n\n- The stored consent covers write approval, human write approval, and per-address lists for read consent and human read consent.\n- Whether these operations are offered unconditionally or behind a flag is decided by the tool's schema, which is not resolved in this build.\n\n**Evidence**\n\n`doc_id is required for a get`\n\n- Area: Artifacts\n- Tier: Nothing to try yet\n- Useful: 3\/5\n- Signal: 4\/5\n- Present in the build but not switched on"}