Status: Accepted, needs to be more formalised and used in the system, not just via handlers and watchers. needs more work. Date: 2026-08-06 Related: [[ADR-018-Plugin-lifecycle]]
A schedule kept running after the decorator that declared it was removed.
"nothing ever gets removed bro, it gets superseded"
a watcher is cold declaration plus hot tally
"is OK"
tally private stream
"is OK"
Schedules take the shape watchers took: the declaration is cold and one object per schedule, the ticks are a private stream, and what changes on every tick is derived from it rather than stored.
The object prefix is named for the SQLite table it stands in for.
make paritypairs a backend's prefix with a table by exact name, so a prefix under any other name reads as a second thing and leaves the line atNO.
An empty declaration is a declaration. A plugin that declares no schedules is saying that everything it used to schedule is withdrawn, and the pruning that withdraws it only runs if it is called. Skipping the call when the list is empty means "declares nothing" reads as "keeps everything".