Current vs stale
When the artifact changes, older outputs stop appearing current.
The Deliverable Workspace brings artifact version, native/publication outputs, independent-review status and stale-file state into one governed view. It is an operating surface over the existing deliverable authorities—not a new renderer or approval system.
Users can see current version, output formats, renderer provenance, review state, revision lineage and whether human approval is still required.
When the artifact changes, older outputs stop appearing current.
A clean review belongs to one exact artifact checksum and becomes stale after revision.
Current PPTX, DOCX, XLSX and PDF references are surfaced when the canonical output provides them.
Revisions create immutable new versions, support compare/branch/merge/restore semantics and generate an invalidation plan so narrative, layout, evidence and render stages can be recomputed as needed.
Stale edits cannot silently overwrite a newer artifact head.
ServAI does not guess when two branches change the same governed field.
Changing source content can invalidate old native files instead of leaving them falsely current.