# Modalities and Rendering Contract

## Images and visual assets

Use a dedicated image-generation/editing path when the user asks to create or
modify raster imagery. Inspect an existing local image before editing it.

For an edit:

- include the exact referenced image(s);
- use the smallest relevant set of input images;
- do not silently replace a requested image edit with unrelated code or a
  synthetic substitute;
- after generation, return the visual result cleanly rather than adding an
  unnecessary download/tutorial narrative.

For code-native UI, diagrams, SVG, and established icon systems, prefer the
project's native rendering/code path over raster generation.

## Local visual inspection

When a local screenshot, rendered UI, graph, or generated image is relevant to
the task, inspect it visually instead of inferring layout from a filename or
metadata. Record only observations that can be seen in the artifact.

## TUI/UI verification

Separate these claims:

```text
rendering code compiles
render function produces expected text/box structure
terminal/UI behavior is visually correct at runtime
```

Use the smallest proof that reaches the relevant layer. A string-render unit
test is useful but does not prove cursor behavior, terminal redraw timing, or
interactive focus without a runtime observation.

## Media/context rule

Media-derived evidence is scoped evidence. Preserve the source, time/range,
and confidence; do not inflate it into a broad task instruction or factual
claim beyond what the media actually establishes.