Changelog
A chronological record of what changed in a product, feature, or scenario over time. In Specsight, every Feature carries its own.
A changelog is an ordered list of changes — what was added, what was modified, what was removed, when, and (where the source allows) by whom. Engineering teams have kept them for decades, mostly at the project or release level. Specsight applies the same idea per Feature: every Feature has its own running changelog, drawn from the releases that touched it.
Each Specsight changelog entry shows a before-and-after view of the affected scenarios, the release that triggered the change, and the Member who shipped it. 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 living product specification.
- OPERATION
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.
- PROBLEM
Documentation Drift
The gradual divergence between written documentation and the product it describes — widens with every release that nobody remembers to document.