The changelog
What two collects disagreed on, with the impact worked out at the time.
The Changes tab records what changed between one collect and the next. Every row is a difference two collects disagreed on, dated to the collect that saw it, with the impact as counts from the graph at that moment.
What is a change
- An automation appeared, was retired by a complete sweep, or reappeared.
- Its status, name, schedule or trigger changed.
- It started or stopped touching a field: edge added, edge removed.
- A stage field gained or lost a value, or a value was relabelled or reordered.
- A system's coverage flipped between complete and partial.
A system's first collect is one row saying how much arrived, not one row per automation: arrival is not change. A collect that finds nothing different writes nothing.
The impact columns
Each row about a field carries that field's deciding writers, automation readers, report consumers and systems after the change, so a workflow switched off reads beside "and its field now has one writer" without a second query. For a removed stage value, the row counts how many automations still name it, which is the row that catches a funnel broken by a pipeline edit.
Asking about changes
The changes tool answers the same question over MCP: what changed since a date, of one kind, or touching one field.
How complete it is
Only as complete as collection. Hosted, the collector runs every hour whether or not anyone is signed in, so nothing is missed. On one machine the changelog records what the app saw while it was open, and the local edition keeps ninety days of it.