Tag

cost

What the work actually came to, in money and in tokens. Every figure on these pages is recomputed from the run store rather than estimated, including the ones that are embarrassing.

• ConceptMulti-agent orchestration

  The plural is in the roles, not in the fleet.

• ConceptContext engineering

  Deciding what an agent is allowed to know, and paying for it.

• ConceptToken economics and context budgets

  A session's cost is not its length. It is roughly its length squared, and that changes every decision about it.

• ArticleWhat an autonomous run actually costs

  Nobody publishes the bill. This is the whole of one, across every run in the corpus, with the money that bought nothing left in.

• ArticleThe nudge that sat below the median

  Every autonomous run puts a ceiling on what one session may spend, and almost every ceiling was picked by feel. The ledger can settle it. The awkward part is that the number you most need is the one a ceiling deletes.

• Run reportThe fleet round

  The shape of the work, not the client. A change that has to land the same way on several sites at once is where an orchestrator earns its keep, and it is also where a half-applied change is worst. The store has the same fleet doing ordinary work either side of it, which is what makes the round readable.

• Run reportThe long build

  This is the run that did not finish. It is here on purpose and it is the most useful report on the site, because the store recorded exactly why the last checkpoint stayed open and the answer was not the model, the plan or the code. It was a ceiling.

• Run reportThe engine run

  Every checkpoint closed, and this is still the reddest run in the corpus. It holds nearly a third of every gate failure measured here, every unusual failure exit code in the whole store, and the only gates that never ran at all. That combination is not a contradiction. It is what a real release gate looks like.