Changelog
A chronological record of what changed in a product, feature, or scenario over time. In Specsight, one running changelog covers the whole product, filterable down to a single Feature.
A changelog is an ordered list of changes — what was added, what was modified, what was removed, and when. Engineering teams have kept them for decades, mostly at the level of code. Specsight keeps one at the level of behaviour: a running changelog for the whole product, drawn from every release and filterable down to a single Feature.
Each Specsight changelog entry shows a before-and-after view of the affected scenarios and the release that triggered the change. New scenarios, modified scenarios, and removed scenarios are all surfaced — the difference is at the level of behaviour, not lines of code.
The result is something most teams have never had: a non-technical record of what changed in this part of the product, in this release, without a PM having to remember to write release notes. Useful for client updates, stakeholder reviews, and any conversation that starts with "wait, when did we change that?"
Related terms
- SPEC
Feature
A logical grouping of scenarios that represents a meaningful unit of the product — like “Document Upload” or “User Authentication.” Features form the structure of a Specsight spec.
- 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.
- PROBLEM
Documentation Drift
The gradual divergence between written documentation and the product it describes — widens with every release that nobody remembers to document.