The example
One process, end to end.
A property manager’s maintenance dispatch, followed the whole way: the manager’s own words, the interview that closes the gaps, the plan that is proven before it may run, and the run itself — which cost $0.11, end to end.
The client is a constructed illustration, not a customer — the first real runs replace it as engagements close. The record shows the same run at full depth: the hold, the negotiation, the verdicts.
The business case.
Tallowbrook manages 1,900 rental units across two cities. A maintenance request touches four parties and takes between four and eleven days, nearly all of it waiting. The coordinator’s own work arrives in ten-odd sittings spread across those days — read, decide, ask, arrange, raise, chase, report — each one a return to a file that has moved on since. There are around 340 tickets a month.
The days themselves are not going anywhere. The question is who keeps coming back to each ticket — ten times a ticket, 340 tickets a month.
It starts with a plain request
No form and no specification — a description with gaps in it. The gaps are what the interview is for. An extract:
Then AI++ authors the plan, and proves it structurally correct
The plan has nine steps; the shaded ones wait on a person. This is the same diagram the manager signed off.
Against a coordinator carrying the same dispatch by hand — triage, vendor selection, access scheduling and owner reporting, returned to again and again across the days it runs.
Tallowbrook Property Management is a composite client.
Seen enough?
The full artifact behind this run — the fourteen-hour hold, the three-round negotiation, the evaluator verdicts — is on the record page. Or skip ahead: describing a process of your own takes a paragraph, and the evaluation is free.