# Choose a spread for the job its content must do

Start at [LLM_ENTRYPOINT.md](LLM_ENTRYPOINT.md) for task routing, selected-state paths, variable counts and narrative assembly. The four new case options use `options[].files.html`; do not infer their parent HTML route. Counts describe checked instances, not universal limits.

## Sanitised teaching cases — implementation policy

Read [reuse-policy.md](reuse-policy.md) before adapting confidential-source material. Reusable cases preserve the argument through a reviewed fictional reconstruction; original text, pixels and identity bridges remain outside the reuse library, including a private repository. General before/after rules must remain independent of the teaching scenario. Existing layout-review status is not a privacy or target-export certification.

## Local meaning and reuse review - 13 October 2026

The additive `semantic.narrative_profile` explains the central point, communication job,
reading path, intended audience value, actual slot roles, adaptation limits, fictional
worked example and narrative fit. The selected variation owns its own profile. The
gallery shows this under **Details & source → Meaning & narrative** and includes the same
content in **Use with AI**. Search also includes the communication jobs and appropriate uses.

`semantic-coverage.json` is the current review record for this deeper pass. **Reviewed**
means the authored layout contract and adaptation example were inspected. It does not
mean the original author confirmed the purpose, the example happened, the content was
validated against a proposal corpus, or persuasion was measured. **Provisional** identifies
a remaining substantive mapping or interpretation limit. **Unreviewed** means no profile
has been completed for this pass. Previous Impeccable checks cover different work and
cannot substitute for these statuses.

Each profile keeps observations from inspected material separate from interpretations
for reuse and from facts that remain unverified. A source may establish arrangement while
leaving wording or purpose unknown, particularly where the retained capture is blurred.
Examples are explicitly fictional teaching scenarios. Use their reasoning, replace their
content, and supply real sources and qualifications before presenting them as a case.

Meaningful variations have a `variation_relationship` of `different-job`; cosmetic or
behavioural alternatives are marked `same-job` and still explain their own active slots
and reading conditions. A shared silhouette does not make a question interface, a
subscription offer and a proof surface interchangeable.

Corrected matching records retain `previous_required_slots` and a `contract_correction`
receipt where the old metadata disagreed with the selected markup. A semantic unit can
be a group whose visible members outnumber its `data-slot` annotations. Read its group
count and explicit mapping together; never assume one annotation means one content item.

The meaning-and-reuse baseline was released as Sites v6 on 13 October 2026. Subsequent local policy additions require their own release; this statement does not certify unreleased changes.

A spread has two connected layers: its visual arrangement and its semantic purpose. The arrangement gives the reader a way to understand a relationship. A comparison has aligned criteria; a message house has a governing message and supporting proof; a roadmap has time and overlapping workstreams. Filling the right boxes with unrelated content loses the reason for choosing the layout.

## Read the semantic profile before adapting

Every `spread.json` includes a `semantic` object. Read it alongside the actual markup, content slots, selected variation and source reference.

| Field | What it tells you |
|---|---|
| audience_question | The question this page answers for its reader |
| intent | What the reader should understand, believe or decide afterward |
| reasoning_relation | The relationship the arrangement expresses |
| message_pattern | A phrasing structure with explicit placeholders, not ready-made factual claims |
| required_content | Inputs and support that must exist before the layout is a sensible choice |
| narrative_positions | Places this page can earn within a story, rather than a compulsory deck order |
| requires_before | Understanding the preceding material must establish |
| enables_after | The explanation or decision this page prepares |
| slot_roles | The rhetorical jobs of the layout’s real content slots |
| avoid_when | Situations in which this arrangement would mislead or weaken the argument |
| provenance | Whether the guidance is a layout-contract interpretation or has reviewed source examples |
| variations | Option-specific overrides when a variation changes the reader's task or reasoning relationship |

The initial semantic profiles are model-authored interpretations of the existing layout and slot contracts. Their inclusion was approved by Nic on 10 October 2026. They are not frequency findings from the proposal archive or independent validation of sample facts. Source-based pattern evidence is recorded separately and added only after review.

## Work from the reader’s question to the layout

1. Name the audience, its current understanding and the question this page must answer.
2. State the point and identify its support. If the support is missing, record the gap before choosing a visually persuasive treatment.
3. Identify the relationship: comparison, cause, hierarchy, sequence, synthesis, evidence, choice or another specific relation.
4. Match both the semantic profile and the actual arrangement. Prefer an honest fit over a superficial resemblance.
5. Map content to slot roles. Keep the claim, evidence, qualification and implication distinct where they have different jobs.
6. Check the preceding and following pages. Explain the logical bridge in each direction.
7. Review meaning and appearance separately. Correct placement does not establish correct reasoning.

A page can serve several narrative roles. Its title and content determine which role it performs in this use. A source proposal’s exact sequence is an example, not a mandatory template for another client.

## Three examples

**S25 Plan on a page** answers how an objective, strategy, audience groups and activities fit together. The matrix requires real mappings. It usually follows the diagnosis and strategic choice, then prepares the detailed workstreams, schedule or measures. An unrelated task inventory does not become a strategy because it fits the grid.

**S57 Comparison columns** answers which option fits the reader’s needs and what tradeoffs the choice creates. Use the same criteria and units in every column; put genuine shared inclusions in the common band. Explain the decision criteria before the comparison, then specify the selected scope or ask for a decision. Colour can indicate a supported recommendation; it cannot supply the reason.

**S76 Message house** answers what to say, to whom and why the audience should believe it. The roof, beams, pillars and proof slots encode a hierarchy. Establish audience needs and positioning first, then translate the narrative into story angles or channel examples. A collection of repetitive slogans does not constitute supporting pillars.

## Preserve meaning when adapting a variation

Read the selected option’s markup and actual slot count. An option may change the amount of content or its reading order. If it changes the reasoning relationship, add option-specific semantic guidance rather than inheriting the default silently.

Merge `semantic.variations[selectedOption]` over the base semantic profile. The gallery applies this rule to its details and AI prompt. For example, S92’s links option is navigation, while its default is a complementary explanation; S91’s specimen option demonstrates typography. A new variation must be reviewed on its own content contract.

Motion also carries meaning. A reveal order can express a sequence or comparison. Preserve a source build only when its order still supports the replacement content. Essential meaning must remain available in the complete static and reduced-motion states.

## Evidence and phrasing rules

- Treat sample text, values, client names, logos and images as placeholders unless the new brief supplies and authorizes them.
- Preserve exact quotations and their attribution. Never turn a historical proposal assertion into a verified current fact.
- Keep units, dates, denominators and evaluation criteria visible where they affect interpretation.
- Use a phrasing pattern to organize real content. Do not invent claims, proof, recommendations or causal relationships to fill a slot.
- If a layout requires a relation the content does not contain, choose another layout or identify the missing input.
- Utility layouts such as file intake have semantic contracts too: state what the interface actually does. They need not be forced into a proposal section.

## Recommendation format for another assistant

For each recommended spread, give its code, the audience question it answers, the reasoning relationship it preserves, the input that supports the point, any missing material, and the bridge to the surrounding pages. Show the relevant preview. Ask for a layout choice only when the brief leaves a consequential choice open.

Keep confidential proposal examples and original source screenshots in their private catalogue. General semantic guidance may travel with Spreads; access to Spreads does not grant access to the source-deck archive.