Resources

What changes, and when.

Payrolless is not open to the public yet, and the repository carries no published release. There is therefore no entry to date without inventing a history. This is the framework that will hold verified changes from the first release onward.

Before the first public release
Development changes are not presented as features people can already use. The first entry will appear when sign-ups genuinely open. It will carry its release date and published version identifier; neither a provisional number nor a repository date will stand in for a release.
One entry, one observable effect
Each entry will say what a user can do that is new or different: connect another tool, understand an approval more clearly, find information, or see an error corrected. Internal changes with no visible effect will remain in the technical history, not in this changelog.
Changes grouped by release
Entries will sit under the release that put them into service, with one shared date. A release may separate additions, improvements, and fixes when that distinction makes the impact clearer. The copy will describe the shipped result, not turn a list of commits into a sales pitch.
Published after verification
A note will appear with its release after the relevant journeys have been checked on the built service. If a behaviour is removed or changes shape, that will be recorded in the same place. Future announcements, promised dates, and work still in progress will stay out.