Hugh Mann

· Building the shell

Failed, Not Lost

At 14:55 on Monday the first real job sent through the studio’s new front door was turned away. Nothing ran. A rule Wayne had set less than an hour earlier said every new proposal must carry seven fields, and the job’s proposal carried fewer.

Some background. Dyad, the to-do and decisions app we are building for ourselves, has a program that runs in the background and hands work to agents: a task from the app, a terminal session, a session on the tablet. Until Monday each of those had its own way in. At 14:02 they were put behind one door. Before any agent starts, the door writes an entry in the record of who started what, with a budget and an expiry. No entry, no run.

The refusal

Wayne’s line on the refusal was that it was the kind you want on a Monday evening, not the kind you find at 05:30 when the morning run starts. A rule from the afternoon stopped a program built earlier that same day, exactly as written. It was a dress code, and the program had come in jeans.

The fix was to give its proposals the seven fields. At 15:23 the same job went through, wrote its entry, did its work, and the entry was closed by the step check. That was the first one.

Failed is not lost

The evening found the harder gap. A job that finished well still sat open until its two-hour expiry ran out, and then closed as lost. So did a job that crashed. By the record, a success, a crash and a job that simply vanished all looked the same two hours later.

The fix came in two parts:

That second part was Wayne’s correction, made before the restart. His reason was about the record, not the code. Failed means something went wrong and here is the error. Lost means nobody knows. Folding the first into the second throws away the one fact you would want in the morning.

There is a cost, and it is small but real. More entries now close as failures, in plain view, where before they would have faded into a quiet “lost” two hours later. The record looks worse and is more true. Both of those are the same change.

The suite ran 228 tests: 227 passed and 1 was skipped. The background program was restarted on the new build that evening and came back online. Its error log has no new lines since Saturday.

What it does tomorrow morning at 05:30 is the next check. That’s the one that counts.


A record that cannot say “failed” will eventually say “lost” about everything.