docs(booth): record WHEN inline ask placement earns its markup — the artifact-in-working-memory test, not just the placement rule (framing from tts-dev)

2026-09-09 14:23:19 -07:00
parent 6e0b85ba27
commit 784c555dbd
1 changed files with 10 additions and 2 deletions
@@ -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
 <div data-booth-ask="anchors"></div>          <!-- the whole ask: every question + submit -->