Checkpoints And Change Review
Capture immutable review baselines, compare them, and discuss current saved changes with Archie
A checkpoint preserves the modeled architecture at a moment within a project version. Continue editing that version, then compare its saved state with the checkpoint or capture another checkpoint for a repeatable comparison.
| Need | Use |
|---|---|
| A separate line of architecture work | History → Versions |
| An immutable review baseline within one version | History → Checkpoints |
| A comparison of two captured states | Checkpoints → Compare |
| Changes from a checkpoint to the current saved state | History → Review changes |
| A proposed future state before changing the baseline | History → Simulations |
Capture A Checkpoint
- Confirm the selected project version and save relevant editor changes.
- Open History → Checkpoints and choose New checkpoint.
- Give it a recognizable label, such as “Before payment contract review.”
- Choose Capture checkpoint.
Existing checkpoints are never overwritten. Capturing a checkpoint requires edit access and keeps the project version editable. The newest checkpoint becomes the default reference for change and drift reviews.
Open a checkpoint from its history to inspect the captured inventory and resource details. These viewers read captured evidence, rather than substituting today's model for an older resource. Older checkpoints can lack some detail; a coverage notice identifies that limitation.
Compare Two Checkpoints
Switch from History to Compare and choose the before/after range on the timeline. At least two checkpoints from the selected version are needed.
Use Explorer to see additions, modifications, and removals in their architecture context, or Changes to concentrate on the change list. Filter by status and search for a resource, then inspect it Side by side, Before, or After. Resource-specific viewers show the captured systems, relationships, workflows, deployments, documents, and other supported model content.
Unchanged resources do not fill the change sidebar. They remain inspectable from the Explorer so a changed resource can still be understood in context.
Checkpoint comparison focuses on architecture content: descriptions, relationships, ownership, behavior, data, and other modeled properties. Moving nodes, changing zoom, routing edges, or rearranging a saved view does not create a model change in this review. Captured layouts remain available for the visual previews.
Review Current Changes
Open History → Review changes, or use Review changes from Overview or Checkpoints. The default baseline is the newest checkpoint; choose an older checkpoint when the review needs a longer interval.
The briefing explains recorded changes, links to modeled workflow, capability, data, and decision evidence where available, and supplies discussion questions. Choose Discuss this change for one finding or Discuss with Archie for the briefing.
The briefing itself uses saved model evidence and does not make an AI call. A dependency link identifies something worth reviewing; it does not prove a failure, a new risk, or a measured operational impact.
The current side is an observation of saved data. Unsaved edits are excluded, and concurrent saves can happen while it loads. Refresh to observe current state again. Capture a second checkpoint when the review needs two fixed states.
This is a difference between states, not a chronological audit of every edit. Opening or refreshing the review does not capture or advance a checkpoint. With no checkpoint, create one first; with no modeled changes, the page reports that the architecture held steady.
Discuss The Evidence
The Archie handoff includes a reference card with the review's project, version, baseline, observation time, and bounded excerpts of the changed evidence. Open review returns to the review page.
The attached observation stays tied to what was reviewed. Reopening the page or asking Archie to inspect current resources can return newer evidence. Large briefings can omit findings or shorten excerpts; inspect the full comparison when those limits matter. Archie discussion uses the normal AI configuration and usage rules.
Preserve The Review In A Document
Add a Checkpoint diff artifact to an Architecture Document and choose the two captured states. Use the interactive comparison for detailed review or the summary for a short report. Follow it with the team's conclusion, owners, and next steps.