{"version":"2.1.235","anchor":"session-transcripts-now-record-an-atis-latch-entry","canonical_anchor":"session-transcripts-now-record-an-atis-latch-entry","heading":"Session transcripts now record an \"atis-latch\" entry","tier":"internal","area":"ATIS Latch","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.235\/e\/session-transcripts-now-record-an-atis-latch-entry","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.235","markdown":"### Session transcripts now record an \"atis-latch\" entry\n\nSession transcripts now record an \"atis-latch\" entry when the atis value changes\n\n**Unclear.** What the atis latch value represents or controls is not stated.\n\nThe transcript writer appends a `{ type: \"atis-latch\", atis, sessionId }` entry once per session file whenever the conversation's atis latch value changes, and the fork\/relocate path re-emits it in the new transcript. The transcript reader only accepts such an entry when its sessionId matches and its value is printable ASCII, and session state now carries `atisLatch` alongside the rest of the session data.\n\n- Area: ATIS Latch\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 3\/5\n- Present in the build but not switched on"}