All the scenariosLaw firmsContract and deadline registerSimple
The export of the active contracts
The situation
The contract register comes out of the spreadsheet as a CSV: one row per contract, with its end date, notice period and tacit-renewal flag. As of the first of April two deadlines have already gone by, and nobody looking at the file had noticed.
The documents
The same files the agent was handed. Open them before you read the rest: the names, addresses and VAT numbers are invented, the structure is not.
What the agent does
The same four phases as every run, in order. In the console you watch them go by one at a time, with the credits beside them.
- 01DiagnoseReads the input and decides what the job actually is.
- 02AssemblePicks tools, data sources and the model you chose.
- 03ActDoes the work. Anything that leaves the building waits for approval.
- 04AssessChecks its output against your rules before settling credits.
The result
Result being recorded
This scenario is ready, but its real run has not been recorded yet. Until it has, there is nothing to show here: we would rather print one honest line than a fake result.
What to look for
Nine deadlines with their row-by-row source and two already past: the software contract with ninety days' notice, whose window closed on 29 January (30/04 minus 90 days, minus one day of safety) and which renews on 30 April, and the policy that expired on 15 March. The other seven are in date order, with the days left; two notices are already drafted.