{"version":"2.1.238","anchor":"artifact-live-rooms-are-fully-built-and-cannot-run-in-this-b","canonical_anchor":"artifact-live-rooms-are-fully-built-and-cannot-run-in-this-b","heading":"Artifact live rooms are fully built and cannot run in this build","tier":"soon","area":"Artifacts","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.238\/e\/artifact-live-rooms-are-fully-built-and-cannot-run-in-this-b","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.238","markdown":"### Artifact live rooms are fully built and cannot run in this build\n\nA complete live broadcast feature for artifacts is built into this version and nothing can switch it on.\n\n**What**\n\nA complete broadcast-channel feature for artifacts ships in the code, including a `room_send` action, its approval copy, validation, result rendering, a topic\/data argument pair, a `rooms` section in artifact `status` and join-on-publish machinery. None of it is reachable, and no flag or environment variable can turn it on.\n\n**Details**\n\n- Every entry point goes through a module handle that is set to null and never assigned anywhere in the bundle, so the enabled check is always false, `topic` never enters the frozen schema, `status` never emits a `rooms` section, and the accessor for the implementation throws.\n- Same null-placeholder pattern used for the live-edit module. Turning it on requires a different build.\n\n**Evidence**\n\n`artifact rooms are not compiled into this build`\n\n- Area: Artifacts\n- Tier: Nothing to try yet\n- Useful: 2\/5\n- Signal: 5\/5\n- Present in the build but not switched on"}