From 6d36119bc5ba6b929fa1778a6165adfde4486f26 Mon Sep 17 00:00:00 2001 From: Vuong Hoang Date: Wed, 9 Sep 2026 14:23:19 -0700 Subject: [PATCH] =?UTF-8?q?docs(booth):=20record=20WHEN=20inline=20ask=20p?= =?UTF-8?q?lacement=20earns=20its=20markup=20=E2=80=94=20the=20artifact-in?= =?UTF-8?q?-working-memory=20test,=20not=20just=20the=20placement=20rule?= =?UTF-8?q?=20(framing=20from=20tts-dev)?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit --- README.md | 12 ++++++++++-- 1 file changed, 10 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index dfade93..be610b6 100644 --- a/README.md +++ b/README.md @@ -177,8 +177,16 @@ above the gallery, styled like the rest of the Booth. Nothing to do. **A booth serving its own `index.html`**: that page is returned verbatim, so the Booth substitutes **placeholders in your markup** rather than rendering a panel above a gallery that does not exist. The question then sits with the artifact it -is about, which is the whole point (operator ruling 2026-09-09: *"the asks should -be inline with the artifacts, not on a separate page"*). +is about (operator ruling 2026-09-09: *"the asks should be inline with the +artifacts, not on a separate page"*). + +**When inline is worth the markup, and when it is not.** The test is whether the +artifact can be held in the head while the form is on screen. Two short images +side by side — no, the appended form is fine. Twenty audio clips, five per voice +across four voices — yes: on a separate page the operator is choosing from +*memory of the audio*, not from the audio, and by the fourth voice that memory is +gone. That is the case this mechanism exists for (framing owed to tts-dev, +2026-09-09, from the `redo-anchors` audition). ```html