The record
One run, in full.
Most systems can tell you that something ran. AI++ tells you what it was asked, what it decided, who said what, why each result was accepted, and what the whole thing cost.
Below is the record of a single maintenance dispatch. The client is a composite — the first real records replace this page as engagements close — but the shape is the system’s own: this is what it writes at every checkpoint, of its own accord, whether or not anyone ever asks to see it.
The element names on this page — pluck, produce, negotiate — are the plan language; the technology page shows it at work.
process maintenance dispatch (plan 21, verified) client tallowbrook property management opened 2026-07-14 09:12 by tenant message, unit 4C, meadow court closed 2026-07-16 11:48 held 40h 03m waiting on people, across two holds restarts 2 (resumed at the same step both times) outcome completed cost $0.1147
Standing decisions this run was bound by
Handed to the AI before it wrote a line, so none of these were open questions at run time. The record carries them because a decision that shaped a run is part of what happened.
approval-limit settled 2026-03-02 Any single repair over $1,000 requires the owner’s approval before work is scheduled. vendor-eligibility settled 2026-01-19 Only vendors licensed for the trade, insured to current date, and with no open dispute may be selected. tenant-contact-hours settled 2026-01-19 Tenants are not contacted before 08:00 or after 20:00 local, except for a habitability emergency. access settled 2026-05-11 No vendor is given entry without either the tenant present or written tenant consent recorded against the work order.
The hold: fourteen hours, two restarts, nothing lost.
Everything this site says about waiting is in this one artifact. The estimate exceeded the standing $1,000 limit, so the run asked the owner — and parked. Overnight, the server restarted twice. The conversation carried on as if nothing had happened, because for the process, nothing had.
The decision
$1,850 exceeds the standing $1,000 limit, so the above branch was taken: ask the owner, and wait for an answer.
The conversation
14 jul 09:31 → owner (r. mehta) Unit 4C at Meadow Court has an active leak at the kitchen supply line. Marrowgate Plumbing quotes $1,850, which is above your $1,000 limit. May I proceed? 14 jul 09:31 process parked · waiting 14 jul 18:40 server restarted · resumed at this step 14 jul 22:05 server restarted · resumed at this step 14 jul 23:34 ← owner (r. mehta) Yes, go ahead. Please get photos before and after.
Result
APPROVED held 14h 03m across two restarts; resumed at the same step with nothing lost. The owner's photo request was carried forward into the work order.
The negotiation.
Two parties, three rounds. The standing contact-hours rule was honoured without anyone thinking about it, and written consent turned out not to be needed — the tenant chose to be present instead.
What it was asked
Converge the tenant and the vendor on a single appointment window, honouring the standing contact-hours decision. The tenant must be present or give written consent.
The rounds
round 1 tenant proposes wed 18:00–20:00, thu 18:00–20:00 vendor declines both — outside service hours round 2 tenant proposes thu 08:00–10:00 (will be present) vendor accepts thu 08:00–10:00 round 3 both confirm → converged
Result
AGREED Thursday 16 July, 08:00–10:00. Tenant present, so written consent was not needed.
The verdicts.
Every acting step is judged by an independent checker before its result counts for anything. Three of this run’s verdicts, verbatim:
An evaluator reports what it observed, never a cause it did not see. Had it been unable to read the work order, it would have said exactly that — not that the work order could not be written. The rest of the run — triage, vendor, notify, confirm, report — is the execution trail on the home page, step for step.
What the run cost
01 classify the request 0.0041 02 select a vendor 0.0188 03 check the approval limit 0.0009 04 ask the owner 0.0194 05 converge on a time 0.0402 06 create the work order 0.0112 07 notify the tenant 0.0038 08 confirm completion 0.0091 09 report to the owner 0.0072 ──────── total 0.1147 usd
Roughly eleven cents, against the fifteen to twenty minutes of a coordinator's time that the same dispatch normally takes — triage, vendor selection, access scheduling, and reporting back to the owner.
The point is not the number. It is that the number exists, per run, without anyone instrumenting anything.