Release Sync
The release-triggered update that keeps a Specsight spec in sync with the codebase. Fires automatically every time code lands on the tracked branch.
When a Project is connected, Specsight watches the branch you nominate (often `main` or a release branch). Every time a release lands on that branch, a Release Sync fires: only the changed files are sent for analysis, and only the affected scenarios are updated. Unchanged scenarios are left alone.
A Release Sync usually finishes in minutes, even on large codebases. It does not rebuild the whole spec — that is what a Full Analysis does. It does not require human approval — that is the structural shift that lets the spec stay current without anyone remembering to maintain it.
Once a Scenario has been edited by a Member, future syncs do not overwrite the manual change. If the underlying code conflicts with the manual edit, the Scenario is flagged for review instead. The team always owns the final word.
Related terms
- OPERATION
Full Analysis
The initial scan of an entire codebase that produces the first version of a Specsight spec. From then on, only Release Syncs are needed.
- CONCEPT
Living Documentation
Documentation that is structurally incapable of falling out of sync with the product, because it is derived from the code rather than written separately.
- PROBLEM
Documentation Drift
The gradual divergence between written documentation and the product it describes — widens with every release that nobody remembers to document.