{"version":"2.1.248","anchor":"local-artifact-replicas-are-wired-up-but-can-never-serve-a-r","canonical_anchor":"local-artifact-replicas-are-wired-up-but-can-never-serve-a-r","heading":"Local artifact replicas are wired up but can never serve a read","tier":"soon","area":"Artifacts","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248\/e\/local-artifact-replicas-are-wired-up-but-can-never-serve-a-r","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248","markdown":"### Local artifact replicas are wired up but can never serve a read\n\nArtifact reads still all go to the server; the local-copy path exists but nothing fills it.\n\n**What**\n\nArtifact sessions gained a block of state for serving artifact reads from a local copy instead of fetching them, including a renderer, a transport and an engine slot. Nothing in this build ever fills those slots, so the optional call always short-circuits and every artifact read still goes to the server. No flag controls this; the code that would populate it is not shipped.\n\n**Details**\n\n- The state block holds replicas, unavailable, opening, transport, engine, renderLevel and headMoved.\n- The read path calls the renderer with the artifact slug and head sequence; on a hit it would log a line about serving from the local replica and return HTML locally.\n- The only writes present are the initialiser and three calls that clear the block.\n\n**Evidence**\n\n`read served from the local replica at seq`\n\n- Area: Artifacts\n- Tier: Nothing to try yet\n- Useful: 1\/5\n- Signal: 4\/5\n- Present in the build but not switched on"}