
Recurring reports that spawn themselves
Every recurring report is rebuilt as if it were new, by whoever remembers it is due. This is how an agent instantiates each cycle from a definition written once, with sign-off by the owner before anything is distributed or used.
Each cycle starts as if the report were new
Due on a date only one person remembers
- The report is due on a date only one person remembers.
- The rebuild starts from last month's file, with the sources re-pulled by hand and the formatting redone, and a number changes that nobody can explain because nobody can say which pull it came from.
- A version goes out before anyone has looked at it, and the correction goes out after.
- Each cycle starts as if the report were new.
Defined once, instantiated every cycle, seen by its owner before it goes anywhere
- The report is due whether or not anyone remembers.
- What moved is shown rather than hunted for.
- Nothing circulates unseen.
How an agent runs it
A recurring report is defined once and instantiated every cycle, which is the whole mechanism. The workflow holds the definition, builds each instance from it, shows what moved, and puts every instance in front of its owner before it goes anywhere.
Holds
Instantiates
Compares
Flags
Human gate
Distributes
Proposes
What changes when the definition does the remembering
Due whether or not anyone remembers
What moved is shown, not hunted
Nothing circulates unseen
Where this fits
Tier 1 through the Automate a Workflow door: one process, the routine, from a definition to a signed-off instance. The boundary is that the definition, the sign-off and every decision the report informs are a person's; the routine carries any report whose content has its own page, such as Job and project status reporting, continuously. It extends toward The agent-run operations back office, where every scheduled report runs this way, as a possible next step rather than a promised state. How It Works covers governed routines and their gates, and Plans vs routines: finite projects and recurring processes, governed differently covers how a routine differs from a plan.
