{"version":"2.1.242","anchor":"artifacts-carry-an-unshipped-live-paths-capability","canonical_anchor":"artifacts-carry-an-unshipped-live-paths-capability","heading":"Artifacts carry an unshipped \"live paths\" capability","tier":"soon","area":"Artifacts","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.242\/e\/artifacts-carry-an-unshipped-live-paths-capability","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.242","markdown":"### Artifacts carry an unshipped \"live paths\" capability\n\nArtifacts carry an unshipped live-paths concept that only appears when three conditions hold.\n\n**What**\n\nPublishing an Artifact gains a live-paths concept throughout: publish results carry live paths and a born-live marker, share status stores the paths and when they were issued, and the publish request sends a live-files flag that is also passed to publish telemetry. The visible part is extra top-level fields spliced into the Artifact tool's input schema, and that only happens when three conditions all hold.\n\n**Details**\n\n- Schema fields appear only when the live-edit gate is open, the files capability is enabled, and a live-paths predicate returns true.\n- That predicate lives on a module loaded lazily from a separate chunk, absent from the main bundle, so what it defaults to is decided outside this code.\n- The combined boolean is also stored as a latch on the durable artifact state. It is written at exactly one place and read nowhere in the build, so it currently affects nothing.\n- None of these fields exist in 2.1.241.\n\n**Evidence**\n\n`livePathsGateLatch`\n\n- Area: Artifacts\n- Tier: Nothing to try yet\n- Useful: 2\/5\n- Signal: 4\/5\n- Present in the build but not switched on"}