In the world derived over the previous twelve steps, one cost appears almost everywhere: the cost of having others read, calculate, judge and act on one's behalf. Ordinary people hand their money to a few professional institutions, a principal can see only a manager's past performance, defaults can only be designed for the circumstances of the majority: all of this has to do with that cost. Now change only this one parameter. Let the price of this labour collapse and keep everything else the same: grain is still harvested once a year, ships can still sink, people still favour the present. Then derive again the steps that it affects.
The method is unchanged: change one thing at a time and look at the result. What changes is the price of cognitive labour, that is, the labour of reading, calculating, writing, comparing and carrying out instructions. What stays the same is time, risk and human preferences. The advantage of this approach is that it separates "the changes brought by a new technology" from "the problems finance has always had": any constraint that survives the new derivation is not one this technology can solve.
The affected steps change in different ways. Some constraints loosen, such as the cost of research and comparison. Some tighten instead, such as checking what a tireless agent has done. Some do not change at all, such as time and risk themselves.
Changing only the price of cognitive labour and deriving again the steps of delegation, commitment, information, markets and bias, the conclusion fits in one sentence: scribes make research, comparison, monitoring and execution almost free, but bring new constraints of guarantees, checking, herding and the exploitation of bias; the information advantage shifts to exclusive data and speed; and not one of time, systemic risk or irreversible loss disappears.
This shows what a product built around an agent should do. Where constraints loosen, give the savings back to the user. Where they tighten, fill the gap with accountability, records, permissions and written goals. Where nothing changes, tell the user honestly what the product cannot do.
Part Two yields new principles and also retests the principles already obtained in Part One: after the parameter changes, do their premises still hold?