Sync
The release-triggered update to a Specsight spec. Fires automatically every time code lands on the tracked branch, touching only the scenarios that release changed.
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 sync fires: only the changed files are sent for analysis, and only the affected scenarios are updated. Unchanged scenarios are left alone.
A sync usually finishes in minutes, even on large codebases. It does not rebuild the whole spec, which is what a full analysis does. And it does not require human approval, which is the structural shift that lets the spec follow the code with no one in the loop.
When a member edits a scenario, that edit becomes part of the spec. Every sync after it reads the spec as it stands, so Specsight continues from the team’s version rather than its own earlier draft.
Related terms
- OPERATIONS
Full Analysis
The initial scan of an entire codebase that produces the first version of a Specsight spec. From then on, only syncs are needed.
- CONCEPT
Product Observability
Continuous insight into how a product behaves and changes, release by release. The same idea as infrastructure observability, pointed at the product itself.
- PROBLEM
Documentation Drift
The gradual divergence between written documentation and the product it describes, widening with every release that nobody remembers to document.