Rendition: definition and contract

A Rendition is an editable explanation derived from approved Observations without rewriting source truth. It can crop, frame, annotate, narrate, localize, sequence, or omit approved material while retaining the Journey Version, context, evidence, privacy policy, approval, transforms, and content hash behind the result.

Why evidence and presentation are separate

Evidence must remain stable enough to support a Decision. Customer-facing explanations must remain editable enough to be useful. Treating one object as both creates a conflict: either editorial work mutates the evidence, or every harmless presentation change requires a new Run.

The Rendition boundary resolves that conflict. The Observation stays immutable; the Rendition keeps ordered, attributable revisions.

Reshot Rendition types

Reshot defines ten product-facing types:

1. documentation screenshot;
2. step guide;
3. support procedure;
4. interactive walkthrough;
5. in-product guidance;
6. support clip;
7. training output;
8. interactive demo;
9. marketing visual;
10. captioned product video.

Renderer formats are implementation details, not additional product types.

What a Rendition revision retains

• source Journey Version and approved Observations;
• selected frames, steps, or evidence regions;
• crop, annotation, camera, timing, caption, narration, brand, and localization edits;
• declared editorial text separated from observed product facts;
• redaction and privacy treatment;
• reviewer, approval state, renderer, and content hash;
• freshness state and downstream Publications.

Example: documentation screenshot

A writer may crop an approved product frame, add a callout, and localize its caption. Those changes create a new Rendition revision. They do not alter the screenshot retained in the Observation or fabricate a state that never ran.

An approved Rendition becomes deliverable through a Publication. Explore Library for the customer-facing creation surface.