Read a message that arrived and prepare the answer

Runs the whole thing over one message: works out what it is about, files it against the lease, unit or building it names, does what it needs, and writes the reply.

What it does is decided by an agent reading the message with the tools the sender is allowed: it may read a deed or a lease that arrived, file a document they sent in, look up the records, make or propose a change, plan a task, or hand the message to you. A message that needs you goes on your list, and its reply waits for you.

A document that arrived with the message is read when its pages come with the request, as page parts of a multipart form beside the file itself. Drawing a PDF needs a renderer and there is none here, so the caller draws it: a browser with pdf.js, the command line with poppler. Without the pages the file is filed and the step says it was not read.

The reply is written on the conversation and never sent: nothing here can send from your address, so the most a run does is file the answer. It is filed rather than left waiting only where the master switch is on, your settings say so, the guardrails resolve to something other than "ask me first", and nothing about the message says a person should answer it. Any one of those leaves it waiting, and the step names which.