Documents and artifacts
An accepted artifact is the canonical deliverable for that job, and it outlives the workspace that produced it.
Run workspaces hold mutable working files. Documents and artifacts are the reviewable outputs retained beyond the active workspace, and an accepted artifact is canonical for that deliverable.
That distinction is what stops a stale working copy from quietly becoming the record. When a workspace copy conflicts with an accepted artifact, the run surfaces the conflict rather than choosing.
Editable by design
For presentation work, Opulent creates a native editable file rather than a web-only deck. Documents, spreadsheets, and presentations retain durable previews so the reviewer can inspect the rendered result after the active workspace cools or reloads.
A source file cannot prove its own rendering. Ask for final-format review as part of completion, not as a separate favour afterwards.
Working from images
Images attached with the opening request are available during the first planning turn. Opulent can inspect a screenshot, chart, scan, or design before choosing the method, which matters when the method depends on what the input actually looks like.