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 way infrastructure observability (Datadog, Sentry) watches your systems, pointed at the product itself.