← Back to Blog

Blog post

The paragraph is the specification

Every application on this platform begins as prose.

By Ines Bekkar · Principal solutions architect · 12 August 2026 · 6 min read

There is no form to fill in and no schema to learn. An application here starts as a description of a piece of work, written in the words the work is already discussed in — which ledgers, in what order, what counts as matched, what has to be explained rather than matched, and what somebody expects to read at the end of it.

That description is not a brief that a team then interprets over six weeks. It is read into a requirement, then into a contract that names the operations the application will answer to, then into a design, and then into code. Four documents, each one derived from the one before it, and the first of them is yours.

What a good paragraph contains

The paragraphs that produce a working application on the first pass have four things in them, and none of them is technical.

  • The inputs, named the way your team names them. "The nightly sales extract" is enough; the file format is not the interesting part and we will ask.
  • What "done" means. A reconciliation that is 98% matched is either finished or not finished, and only you know which.
  • What must be explained rather than resolved. Every real analysis has a residue. An application that pretends otherwise is confidently wrong rather than usefully incomplete.
  • Who reads the result. A pack for an audit committee and a file for a warehouse system are the same analysis with two different endings.

What a good paragraph does not contain is a technology. Naming a database, a scheduler or a library is the fastest way to get an application shaped around a tool instead of around the work.

What comes back, and what to do with it

What comes back is an application: a set of named operations, an HTTP interface in front of them, a background worker that finishes the long ones, and a place its results are written. You call an operation, you get a job id, you poll the job, and you read the result out of your own store.

The first afternoon with it should be spent doing what you would do with a new analyst — correcting it. In practice the corrections are always the same three kinds: a rule that was too generous, a cut-off that was a day out, and a threshold that mattered to somebody who was not in the room when the paragraph was written.

Corrections change the description, not the code

This is the part that is genuinely different, and it is worth being explicit about because it sounds like a technicality and is not.

When a correction lands, the application is regenerated from the corrected description rather than edited in place. The paragraph, the requirement, the operation contract and the design move together, and the code is derived from them again. That is what the platform calls Evolve, and it is a phase of an application's life rather than an exception to it.

The cost is that you cannot make a change by editing one function and moving on. The benefit is that after two years the application still matches its description, because there has never been a moment where the two were allowed to disagree. Every system that lets you patch the code and update the document later ends up with a document nobody trusts and a codebase only one person can read — which is the failure mode the workbook you are replacing already has.

What this asks of you

Three things, and they are all unglamorous.

Write the paragraph yourself rather than delegating it, because the person who knows what "matched" means is the person who has to write it. Expect the first fortnight to be a fortnight — of correcting, not of building. And accept that a vague sentence produces a confident application that is wrong in exactly the way the sentence was vague, which is the most useful property this whole arrangement has: the ambiguity surfaces immediately, in the answer, instead of two quarters later in a meeting.

The figures in this piece — including the ones in the panels — are illustrative. They show what a result of this shape looks like, not a measurement of anything that happened.

Read next

Stories for the same roles