{"version":"2.1.248","anchor":"publishing-no-longer-refuses-when-the-model-already-saw-the-","canonical_anchor":"publishing-no-longer-refuses-when-the-model-already-saw-the-","heading":"Publishing no longer refuses when the model already saw the current version","tier":"notice","area":"Artifacts","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248\/e\/publishing-no-longer-refuses-when-the-model-already-saw-the-","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248","markdown":"### Publishing no longer refuses when the model already saw the current version\n\nPublishing no longer fails on a stale version when the model already saw the live one.\n\n**What**\n\nThe guard that blocks a publish based on a stale document version can now let the publish through. If the model already observed the live version, the publish adopts that version as its base rather than failing with a \"publish again in your next turn\" style refusal.\n\n**Details**\n\n- The guard result gained a `proceedWith` field carrying the live version, returned with no refusal text plus a replay record.\n- Telemetry labels this path `proceed_own_version`, distinguishing it from the seeded-refusal path.\n- The proceed branch also depends on two further checks in the same condition whose meaning is not resolved in this build.\n\n**Evidence**\n\n`mode: c(\"proceed_own_version\")`\n\n- Area: Artifacts\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 2\/5"}