Capture
Record every repository and exact commit included in the assessment.
Delivered capability · 02
Commit-pinned assessments
Reproducible migration analysis tied to an exact code, dependency, configuration, and infrastructure state.
DeliveredEvidence-led product capability
SnapshotExact commit
ComparisonRevision to revision
Planning resultReproducible evidence
Capability overview
Built around a verifiable operating model.
Every CutoverGrid assessment is anchored to immutable repository revisions. Findings do not simply say that a package, runtime pin, or configuration exists; they record the repository, commit, file path, structured location, observed value, and analysis rule that produced the conclusion. Engineers can reopen the same assessment and verify the same source state even after the default branch has moved forward.
When repositories change, CutoverGrid creates a new evidence state instead of silently rewriting history. The system compares revisions, marks findings as resolved, changed, unchanged, or newly introduced, and identifies which effort assumptions, migration tasks, and cutover gates require recalculation. This makes the migration plan a controlled record of technical change rather than a report whose source context is lost over time.
How it works
From source context to operational control.
Analyze
Run deterministic rules against the pinned source and configuration state.
Compare
Rescan later revisions and classify the change to each finding.
Propagate
Update readiness, effort, tasks, dependencies, and gates affected by new evidence.
Evidence produced
Every decision remains inspectable.
The capability produces structured evidence that can be reviewed by engineers and reused by downstream planning and verification.
Source coordinates
Repository, branch, commit, file, line, and configuration path.
Rule identity
Rule version, applicability conditions, severity, and confidence.
Change history
Previous and current observations with resolution classification.
Decision lineage
The estimates, tasks, waves, and gates that depend on the finding.
Operational impact
Why this capability matters.
Commit-pinned assessments give engineers a stable object to review and challenge. They also prevent a common migration failure: making a decision from one source state, executing against another, and no longer knowing whether the original risk still applies.
See it in a migration assessmentMigration control in practice
Connect the evidence to an executable plan.
Start with the repositories, define the target transition, and see the technical and operational work required.