{"version":"2.1.248","anchor":"reads-can-now-say-the-working-copy-is-live-and-verified","canonical_anchor":"reads-can-now-say-the-working-copy-is-live-and-verified","heading":"Reads can now say the working copy is live and verified","tier":"internal","area":"Artifacts","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248\/e\/reads-can-now-say-the-working-copy-is-live-and-verified","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248","markdown":"### Reads can now say the working copy is live and verified\n\nReads can now report a document as live and verified with its sequence number.\n\n**What**\n\nFile listings can mark individual files as live, and a read of one reports `live`, `live_verified` when the fetched document was checked, and its sequence number. A verified live read is no longer flagged `as_served`, so it is no longer reported as differing from the published bytes.\n\n**Details**\n\n- The read telemetry event gained a `doc_verified` field.\n- Whether a file is marked live or verified is decided by the server, not by anything set in this build.\n\n**Evidence**\n\n`...(He.docVerified && { live_verified: !0 }),`\n\n- Area: Artifacts\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 3\/5"}