Search feature reference

List snippets: what they are and how MIRENA uses the signal

A list snippet is a search extract that uses visible list content to answer steps, types, methods, reasons, examples, checks, or ranked option queries.

A bullet list alone does not create a list snippet. MIRENA uses the observed result pattern to classify the query, check list ownership, review labels and order, and route process, list, section, or audit work.

See the MIRENA process Open the full ring

Informational reference Reference intent Five internal stages One owned handoff

Asset job Explain the list snippet pattern, distinguish ordered and unordered needs, and direct the evidence into a suitable operational workflow. The user task controls the format.

First stage Classify the list need Evidence comes before content changes.

Primary output Reference definition Every decision keeps its reason.

Search boundary No display promise Search systems decide the result presentation.

Ring position

List Snippets belongs to the search feature reference route.

Role inside the ring

Explain what the search presentation is, what publishers can observe, and which MIRENA workflow acts on the signal. The asset receives evidence from the hub and returns approved work, reference notes, or an owned next route.

When MIRENA uses the asset

Start from the visible need rather than a generic feature request.

A query shows steps, types, reasons, or checks.
A paragraph should be a list.
An existing list has vague items or no context.
A list snippet source has changed.

Internal MIRENA process

Five stages move the evidence into a controlled handoff.

The stages stay sequential. MIRENA stops when page ownership, intent, proof, technical access, current platform support, or approval is missing.

Classify the list need

MIRENA separates steps, types, reasons, checks, examples, and ranked choices.

Read the extracted list

Heading, item labels, order, truncation, and source section are observed.

Check the current asset

The system notes vague labels, missing context, false order, and overlap.

Choose an operational route

Process formatting, how to formatting, section targeting, or loss audit receives the evidence.

Monitor the pattern

The current extract is dated and kept as changing evidence.

Acceptance checks

The asset is reviewed against the user task and current platform rules.

Acceptance check

List intent

Ordered and unordered needs are separated.

Acceptance check

Item clarity

Every item names a distinct point or action.

Acceptance check

Context

The list has a clear heading and setup.

Acceptance check

Order integrity

Sequence appears only when dependency exists.

Acceptance check

Support

Complex items receive explanation outside the compact list.

Acceptance check

Expectation

No item count or search display is promised.

Failure patterns

MIRENA blocks shortcuts that create weak content or false search expectations.

Failure pattern

Bullet dump

Loose points are grouped without a shared job.

Failure pattern

False order

Numbers imply sequence where none exists.

Failure pattern

Vague labels

Items such as optimise or research hide the action.

Failure pattern

Item count myth

A fixed list length is treated as a search requirement.

Reference handoff

Use the signal to choose an operational workflow.

The informational intent does not benefit from a standalone prompt. MIRENA consumes the observation through the related planning, writing, formatting, entity, or audit workflow.

Reference intent

No standalone prompt is needed for the reference asset.

The job is to explain the search presentation accurately, record what can be observed, and send actual production or audit work into an operational MIRENA workflow.

Process Formatting master workflow How To Formatting master workflow Section Level Snippet Targeting master workflow Snippet Loss Audit master workflow

MIRENA handoff