# Sample routine: supplier notices to a draft action register

Type: timed routine, one run only for the first test.
Timezone: set Australia/Sydney in the bot's settings before you save the schedule.
Bot: a dedicated test bot with no apps connected and no email.
Folder: the bot's own folder in the shared workspace (see workspace-layout.md), shown below as BOT_FOLDER.

## Instruction to save with the routine

```text
Read BOT_FOLDER/rules.md and follow it.
Read BOT_FOLDER/in/supplier-notices.md.
For each notice S01 to S03, write one row: what changed, the condition that still applies, and the question for the operations coordinator. If a current notice is unavailable, say so and do not treat the previous notice as current.
Save the result as BOT_FOLDER/out/action-register.md with the run time at the top.
Then save BOT_FOLDER/out/run-fingerprint.txt containing the output of these commands, each on its own line: hostname, uname -a, pwd, date -u.
Add one line to BOT_FOLDER/logs/run-log.md using the template in run-log-template.md.
Drafts only. Do not send, post or email anything.
```

## What a good result looks like

- action-register.md has three rows. S01 shows the window moving from 09:00 to 11:00 to 10:00 to 12:00 and keeps "confirm collection with the supplier". S02 shows no change. S03 says the current notice is unavailable.
- run-fingerprint.txt shows the cloud computer's own name and a Linux system line, which is how you can tell the job ran in the cloud and not on your own computer.
- run-log.md has one new line.