{"version":"2.1.248","anchor":"joining-an-artifact-s-live-room-after-publishing-with-named-","canonical_anchor":"joining-an-artifact-s-live-room-after-publishing-with-named-","heading":"Joining an artifact's live room after publishing, with named skip reasons","tier":"soon","area":"Artifacts","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248\/e\/joining-an-artifact-s-live-room-after-publishing-with-named-","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248","markdown":"### Joining an artifact's live room after publishing, with named skip reasons\n\nPublishing an artifact can join its shared room, or report why it didn't.\n\n**What**\n\nOne routine now decides whether your session joins an artifact's shared room after you publish it, reporting a reason such as `not_declared` in the publish output when it does not.\n\n**Details**\n\n- It reads the artifact's declared capabilities, then checks the consent markers recorded when the artifact was created.\n- Returns immediately unless the room module is present and the room capability check passes; that module is absent here.\n\n**Evidence**\n\n`not_declared`\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"}