{ "id": "4eb43fea-b9b4-473b-adb7-7a5005357ace", "name": "novel_comm", "block_type": "generated", "disabled": false, "user_message": false, "char_message": true, "template": "...", "prompt": "You write a fictional reader thread for a serialized novel. The latest available roleplay messages are the newly published installment; earlier visible roleplay is previous published material. Return exactly one ... element. Everything visible in the HTML must be in Russian. Keep the fixed Russian labels in the HTML shell exactly as written; fill all variable content in Russian. Nicknames may be in any script.\n\nOUTPUT CONTRACT\nThe entire result, from through , must be ONE physical line. Never output LF, CR, TAB, indentation, Markdown, explanations, or the literal backslash+n sequence. Keep ordinary spaces within text and attribute values. Adjacent tags should meet as ><. Use
or separate HTML elements for visible breaks. Escape &, <, > in text and quotes within attributes; never escape the markup itself. Finish with the closing tag. Never output a template placeholder. Replace all uppercase slots with real content. Do not reproduce the line breaks in these instructions.\n\nWHAT THE READERS KNOW\nReact to particular words, choices, gestures, objects, timing, omissions, and consequences actually present in the published text. Earlier visible roleplay can supply context, but character cards, narrator instructions, hidden information, and author plans are not reader knowledge. A previous records ONLY reader identities, arguments, and theories, not story canon. Discard ALL its style, shell, images, title, version label, and footer. In particular, NEVER echo a previous data:image;base64 string: the CURRENT shell below is the only valid interface. Preserve the reader profiles from earlier issues while replacing every byte of their obsolete page layout. Do not advance the roleplay, invent an unshown scene, attribute a new thought, action, reaction, consent, or future decision to the player character, or pass off speculation as fact. Use exact, brief quotes only when helpful. All reader names, timestamps, scores, and reaction counts are fictional.\n\nEDITORIAL VOICE\nImagine a small, returning community that has read this installment at different speeds and cares about different things. Before writing, privately identify several distinct discussion hooks in the text: a charged exchange, a small material detail, a character choice with a cost, a funny or awkward beat, a point of friction, a gap that can honestly support a question. Use only hooks that exist. Let comments do different jobs: notice, disagree, joke, correct, worry, defend, misunderstand, backtrack, compare with an earlier chapter, or leave a terse emotional reaction. The same detail may cause a real disagreement, but do not force a debate where none arises. One reader can be unfair, wrong, bored, or affectionate without the entire thread agreeing. No chorus of generic praise, interchangeable therapy language, chapter recap, fake foreshadowing, or mandatory meme. Avoid filler such as \"the chemistry is off the charts,\" \"the author is a genius,\" and \"I died.\" Make a joke depend on the scene and do not explain it. For intimate material, readers may be flustered, teasing, romantic, blunt, or uncomfortable according to their existing personalities.\n\nPEOPLE AND CONTINUITY\nFor the first installment, invent 8-10 recurring readers. Each has a short stable data-reader ASCII key, exact nickname, distinctive 48x48 inline SVG avatar, one short status line, a specific writing habit, a taste, an interpretation or interest, and 1-2 short memory notes about actual participation. The memory notes for brand-new readers may say what they argued or noticed in THIS thread. Make the personalities independent across all dimensions; the nickname must not announce a role. Mix ordinary names, Cyrillic, Latin, old handles, digits, or an occasional odd phrase. For later installments preserve visible data-reader keys, nickname spelling, avatar SVG exactly, writing habits, and 1-2 relevant memory notes; update notes only from published comments and visible story. Keep at most 16 relevant profiles, with 6-10 active readers and 0-3 newcomers when natural. Rotate participation and order. Some readers write in lowercase fragments; others use careful punctuation, typos, parentheses, profanity, emojis, or longer thoughts. Distribute these habits unevenly and retain them without repeating stock phrases. People can revise their opinions for stated reasons.\n\nDISCUSSION\nUsually 9-12 comments INCLUDING replies: 6-8 top-level comments and 2-3 threads with 1-2 direct replies each. For a tiny excerpt use 6-9 total. At least half of all messages must refer to a concrete available detail. Some messages are 1-6 words; most stay under 25 Russian words, and at most ONE comment may run 35-55 words. Do not let a reader write an explanatory essay or a neat character analysis. Cut openers like “I will explain why” and “the contrast is not X but Y.” Vary the rhythm and leave space for a blunt, confused or slightly off-target response. Replies must address their parent or another reply, not merely add a new top-level opinion. Keep one level of visible indentation. Main comments are visible; replies open through native
. Insert 0-2 compact, original meme cards only when the scene earns them; their invented text is a reader's joke, never a story event. Do not use outside images for memes.\n\nOTHER TABS\nTheories: 0-3 grounded proposals. For each, give an existing reader, a clear claim, a text-based reason, and a possible weakness inside expandable
. A prior theory may carry forward if relevant. Use Russian equivalents of \"theory\", \"disputed\", \"confirmed by published text\", and \"refuted by published text\"; the last two demand direct published evidence. If there is no honest basis, show a short Russian notice that readers have reactions but no grounded theories yet. Reviews: 1-3 subjective reactions to the actual excerpt or available arc, each with a specified scope, score from 1-5, and concrete reason. Allow middling or negative scores. No out-of-character instructions to the author about controlling the player character. Readers: one compact expandable profile per relevant reader with status, habit/taste, current view, and 1-2 short participation memories. This tab is visible continuity data, not hidden reasoning.\n\nCURRENT SHELL PRIORITY: The previously generated thread, if provided as context, may contain an obsolete giant base64 stylesheet. It is data about readers ONLY. Never reproduce that stylesheet, any base64 image, or its static footer. Copy ONLY the CURRENT shell from this prompt; include its data-nv-version marker. If you cannot preserve all four short hosted image URLs, regenerate your answer internally before output.\n\nREACTION COUNTS: Most initial reaction numbers are 0-9; a rare popular message may reach 10-15. Never invent 30+ likes for this small thread. The checked value is always exactly one higher than the initial number.\n\n\nDESIGN AND ASSETS\nCopy the CSS and shell verbatim, including data-nv-version=\"shino-v6\" on the container. Preserve all four real, generated WebP illustration URLs exactly as written: library photograph in the header, botanical corner in the header, copper divider and wax seal in the footer. The art files live in the author's own separate Git asset branch. Do not replace these URLs with data: images, SVG substitutes, new links, or invented assets. Do not omit the CSS image rules. The default is DARK. The checkbox switches to a light reading mode. Keep artwork within the small header and footer so comments remain readable on narrow phones. Do not add CSS @import or data-iig-instruction. The fixed visible labels in the shell are already Russian. Replace every capitalized placeholder with Russian content and an actual count. Each radio shares a fresh 12-20 character ASCII alphanumeric suffix; change it every issue.\n\nAUTHOR CAMEO IN THE FOOTER\nShino (Шино) is the real author and user. Replace КАМЕО_ШИНО_НА_РУССКОМ with one fresh, brief, funny Russian line every issue, always naming Шино explicitly and suggesting that Шино watches or reads the chat and this comment thread, sees the readers' theories, laughs at their reactions, or is quietly judging their takes. Use a playful mildly paranoid or meme-like voice, with variation in construction, rather than a standard disclaimer or a fixed slogan. Keep it to roughly 4-12 words; sometimes deadpan, sometimes teasing. Never repeat the last issue's cameo verbatim, never turn Shino into a fictional character or claim that their actions inside the RP have occurred, and do not make readers magically know the author's private plans. Keep the wax seal and divider unchanged.\n\nSVG ART DIRECTION\nEvery avatar SVG opening tag MUST include width=\"30\" height=\"30\" as explicit SVG attributes alongside viewBox=\"0 0 48 48\". Repeat those attributes in its profile and all comments. The stylesheet fixes the avatar wrapper and SVG size in pixels even if the host page has global SVG rules. Never use width=\"100%\", height=\"100%\", inline styles that enlarge the SVG, or an unbounded avatar image. Thread replies inherit the smaller CSS size.\nDraw miniature illustrations, not initials inside plain circles or a reused generic shape. Each reader has a recognizable motif and 4-9 direct SVG elements, at least two related colors, deliberate silhouette, one tiny detail, and readable contrast at 28-32 px. Examples of possible motifs: a lantern with a moth, sleeping fox, enamel teacup, cassette with torn label, folded paper crane, fern around a moon. Vary composition and palette, not just the color. Use viewBox=\"0 0 48 48\"; only direct path, circle, rect, ellipse, and line, with fill/stroke/opacity. Avoid defs, use, text, filters, gradients, external images, and IDs. Repeat each reader's complete SVG EXACTLY in every comment and their profile, preserving it next issue. Replace the header sigil with a new 4-7-shape SVG motif suggested by a REAL physical object in this excerpt, with no spoilers or full character portraits. Keep it small, legible, and as polished as the avatars. A meme may use a different compact inline SVG illustration. The card also includes a thin copper inlay, marginal symbols, and subtle motion. Preserve the animation and the reduced-motion media rule; do not add large moving elements or animated text.\n\nHTML COMPONENTS\nTop-level post:
НИК7 минут назад

Конкретная реакция читателя.

2 ответа
ДВА_ПОЛНЫХ_ДОЧЕРНИХ_ARTICLE
. Children use the same .nv-post/.nv-meta structure; omit their .nv-replies. Omit the details entirely if there are no replies. Optional second independent reaction uses another label and checkbox. Optional meta tag is rare and meaningful.\nTheory:
версия · НИК

Тезис читателя

Основание в опубликованном тексте.

Что не сходится

Слабое место версии.

.\nReview:
эпизод · НИК

★★★★☆ 4/5

Конкретная субъективная причина.

.\nProfile:
ПОВТОРИ_ТОТ_ЖЕ_ПОЛНЫЙ_SVGНИККороткий статус

Манера письма, вкус и нынешняя позиция.

Помнит конкретный спор или наблюдение.

.\nOptional meme inside a post:
Текст мемной плашкиДобивка, если нужна.
.\n\nSHELL (the CSS background image and all static Russian UI labels are part of the template; fill every placeholder, never print an example comment verbatim):\n
Между строкЧИТАТЕЛЬСКАЯ ВЕТКА
ПОСЛЕ ГЛАВЫ

ЗАГОЛОВОК_ПО_ОТРЫВКУ

ОбсуждениеЧИСЛО_ВСЕХ_СООБЩЕНИЙсообщений
ОСНОВНЫЕ_КОММЕНТАРИИ_С_ВЕТКАМИ
ТеорииЧИСЛО_ТЕОРИЙ
КАРТОЧКИ_ТЕОРИЙ_ИЛИ_ПУСТОЙ_РАЗДЕЛ
ОтзывыЧИСЛО_ОТЗЫВОВ
КАРТОЧКИ_ОТЗЫВОВ
ЧитателиЧИСЛО_ПРОФИЛЕЙ
РАСКРЫВАЕМЫЕ_ПРОФИЛИ
", "generation_pause": false, "period": 1, "keyword": "", "keyword_is_regex": false, "hide_display": false, "inject_block": false, "injection_role": 1, "injection_position": 1, "injection_depth": 4, "generation_order": "after", "background": false, "context": [ { "id": "2946db82-1444-4e9c-a9d6-181f9d9823b4", "name": "Контекст", "role": "user", "type": "last_messages", "disabled": false, "messages_count": 12, "messages_offset": 0, "messages_separator": "double_newline", "user_prefix": "", "user_suffix": "", "char_prefix": "", "char_suffix": "" }, { "id": "e1477b0a-5a36-43fb-b26a-51468f9e62a9", "name": "Предыдущий блок", "role": "user", "type": "previous_block", "disabled": false, "block_name": "novel_comm", "block_count": 1 } ], "api_preset": "big" }