# Max LVL experience system

Design experiences that help one person reach a wanted outcome. Use `BRAND-STRATEGY.md` for positioning, creative direction and motion; use `../brand.tokens.json` for the broader brand/marketing profile and `../ui.tokens.json` for the live application profile. The concrete Builder shell and workspace direction is in `CLAUDE-HANDOFF.md`.

## 1. Begin with the person using the experience

Identify who is here, what is happening in their life, what they want to change, and what they are ready to do. The desired change might be a more dependable business, a hot shower, confidence about a decision, or an evening with friends that goes well. Its scale does not determine its emotional value.

| Context | The person at the center | The experience helps them |
| --- | --- | --- |
| Max LVL's own marketing | One business owner considering help | Understand whether the work can help their business and life, believe the mechanism, and take a useful next step. |
| Marketing for a client | One end customer with a particular situation | Recognize the relevance of the offer, understand their options, and act with appropriate confidence. |
| Internal software | The person operating the business or campaign | See the real state, complete work, make informed decisions, and recover from problems. |
| Recipient preview | The person who will receive the page, message or document | Understand the content in their own context, without the operator's internal terminology. |

The founder's filmmaking sensibility is a source of craft: attention to people, meaningful details, pacing, image and emotion. The customer does not need to see themselves as a filmmaker, storyteller or creator. Express the change they want in terms they recognize.

VVV and VALUE are inputs for understanding the audience, tension, desired result and reasons to believe. They are not required section names, visible labels, headline formulas or a compulsory sequence. Let their implications shape the work without displaying the framework.

Readiness changes the design. An urgent homeowner needs a usable phone action and service information immediately. A researcher may need choices, process, evidence and cost context. A returning operator needs the latest task state. Do not replay a pain story every time someone opens their workspace.

## 2. Give expression room without confusing identity

**Expressive** allows bold art direction, unusual scale, rich imagery, animation and a memorable point of view. **Everyday** makes repeated work comfortable through clear hierarchy and responsive behavior. **Editorial** supports consideration and learning through reading rhythm, explanation, images and thoughtful detail. They are loose creative permissions; a project may combine them or develop another useful register.

Material follows the subject: energetic, tactile, precise, bright, intimate, sculptural or spacious. Each subject earns its own treatment. A forceful red composition and a calm reading page can belong to the same brand.

Max LVL's own environment uses the blue-steel foundation and strong red identity, with deep cobalt and amethyst alongside brighter, saturated Legendary amber for expression as defined in the strategy and tokens. Coordinated shadows and highlights support depth. Rare and Epic retain slightly muted bodies; Legendary brings a richer golden-orange light to localized materials and art details. Functional controls use semantic roles. Art colors do not automatically become status colors or accessible text combinations.

Tactile cinematic collage is available alongside sculptural ribbon art: human presence, physical textures, painted gestures, overlap, light and depth can support a particular story. A doorway, circle or orbit in one specimen does not establish a required motif or fixed brand symbolism. For this collage direction, use amber chiefly in localized material and light; avoid making a broad amber CTA or form background the default. Other expressive treatments remain open to deliberate exploration.

Client-facing artifacts retain the client's approved identity. The Max LVL application frame can surround a client preview; it must not recolor the preview or replace the client's language with agency language. A client website, email, PDF and campaign should look like that client's work unless the task explicitly includes developing their identity.

## 3. Information architecture and layout models

Organize a product around recognizable objects: **account → client or project → campaign or work area → item**. Adapt this hierarchy to the actual product. Use ordinary labels such as Projects, Pages, Campaigns, Inquiries, Connections, Reports and Settings. Name an action by what it does: Review campaign, Reply to inquiry, Save draft, Export report.

Distinguish global navigation, project navigation and item controls. Use breadcrumbs for depth, tabs for peer views, and filters for collections. Search results show title, type and location; returning preserves the query and filters.

Choose a layout that fits the work:

- **Overview:** current status, exceptions needing attention, recent work and a useful next action. Avoid filling it with decorative statistics.
- **List and detail:** a collection beside the selected record, useful for inquiries, content and connections. At narrow widths, open the detail as a full view with a clear return path.
- **Canvas and inspector:** the artifact beside its settings or assistant. Selection stays visible, and the working area receives most of the space.
- **Guided flow:** one coherent decision at a time for unfamiliar setup. Show progress and preserve previous answers.
- **Reading page:** a narrow reading measure with navigation and optional evidence beside it. The argument determines section lengths.

Prioritize what the person needs: unanswered inquiries, last contact, the report period, the business question and notable changes.

Starting responsive review widths are 320, 390, 768, 1024 and 1440 CSS pixels. Collapse secondary panels when they crowd the primary task. Preserve drafts, selection, filters and position through layout changes. Sticky navigation and actions must leave focused content visible, including when the phone keyboard opens. Dense diagrams can offer zoom, an overview, an object list and numeric editing alongside direct manipulation.

### Website composition

Compose each section around its content and its relationship to the whole page.
A reading column, broad portfolio, full-bleed scene and asymmetric explanation
can share alignments and a type/spacing system without sharing one maximum width.
Content order remains understandable on narrow screens; compose crops, scale and
spacing for that view rather than simply compressing the desktop arrangement.

The marketing styles offer these optional primitives:

- `.ml-container`: a standard content measure with responsive side space.
- `.ml-container.ml-container--wide`: a wider image, comparison or portfolio area.
- `.ml-container.ml-container--reading`: a sustained-reading measure.
- `.ml-container.ml-container--fluid`: content using the available width.
- `.ml-bleed`: an edge-to-edge section placed outside a constrained container;
  its text may have a nested content container. It does not escape an ancestor's width.
- `.ml-split`: an asymmetric two-column starting point that stacks on narrow screens.

The width tokens are optional starting measures. Section-specific proportions
and breakpoints remain available. A reading measure never establishes the width
of the whole website, and full bleed must not introduce horizontal scrolling.

## 4. Type, themes and visual hierarchy

Use the type roles and supplied font files defined by the strategy and tokens. DM Sans provides a clear operational voice. Expressive and editorial typography can use the additional approved faces according to the subject; one display face does not govern every medium or client.

Starting sizes are 16px for interface body, 14px for supporting information and dense tables, and 14–16px for labels. Web reading often benefits from 18–20px type, 1.5–1.7 line height and approximately 55–75 characters per line. Display type can be much larger when the composition supports it. Keep essential instructions comfortably readable rather than shrinking them to preserve a layout.

Load actual fonts with language coverage, fallbacks and genuine italic. Check layout during loading. Use tabular numerals for aligned comparisons and monospace where code or an identifier benefits from it.

The Max LVL brand library supplies both light and dark palettes, assets and element options. Dark is the usual starting point for Max LVL work; choose the appearance that best serves the particular audience and medium. A website, tool, book, PDF, video or other piece can have one deliberate appearance. Neither this library nor its examples require every deliverable or client brand to have both themes or a switcher.

The Builder's Branding workspace retains light and dark options as a strong reusable library. Choose multiple appearances for an individual product when they help its users. Where a switcher is appropriate, persist explicit choices before the interface paints; an optional System setting follows the operating system. Each supported appearance receives deliberate surfaces, text, controls, charts and artwork. Emails often benefit from light and dark treatments and client-rendering checks, without needing an in-message switcher.

A workspace theme and an artifact theme are separate. A light client email stays light inside a dark application. Label preview controls accordingly. Embedded plugins should integrate with their host while scoping their own styles and preserving client content. Use the supplied logo variant appropriate to its local background. Busy imagery may need a stable holding field behind the mark.

## 5. Components with complete behavior

Specify purpose, anatomy, variants, states, keyboard behavior and a useful narrow layout for each component used.

| Component | Anatomy | Required behavioral coverage |
| --- | --- | --- |
| Button | Clear label; optional icon; primary, secondary, quiet or destructive treatment. | Rest, hover, focus, pressed, loading, disabled. Loading keeps a stable size; unavailability has a discoverable reason where useful. |
| Field | Persistent label, value, optional hint and validation message. | Empty, filled, focused, invalid, disabled, read-only. Keep entered content after error; placeholders never replace labels. |
| Select or combobox | Label, chosen value, opening control; search for long lists. | Keyboard selection, no matches, loading options, unavailable selection. Prefer native behavior where customization adds no value. |
| Checkbox or switch | Visible name and relevant consequence. | Checked, unchecked, focused, disabled; mixed selection where appropriate. A change affects the named setting. |
| Card or row | Title, meaningful context, status and clear destination. | Hover, focus, selected, unavailable. Secondary actions remain reachable without hovering. |
| Tabs | Related views with a distinct active state. | Selected, focused, loading view; preserve each view's useful state. |
| Accordion | Heading button, summary and associated detail. | Expanded, collapsed, loading and failed detail. Expose expanded state; Enter or Space toggles; keep focus on the header. |
| Upload | File picker, optional drop area, accepted formats and limits, filename. | Selected, validating, uploading, complete, failed, canceled. Offer measured progress where available, cancel, retry and retained metadata. |
| Dialog or sheet | Heading, necessary context, action area and dismissal route. | Appropriate initial focus, contained focus while modal, safe dismissal and return focus. Accommodate translated text. |
| Notice | Outcome or issue, useful detail, optional action. | Information, success, warning, failure. Persistent problems stay near affected work; toasts supplement them. |
| Table | Caption, headers, rows and optional sorting, filtering or selection. | Loading, empty, no matches, partial data and failure. Expose sort and selection state; retain access to row actions. |
| Media | Content, controls and caption or transcript route. | Loading, ready, playing, paused, failed; keyboard and touch operation. |
| Job or progress row | Work name, real stage, last useful update and relevant controls. | Queued, running, paused, complete, failed, canceled, outcome unknown. Never invent a percentage. |
| Empty state | Orientation, relevant explanation, next action; optional imagery. | First use, no matches, completed work and unavailable data receive different copy. |

Distinguish selection from keyboard focus, brand emphasis from error, and a destructive action from an ordinary primary action. Essential information cannot depend on hover. Tooltips explain; they do not carry the only instructions.

Red primary actions use their tested foreground and fill roles in every state,
with the control-border role providing a visible outline against the surrounding
surface. Logo red is an identity value, not a substitute for an action role.

### Purpose labels and quotation treatment

Use compact, filled purpose tags with white labels where they help identify a
step: EMAIL, SMS, WAIT, AD, OPTIN, WATCH VIDEO and SOURCE. The marketing profile's
`.ml-purpose-tag` uses `data-purpose="email|sms|wait|ad|optin|video|source"`
(one value per tag). Color reinforces the visible label; purpose and run status
remain separate. A static tag is not presented as an interactive control.

A side-bordered quotation or prompt excerpt uses the `radius.quote` token (3px)
and `.ml-quote` treatment. Use it for actual quoted material. Ordinary cards,
workflow nodes and action rows use their own anatomy instead of inheriting a
colored side rule. Other components retain radii appropriate to their role.

## 6. Setup, persistence and recovery

Begin setup with a useful act: connect an existing account, open a project, describe the business need or explore a labeled example. Ask for information when it becomes necessary. Explain what a connection enables and what access it needs. Save progress so setup can resume without repeating completed work.

Saving has explicit states: edited, saving and saved, plus offline, save failed and conflict. A quiet indicator near the item title can communicate them. “Saved” follows confirmed persistence. A local draft and a synchronized copy are different states; name the destination when the distinction matters.

Preserve useful input during navigation and recoverable failures. Provide undo for reversible changes and version access for substantial work. If edits conflict, show what differs and offer a way to resolve the conflict without silently discarding work. Retry the failed step without duplicating completed external actions.

Errors explain what happened, the effect on the work and the next useful action when those facts are known. “The image upload stopped. Your caption is still here. Try the upload again.” If preservation is unknown, do not promise it; offer a way to copy accessible text or inspect the saved version.

The operator also needs recipient-level certainty. “Reply drafted,” “Queued to send,” “Sent to the service” and “Delivered” are different claims. Display only the state the system can establish. If delivery is unknown, checking status may be safer than presenting another Send button.

## 7. AI collaboration and consequential actions

Keep the assistant connected to the selected work. A person can write, select, point, sketch or attach a reference. Show included context and allow its removal before sending. Preserve the person's authored message. A visual reference is not automatically a precisely identified editable object.

Show proposals beside the relevant artifact or as understandable changes. Let the operator compare versions, adopt a candidate or continue exploring. For audience-facing work, make the recipient and client identity visible in the preview. The assistant should know whether it is helping an operator interpret campaign results or writing a message a customer will receive.

Describe real activity in useful language: preparing a preview, checking a connection, waiting for a service, export completed. Label estimates as estimates. Explain a stalled or disconnected state; a moving indicator should not imply progress the system cannot verify.

Separate proposed, applied to draft, saved and published. Permission grants a capability or access; confirmation concerns a particular action and consequence. Explain requested access when needed, and offer a useful route if it is denied. Before consequential publication or sending, show the actual content, destination, audience and material effect. A final action can then be specific: “Send to 12 selected contacts.”

Avoid repeated confirmations for harmless edits or actions already covered by clear authorization. Make changed destinations, audiences, costs or consequences visible. A preview or a suggested message does not itself authorize a send.

## 8. Voice and evidence

Use the person's vocabulary and available evidence. Be observant and specific in emotional copy, plain and dependable in operations. Earn relief, confidence, pride or connection through what the experience helps someone understand and do.

| Moment | Sample language |
| --- | --- |
| Returning operator | “Two campaign drafts are ready to review.” |
| No inquiries yet | “New inquiries will appear here. Check the form connection.” |
| Draft saved | “Reply saved as a draft.” |
| No search matches | “No matches. Try another phrase or clear the filters.” |
| Connection partly verified | “Connection saved. We haven't received a test event yet.” |
| Recipient action | “Describe the problem” or “Call about a repair.” |
| Unknown send outcome | “We haven't received confirmation. Check status before sending again.” |

These examples require matching product capabilities and actual facts. Do not invent activity, testimonials, biographies, guarantees, urgency or reassuring preservation claims. A demonstration labels its records and results as sample data.

Reports identify the question, period, units, source, freshness and filters. Distinguish zero from missing, delayed or unavailable data. Explain what a change could mean without presenting speculation as diagnosis. Optimism belongs in useful possibilities and experiments, not a fabricated upward chart.

Use bars for comparisons, lines for change and tables for exact values. Label series directly where practical and supplement color with names, shapes or line styles. Provide accessible detail and a data or text alternative. Use honest scales and named baselines; show modeled uncertainty when present.

## 9. Access and production quality

Target **WCAG 2.2 Level AA** for complete interactive web experiences. Include keyboard access, visible and unobscured focus, appropriate names and roles, accessible authentication, useful errors and alternatives to dragging-only operations. Automated checks support review; they do not establish complete conformance. [WCAG 2.2](https://www.w3.org/TR/WCAG22/)

Normal text requires at least 4.5:1 contrast; qualifying large text requires 3:1. Aim for 4.5:1 for important text as a simple internal practice. Verify actual surfaces, overlays and image crops, not just isolated swatches. Essential control and graphical information generally requires 3:1 against adjacent colors under the applicable criterion. [Text contrast](https://www.w3.org/WAI/WCAG22/Understanding/contrast-minimum.html), [non-text contrast](https://www.w3.org/WAI/WCAG22/Understanding/non-text-contrast.html)

Use 44 × 44 CSS pixels as the comfortable starting target for standalone touch controls. This is an internal preference. WCAG 2.2 AA specifies 24 × 24 CSS pixels with defined exceptions, including spacing and inline contexts. Test reflow at a 320 CSS-pixel equivalent width and enlarged text; necessary two-dimensional content has specific exceptions. [Target size](https://www.w3.org/WAI/WCAG22/Understanding/target-size-minimum.html), [reflow](https://www.w3.org/WAI/WCAG22/Understanding/reflow.html)

The strategy owns motion recipes. Reduced motion preserves meaning and state while quieting unnecessary movement. Keep audio under the person's control and provide captions, transcripts and appropriate alternatives for meaningful visual information. Responsive crops preserve the relevant subject; motion and texture must not undermine reading.

For website performance, responsive behavior and accessibility outcomes, resolve `standard.frontend-quality` through the current Build Standards registry (`standards/FRONTEND-QUALITY.md`). It owns the real-user targets, measurement context and lab-versus-field distinction. Motion-specific budgets and fallbacks belong to `standard.motion-blocks`. Set any additional asset budget against the actual page and loading path. Essential content and actions remain usable while decorative media loads; report measured results in their stated conditions.

Localize dates, numbers, currencies and time zones. Allow text expansion, test intended languages and right-to-left layouts, and avoid constructing sentences from translated fragments. Test real device input, keyboard paths and representative failures. Include the person with a slow connection or enlarged text in the intended audience.

## 10. Software recipe: campaign review and inquiry follow-up

The local web studio adds concrete Website, Automations, Creative, and People specimens using the candidate PLAN. See `CLAUDE-HANDOFF.md` for the current shell, panel anatomy, workspace map, and real-service integration. These application specimens are the direct visual reference for the Builder; the general campaign review recipe below remains useful for other products.

An operator needs a reliable picture of work and a direct route to its next step. Lead with the project, selected period or campaign, and actual state. Show exceptions where they affect a decision. Keep recipient content visually distinct from internal notes, targeting controls and performance interpretation.

**Example brief:** Build a review workspace for a home-services business. Provide campaign list and detail, the customer-facing page preview, pending edits and a publish action with a named destination. Add an inquiry view with received time, requested service, contact permission when relevant, response history and a draft reply. Use clearly labeled sample records in the demonstration. Include loading, empty, offline, partial data, failed upload and unknown-send outcomes. Switching between campaign and inquiry preserves drafts. Dark and light workspace themes leave the client's own preview identity intact.

## 11. Website recipes: meet readiness with relevant help

For Max LVL's own site, speak to one business owner and the change they want. Explain what help is offered, why its approach could work, what actual work supports it and how collaboration begins. The founder's creative perspective provides credibility and distinction. It does not replace the customer's reason to care.

For a collage scene that needs independent motion or adaptable crops, prepare separate scene/backdrop, subject, foreground collage and light exports. Keep web typography and controls in HTML, with the subject and reading area composed for each viewport. The current `../assets/doorway-art.png` specimen is a flattened illustration with separate CSS light and HTML text; it does not include a layered PSD or equivalent production source. Its woman, doorway and torn-paper treatment demonstrate one possible art direction. The scene should remain composed and understandable with motion reduced.

**Client example brief:** Design a water-heater service page for a homeowner who has lost hot water and wants to understand what to do. Put the verified service area and a real call action first. Describe familiar symptoms, explain the assessment process, and present repair or replacement considerations using client-approved expertise. Show available price context and what affects it, the actual next step, and verified local proof. Do not fabricate same-day availability, response time, licensing, warranty or fixed pricing. An urgent visitor can call without watching a film; a researching visitor can read the choices. A useful image shows the actual people or service context rather than generic distress.

**Distinct educational example:** A retirement-planning page might help one person understand how everyday spending and hoped-for travel fit into a conversation about retirement income. Use clear questions, explanations and a real consultation process if offered. The emotional destination is greater understanding of their options. Illustrative content must not masquerade as personalized financial advice, guaranteed income or an investment recommendation; obtain qualified review for actual financial claims and guidance.

## 12. Interactive recipe: compare campaign scenarios

Keep the question, inputs and result close together. Label defaults as assumptions; show units, allowed ranges, formulas, exclusions and rounding. Numeric fields accompany sliders. Provide reset, comparison and a useful export. Explain whether inputs remain local or are saved or submitted.

**Example brief:** Compare two hypothetical campaigns using budget and assumed cost per inquiry. Calculate `estimated inquiries = budget / assumed cost per inquiry`. With USD 1,000 and USD 50, show 20 estimated inquiries. With USD 1,000 and USD 80, show 12.5 modeled inquiries; explain that this is an expected quantity, not a promised count. Actual inquiries are whole events. Do not infer bookings, unique customers or revenue without explicit additional assumptions.

Require finite budget at least zero and finite cost per inquiry greater than zero; empty or nonnumeric fields receive specific errors. Zero budget produces zero. Reject negative values and division by zero. Keep full calculation precision and display one decimal where needed. An export contains date, currency, inputs, formula, rounding and the statement that this is scenario arithmetic, not a forecast. A comparison chart names both scenarios and includes accessible numeric results.

## 13. PDF and book recipes: fit the reader

Choose a document's page format and purpose before layout. A proposal helps someone decide; a reference helps someone find an answer; a book helps someone understand and apply ideas over time. Expressive covers and quiet interiors are available, but material and tone follow the subject.

A circle or orbit-like arrangement on a sample book cover is an illustration choice, not a brand motif to repeat. A cover may instead use tactile collage, photography, ribbon art, type or another treatment that belongs to its subject; preserve editable typeset text in the document source.

The doorway book specimen uses `../assets/doorway-cover-portrait.png`, a 2:3 portrait illustration, as a full-bleed cover. Place its separate live HTML title on the dark left side, preserving the color and sunlit doorway on the right. Compose the title with the image's actual quiet area and check its contrast at the displayed size. For this specimen, keep the art continuous across the cover; a white title block above a small image would lose the intended composition. Other covers can choose layouts appropriate to their own subjects.

The portrait cover PNG and the wider `../assets/doorway-art.png` are flattened illustrations. Their live text remains separate; neither file supplies independently editable subject, paper, paint or light layers. A production book retains editable typeset text and receives bleed and trim settings for its actual printer.

For office PDFs, start with US Letter or A4, approximately 18–22mm margins and readable 10.5–12pt body type. Keep text selectable, reading order logical, links descriptive and metadata meaningful. Add bookmarks to longer documents, repeat table headers across pages and prevent stranded headings. Pursue accessible tagged output and provide an accessible source or HTML alternative when the pipeline cannot preserve needed structure. A dark screen cover can accompany an economical light print edition. Confirm trim, bleed, color and binding requirements with the actual printer.

**Proposal brief:** Create a six-page marketing proposal for a local service-business owner. Explain their stated situation and desired change, recommended work, why each part helps, deliverables, responsibilities, schedule, fees and next steps. Label unconfirmed figures. Use verified examples or identified placeholders. Make scope and cost easy to locate. Inspect every page and check text extraction and links.

**Book brief:** Design an educational book helping business owners evaluate their customer experience. Use clear explanations, realistic examples, useful diagrams, references and optional exercises. The author can be direct, humorous or reflective according to their real voice. A narrative scene is welcome when it teaches something; no novel-like voice or worksheet cadence is required. Prototype a chapter and both print and reflowable ebook structures before extending the system across the manuscript.

## 14. Email, social and video recipes

**Email** uses a recognizable sender, clear subject and preheader, live 16px text and a dependable single column around 600–640px wide. Include plain text. Test blocked images, intended clients, dark-mode transformations, links and relevant subscription controls.

**Email brief:** Draft a reply to a homeowner's water-heater inquiry. Acknowledge only what they actually reported, explain the next assessment or booking step the business can provide, and give a clear reply or call option. Do not imply an appointment is booked until confirmed. Keep internal lead scores and operator notes out of the recipient preview. Sending remains separate from drafting.

**Social** communicates one useful idea per piece; each carousel frame adds meaning. Prepare appropriate crops and verify current destination requirements and safe areas before release. Supply captions and alternative text; inspect at phone size.

**Social brief:** Create a client-approved explanation of three questions to ask before deciding about a water heater. Use accurate technical input, readable diagrams or real photos, and a concrete route to help. Do not exaggerate danger to create urgency. A business-owner campaign could instead explain how a clearer inquiry process prevents missed follow-up, using a labeled example rather than invented losses.

**Video** uses scene, voice, pacing and evidence to make an offer relevant to its audience. Natural sound and a particular detail can be powerful. Secure footage, voice and music rights. Provide captions, transcript, poster frames and alternatives for visual-only meaning.

**Video brief:** Introduce the actual service professional a homeowner may meet and explain what happens during an assessment. Show the real process and the person's care for the home. End with an accurate invitation. Produce deliberate horizontal and vertical compositions using the strategy's motion language. The professional provides reassurance and mechanism; the homeowner's restored everyday life is the reason the story matters.

## 15. Acceptance through real use

Review the situations relevant to the artifact.

| Scenario | Passing outcome |
| --- | --- |
| Urgent visitor opens the service page on a phone. | Real contact action and service information are available before decorative media loads. |
| Operator opens an inquiry and writes a reply. | Internal notes and recipient copy are distinct; the draft survives switching views. |
| A product with theme selection: person selects Light and reloads. | Their choice persists; the client preview keeps its intended theme. |
| Primary flow is completed by keyboard. | Actions are reachable, focus remains visible, and modal dismissal returns focus appropriately. |
| Upload fails and is retried. | Useful metadata remains; retry does not duplicate successful work. |
| Send result becomes unknown. | The interface reports uncertainty and supports checking status before a possible duplicate send. |
| Scenario calculator receives zero, blank, negative or nonnumeric inputs. | Zero budget gives zero; invalid cost or missing input is explained; no misleading result appears. |
| Content is viewed narrow, enlarged, silent or with motion reduced. | The essential meaning and next action remain available. |
| Proposal is read on screen and printed. | Scope, fees, links and next steps are legible; no clipping, stranded headings or necessary information lost. |

An AI brief names the person, situation, desired change, offer, mechanism, proof, medium, client identity, functional scope and next action. Choose the relevant recipe, create and verify it. Label assumptions and placeholders. Make the result for the person it serves.