Georg Chimion

Every condominium association, by the third month of its existence, discovers the same six problems in approximately the same order: something needs fixing, somebody has not paid, a document is missing, a tenant has appeared without warning, a vendor has sent an invoice that nobody can read, and the board meets on Tuesday.

Vestia, composed over the course of two years for a consortium of South Florida properties, addresses these six problems in their natural sequence. A triage module reads maintenance requests and routes them by urgency. A compliance module watches the calendar and files what must be filed. A collections module writes the letters that must be written, though more politely than the properties had written them before.

There is a fourth module, for screening, and a fifth, for documents, and a sixth, for vendors. Each is composed to a single design principle: the board should leave the Tuesday meeting having done less work, not more.

This is not the ordinary fate of software in this sector. The ordinary fate involves a six-month sales cycle, a nine-month implementation, and a twenty-minute quiet funeral. Vestia, in its current form, runs the operations of several associations who have asked not to be named — a courtesy the monograph is happy to extend.

The household budget, considered honestly, is not a spreadsheet. It is a quiet argument between what the family means to do and what the family has, in fact, just done at the grocery store. Ask Penny was composed to sit in the middle of this argument without taking a side — an amiable intermediary who reads the bank feed and offers, each morning, a brief account.

The piece reads the day's transactions, arranges them, notes the unusual, remembers the regular, and writes — in a short paragraph — what has changed since yesterday. It does not shout. It does not pester. It does, on occasion, ask whether the coffee line item is really about the coffee, which the family is welcome to ignore.

The composition uses a modern language model as its narrator and an open banking integration as its ear. It is the plainest of all the works in this volume and, perhaps for that reason, the one the author's family uses most.

A companion note, on the matter of not nagging, appears in the appendix.

The question the piece addresses is an old one in this sector: what can be delegated? The composition answers in four parts — a Project Manager, a Coder, a Reviewer, and a Deployer — each an autonomous instance of Claude, each with its own tools and its own shorter temper about its narrow job.

The four agents take a single-paragraph brief and deliver, without further human supervision, a production website. They quarrel with each other in a log file, which the author has permitted to remain visible in the interest of craft.

The piece is, among other things, an argument for division of labor: no single model, presently, does all four jobs with equal grace. Four models, each confined to one, do.

There is a room in every bank where reconciliation is performed, and it is usually the room where the lights have been on for some time. ReconX was composed for this room. It performs a multi-pass match against the day's transactions, raises exceptions to the level required, and produces a nostro proof against a service-level timer.

The installation is, in every case so far, a quiet one. The piece does its work beneath the floorboards. One notices it, much as one notices a reliable furnace, only in its absence.