Preamble spends the auditory budget before the payload

What it is

A weather skill opens with “sure, based on the latest meteorological data, tomorrow’s conditions are as follows,” and four seconds later “clear, twelve.” Those four seconds occupy the best encoding seat in the sentence — the start. A preamble is structural lead-in before the payload: restating the question, announcing that a report is coming, courtesy, a source claim. It spends auditory bandwidth. It is not the two silent seconds before speech starts that may need a “hold on,” and it is not the joke a persona uses to perform.

Why it happens

In a serial position, the opening has primacy: an empty buffer loads whatever arrives first. Preamble spends that seat; the payload is pushed to the middle or the tail, where the buffer starts dropping items. Preamble also trains barge-in: people who know the lead-in pattern come in at “as follows,” and either cut the payload or get treated as a cancel. Either way, the lead-in is competing with the answer for the same timeline.

Preamble is often filed under politeness or transparency. On an auditory channel, source, stance, and restatement are extra propositions and they cost seconds. While a query is still outstanding, a floor-holder can fill the gap; once the result is in and the first sentence is still lead-in, payload exists and empty talk is being played first. If persona colour also lives in that lead-in, the costs stack — but even with no persona at all, “I have found the following results for you” is still preamble.

Studying it

The same payload in three shells: zero preamble (read the number), short preamble (sub-second “found it”), long preamble (restated question plus source plus courtesy). Dependent measures: immediate recall of payload items, time from turn start to first payload syllable, whether barge-in lands on the lead-in. Independent variables: preamble duration, whether the listener already knows this skill’s lead-in pattern.

In production, align “first syllable of payload” to system onset. If that offset grows across versions while recall falls and barge-in moves earlier, the lead-in is billing. “Did it sound polite” is the wrong primary. A lab that prints both preamble and payload as text will wash primacy out with reading.

Where it stops holding

When the query still needs a second or two, a very short floor-holder is not preamble — it fills a blank; the moment the result lands, cut to the proposition and do not extend the holder into a lead-in. Legally required spoken notices (recording notice, investment risk) must precede payload; those are compliance slots, not deletable courtesy — they should be their own sentence and skippable, not blended into “the following report.” On first use of a skill, one capability-boundary sentence can sit in front; from the second use, drop it. Listeners with hearing difficulty may drop the decoration in the lead-in, or be dragged by it until the digits are gone — both require payload first.

Applying it

• The first two syllables of system speech should already be in the payload. Restatement, source, and courtesy are off by default; a notice that must be said is its own skippable sentence.
• Floor-holders like “found it” only while the result is not in. Once it is in, do not stack “the following report is.”
• Allow barge-in on the preamble to jump to payload; do not make the lead-in an uninterruptible gate.
• How to check: measure onset-to-payload and subsequent recall on a critical skill. Cutting the preamble should drop the time and raise recall. If the preamble is only made cuter, the bandwidth bill is unchanged.

Related

• Same group: M3.11.1 Answer length should track how certain the answer is · M3.11.2 Trimmed information still needs a way back in
• Nearby: M2.01 Information Density of Prompts · M2.05 Persona · M1.08 Turns and Floor Management
• Search terms: preamble consumes auditory bandwidth · preamble · primacy in spoken output