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.
A full analysis runs once when you first connect a project, and again any time you choose to rebuild the spec from scratch. Specsight clones the repository, walks every source file, and produces a complete set of features, scenarios, and connections. Most projects finish in under an hour; very large codebases take longer.
Full analyses are heavier than syncs because they read the whole codebase rather than only the changed files. Most teams only need to re-analyse after a major refactor or restructure.
After the full analysis completes, the spec is live. From that moment on, every release to your tracked branch triggers a sync that touches only the affected scenarios.
Related terms
- OPERATIONS
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.
- OPERATIONS
Project
A connected codebase in Specsight, scoped to one organisation. Every feature, scenario, and changelog entry belongs to exactly one project.
- 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.