Recurring service cycle
Prepares each agreed reporting cycle so it does not start blank; the service owner approves each issue.
Serve clients
The saved work
A briefing that distinguishes change from uncertainty
Changed: R1 is classified changed. The assurance record is now reported received and the status is ready rather than blocked. This supports preparing the question whether mobilisation may responsibly be proposed, but does not approve release: validity and actual authority require review.
Unchanged: R2 remains open with no recorded client instruction; R4 remains open with no diary acceptance. The competent existing steering meeting and action register remain the process comparator, not proof of current operational continuity.
Uncertain: R3 remains unknown; validation was not observed and technical evidence is missing. The actual decision implications are therefore limited: the ordinary pre-read/meeting can prepare questions, while waiting for Nadia’s R1 evidence review, the fictional client sponsor’s R2 instruction, the fictional specialist reviewer’s R3 validation, and the fictional programme lead’s R4 confirmation. A proposed exception brief remains an internal input, not existing delivery or rewritten issued advice.
A related local example. It shows the stated part of the work, not every step in this design. Read it in saved outputs
- Starts when
- Agreed briefing/report cycle
- What it works from
- Authorised updated sources, method and prior issued output
- What it prepares
- Updated briefing with changes, exceptions and reviewer queue
- What your team decides
- Service owner approves each issue; continuity is not auto-renewal
What this helps your team do
This path has been checked in the fictional local build.
Responsibilities connected
See what each agent is responsible for preparing in this workflow. These are designs and local examples, not a set of independently running agents.
When it stops and asks
Unclear commitment, stale advice or missing recipient/authority is returned to the client owner; no agreement or delivery is inferred.
Supported scope, source access and authority are agreed for each installation.