Pogee screens prompt design fix: keep AI character state and posts in sync

The essay builds its argument from a narrow starting point: a public post it opened in Pogee's Japanese UI on 2026年10月15日. In that post, Irene describes adding cheese to spicy ramen after a festival and being teased about the combination by Manager Kim, with the photo, character name, body text and input field visible on one screen. From that single view, the author asks which context a character should pull from when a user follows a post into a conversation, and whether the input field there is a comment or a path into chat — a question the screen alone cannot settle.

The library example is invented, not observed. Its purpose is to separate things that age at different speeds: a stable profile, a temporary state, an event, and relationship details such as a user's preferred name. Around that, the author lays out a short timeline — 18:00 closing, 18:10 finding a forgotten umbrella, 18:20 posting it, 18:25 starting a chat from the post — to show that a character's own knowledge and what the user has already seen are two different records. Conflating them is what produces a reply like "we talked about that" to a post the user has never opened.

The proposed answer is procedural rather than technical: a small contract when opening a chat from a post (the post ID, which parts are public, the related current state and how long it is valid), a fallback of quoting the post when the chat cannot reach it, and a rule against copying private chats into public posts. The essay closes by recommending a small start — one character, one state, one event — and a short route from post to chat, tested for missing and stale information before the world is expanded.