Build notes from the products we run, how we put AI systems into production, and the reasoning behind design decisions. An outside claim carries its source; every note carries its date.
Topics: Build notesAI systemsGovernance and securityDesignField notes
Drawing a box over text leaves the text in the file. What a PDF still carries after the box, why Redact PDF rebuilds a marked page as an image, and how it checks its own export before you send it.
Read the noteSix notes, newest first
Drawing a box over text leaves the text in the file. What a PDF still carries after the box, why Redact PDF rebuilds a marked page as an image, and how it checks its own export before you send it.
Generating a working application has become cheap. What still costs money is knowing how it fails, who is told when it does, and what happens next: the work between a convincing demo and a system a business can run on.
The protocol hands a model a list of functions it can call. Whether a call should happen is a separate decision, and the specification says so itself. How we draw that line when an agent goes into production.
A log that can say why an agent acted, who approved it and what it had read is an engineering artefact. The fields we think belong in each record, who may write it, what is redacted and how long it is kept, each with its source.
A blank, a zero, a confident sentence and a spinner each hide a different gap. Seven kinds of not knowing an interface has to tell apart, what a reader needs from each, and the honest form, shown in products we run.
Two quotations for the same material can differ in unit, tax basis, delivery point and version, and a ranking that ignores any one of them is a guess. The rules we gave Rateslip for refusing to rank, and what it does instead.
When a note is published, one email, with the note. Product engineering, AI systems and the decisions behind what Kordal builds. Nothing else is sent to this list.
RSS feed
