The Same Three Facts, in a Different Order

The form had a line marked Work Experience. The woman at the kitchen table stopped there and asked her daughter how you fill in the last twenty years.

Leave it blank, the daughter said. She didn't. She wrote one word instead — homemaker — then looked at it and said that doesn't count, and crossed it out.

There was a job going at the community canteen: kitchen help, plus carrying meals up to a few elderly people. Go and try, the daughter said, they don't care about age. I haven't had a job in twenty years, her mother said. Just go and sit down and answer what they ask you.

The interview was set for ten on Thursday morning.

We build a long-running agent that lives in the cloud. You describe a job in words, it runs on our machines, a finished document arrives in your inbox or your chat, nothing installed. This post is about the Wednesday night before that interview — four sentences typed into a phone, one page back in the morning — and about the single decision inside it that mattered, which was not a sentence at all. It was the order.

The input was a person talking, not a record

Wednesday night she practised in the kitchen, a pot of radish on the stove, the range hood running. She turned the flame down and introduced herself to the hood. My name is—

The next sentence went round in her mouth and would not come out. She turned the flame down another notch and started again. My name is— I'm fifty-one this year, and I haven't had a job in twenty years. Then she ran out of words, and the radish muttered in the pot.

Her daughter heard it from the living room. That won't do, she said, they're asking what you can do. Tell me what you've done, anything at all.

So it came out: six people at the table, twenty years. Her mother in bed for three years, and she was the one who looked after her. The boy next door ate lunch at their place all through primary school.

Nothing in that is a field. No employer, no title, no start date, no end date. There is a duration, a set of people, and one arrangement that repeated every day for two decades. Hand that to a system that expects a schema and it has two honest moves: ask for the fields, or take the mess and decide on a spine. Most ask for the fields, which is how the kitchen table became a problem in the first place.

The daughter typed while her mother talked. What's that for, her mother asked. She said it would write a draft and it would be in her inbox in the morning. Don't spend money on it, her mother said. There's no monthly plan, the daughter said — you pay for the one time you use it, several times less than the ones that bill you every month. Nothing to install either. It runs in the browser.

I've got nothing to show it, her mother said. Twenty years and not one sheet of paper. You don't need paper, the daughter said. What you say goes in.

The first line was the genre, not the person

A little after seven the next morning the draft arrived, and the daughter read it out. The opening line:

Two decades of dedicated household logistics, with extensive experience managing meals for a large family.

Stop there, her mother said. Who is this about.

That line is not a lie, which is what makes it worth looking at. It is true and unusable. Nobody says it out loud. It is the register of a document written for a reader who has already decided to keep reading, borrowed whole and worn as a coat. Ask for work experience with no fields to fill and a model will reach for the shape work experience usually takes, and that shape is a genre — confident, abstract, third person — and the genre belongs to the side of the table that writes job ads.

The fix is not to make the sentences warmer. Warmth applied to an abstract line produces a warmer abstract line. The fix was already sitting in the room: her own words, in her own order of importance, with the genre's coat taken off.

Two lines survived the audit, and neither was the impressive one

She copied the usable lines onto a sheet of paper. Six people at the table for twenty years, and nobody ever got sick from my cooking. My mother in bed three years, me looking after her alone, never a bedsore. The children who ate lunch at our place — I knew which one didn't eat coriander.

She paused after the last one. Too small, maybe nobody wants to hear it. She didn't cross it out.

The draft's closing line said: I am confident I can do this job well. That one she crossed out.

Look at which direction that audit went. The abstraction went first. The confidence went first. What survived was the detail someone on the other side of the table could actually check. Nobody can verify dedicated household logistics. Anybody who has run a kitchen can verify six at the table for twenty years and nobody ill. The coriander line says something a resume cannot: that she notices per person, unprompted. It is also the one line that could only have come from her, which is the same as saying it is the line no generator would have written.

The line she kept in the middle is the one I'd frame. One passage of the draft read: I don't like leaving a thing half done. Her own sentence, four words of it anyway, made sayable. That is the whole trick, and it is much less like writing than like promoting something a person already said into the position where it does work.

The order was the whole of it

The night before the interview she practised twice.

The first time she kept her own order — twenty years without a job at the very front. It came out sounding like an apology. She wanted to laugh, and once she laughed she couldn't go on.

The second time she followed the draft's order: the pot first, the people first, the twenty years last. That time it ran.

Same three facts. Two different documents. Nothing about the facts changed, and yet one of them is a confession and the other is an account of twenty years of work.

This is the part worth taking seriously if you build these things, and it is the part we underrate in our own work. Almost all the effort goes into producing sentences; almost none goes into sequence, because sequence feels like formatting, and formatting feels like the boring layer under the interesting one. But with a form, someone has already decided the order for you — reverse chronological, dates on the right, education last. Where the record is blank there is no form to inherit, and sequence stops being formatting and becomes the argument. Opening with twenty years without a job is a factual choice and simultaneously a claim about what the reader is about to hear. Moving the same sentence to the end uses it as context instead of as a verdict.

A system that emits facts in the order it received them will produce the apology version every time, because people introduce themselves by apologising. The order therefore has to be a deliberate, inspectable decision — something the person can see, disagree with and overrule in one move — not a house style applied quietly in the background.

What we changed after this one

Three things, all of them about the spine rather than the prose.

Input stays unordered. We stopped treating a missing schema as a failure to be corrected with questions. She was never going to produce a job title; there wasn't one. The material is allowed to arrive the way it arrives when someone talks to a person they trust at nine at night — out of sequence, with the parts that matter buried in the middle.

The spine is its own object, and it is revisable. The draft that helped her was not a better set of sentences than the one she could have written herself. It was the same material under a different order, and she needed to see that order as a thing, not as weather. Once it is a thing, "no, not that" is one move instead of a rewrite.

Keep the person's sentence. If a line is unrecognisable to the person who said it, it will be unrecognisable to the person hearing it, too. The measure of a good replacement is not how much better it sounds; it's whether it can still be defended by the person who has to say it out loud in a room.

Which turns out to be the real exit criterion, and it is not readability. She never read the draft. She copied lines onto a sheet of paper, folded it twice, practised from it, and put it under the spice jar when she got home.

Thursday, ten in the morning

Upstairs at the canteen, two people: one in charge, one about her age.

The one in charge went through her form and asked: where did you work before.

Nowhere, she said.

He made a sound, didn't look up, and waited.

So she said it, in the new order. Six people at the table, twenty years, nobody ever got sick from my cooking. My mother in bed three years, me looking after her alone, never a bedsore. The children who ate lunch at our place — I knew which one didn't eat coriander.

He looked up then, put his pen down, and asked: when can you start. Monday, she said.

Downstairs she stood at the door a while and messaged her daughter: they want me to start Monday. Her daughter wrote back: did you read the draft. No, she said. Then it was for nothing, said the daughter. It wasn't, she said.

They are both right, and the disagreement is the useful part. Judged as a document, the draft failed; she never read it. Judged as an order to practise against, it did exactly the work — the second rehearsal ran because the sequence was no longer hers to fight with. The thing we shipped was a page. The thing that got used was a sequence, spoken out loud in a kitchen, twice.

Where it sits

CloudPal runs long jobs on our machines and hands back a finished document. Nothing to install, nothing asked of your computer, nothing read from the files you already keep. You describe the job the way you would describe it to a colleague — badly, out of order, including the parts you only remember on the second telling — and the result arrives where you already look, on a schedule.

It is in limited preview: new accounts get a dollar of credit, enough to run something real, and the number of new accounts per day is capped. It costs a few times less than the comparable tools and you pay for what you use, which matters most for the documents nobody wanted to write in the first place.

If you are building anything that turns a person's own account of themselves into a document, the property worth measuring is not how the page reads. It is whether the order survives being said out loud to the person who is deciding, and whether the lines that survived the audit are the ones only that person could have said.

CloudPal.TuringCorp.net — create an Agent Pass, sign in, and say what you want done.

Earlier in this series: the second half of the draft was policy we never agreed to, it can't read anything on my laptop, a direction is not a spec, four sentences in, seventeen pages out, the requester is not the reader, the first run is a demo, the ninth is the product, the meter, not the price, we deleted the install step.