Versions and Revisions

Drawing History in Scopture

Scopture exposes a drawing’s history so reviewers can preserve milestones, inspect earlier states, and recover from an unwanted change. Create a named checkpoint before a formal review, approval, handoff, major import, or other boundary that should remain easy to identify.

Name the event or accepted state rather than the person who created it, for example, “Coordination review accepted” or “Before structural model revision.”

Preview Before Restoring

Preview a historical state to confirm that it contains the intended drawing, project context, and referenced artifacts. Restore it only when the active drawing should continue from that point. Restoration is permission-controlled and is different from ordinary canvas undo.

Scopture also records bounded background and agent operations in drawing history. This makes an automated change inspectable and recoverable through the same application workflow as other project changes.

Source-File Revisions

A source-file revision and a drawing-history entry serve different review tasks. Replacing or revising an IFC, STEP, DXF, PDF, or other referenced asset updates the source being examined; a drawing checkpoint preserves the broader Scopture context around it.

Keep the revised source associated with the same review narrative, then create a checkpoint when the project reaches a meaningful state. Existing issues and decisions can then be evaluated against the changed artifact without treating its context as disposable.

The version graph, checkpoints, deltas, restoration rules, external-file records, and active revision mechanics are Duc format concerns. See Version Control and External Files & Revisions for those details.

For automated operations in Scopture, see Agents and MCP.