Decisions Without Alternatives Aren't Decisions

Your agent proposes something. You read it, it’s sound, you accept it. It gets logged. You move on.

A month later you open the log and read the entry back. It says what you decided. It does not say what you didn’t decide, because nothing was ever not-decided — there was a proposal and there was a yes. And here is the problem that doesn’t announce itself: that entry is indistinguishable from one where you genuinely chose. Same shape, same confidence, same past tense. You cannot tell, reading it cold, whether you reasoned your way to that line or whether you absorbed it from an agent that was good at sounding right.

I think this is the most common failure I see in operator decision logs, and it’s invisible precisely because the log looks complete. Every entry has a title, a date, a rationale. What most of them don’t have is the field that does the actual work: what else was on the table, and why it lost.

I want to make the case that a decision record without its rejected alternatives is not a decision record. It’s an assertion that has put on a decision’s clothes. And the gap between those two things is the entire reason to keep a log at all.

An assertion that has put on a decision’s clothes.

The field that feels optional

If you keep any kind of decision log, you’ve met the alternatives field. It’s the one that feels like overhead. You’ve already made the call — you know what you’re doing and why — and now the template wants you to enumerate the paths you’re not taking, which feels like writing a book report on roads you already decided not to drive down.

So it gets skipped, or worse, it gets filled with theater. Three strawman options nobody seriously considered, each with a one-line dismissal, arranged so the choice you’d already made looks inevitable. That version is worse than an empty field, because an empty field is at least honest about having no audit trail. A field full of manufactured alternatives manufactures false confidence — it reads, later, like a real deliberation happened when it didn’t.

The skeptic’s position here is strong, and I want to state it at full strength before I disagree with it: the alternatives field is busywork. The decision is what you decided. The roads not taken are noise. Recording them is a ritual that makes you feel rigorous without making you more right, and a disciplined operator should spend that energy on the decision itself, not on a museum of rejected options. Most of the time, looking at most alternatives fields, the skeptic is correct — I’ve written the theater version, and you probably have too. The question is whether there’s a version that isn’t theater, and what makes it different.

What a real alternatives field is for

The difference is testable, and the test is simple: does reading the field later change what you’d do, or does it only confirm what you did?

A theater alternatives field confirms. You read it back and it tells you the choice you made was the obvious one, which you already knew, which is why reading it adds nothing. A real alternatives field does something else — it preserves a live fork. It records options that someone could actually have chosen, with the actual reason each one lost, in enough detail that a future reader (including future-you, who has forgotten everything) could pick the entry up and reconstruct not just the verdict but the evaluation that produced it.

That’s the load-bearing idea: active evaluation. A decision is the resolution of a live evaluation between options that were actually open to you — where you could have gone the other way and didn’t, for a reason. If there was no live evaluation — if there was a proposal and a yes — then there was no decision, and the log entry recording it as one is lying about its own provenance. The alternatives field is where the entry either tells the truth about what was evaluated or admits nothing was.

This is a narrower claim than it might sound, and the narrowness is deliberate. I am not saying every action you take is a non-decision unless you agonized over rival plans. Plenty of correct moves have no live alternative — you accept the calculation that checks out, you take the only road that’s open. Those aren’t decisions in the sense this essay cares about, and they don’t need an alternatives field, because there’s nothing for a future reader to reconstruct. The class of work this is about is narrower: the choices where a path was genuinely open, you closed it, and six months later you won’t be able to tell that you closed it on purpose unless the entry says so.

And the function this serves isn’t sentimental record-keeping. It’s that six months on, the alternatives field is the only thing in the entry that can stop you from making a mistake you can no longer see you’re making.

Let me show you the entry that taught me this.

The decision that was about deciding

In early June I had to anchor a roadmap.

The background, sanded down to what matters: I’d built a small adversarial-review tool — the cold-review shape I wrote about in the first essay, a thing that fans a question out to several AI models and collects their independent verdicts. It had grown a roadmap over time. Six positions, sequenced: do this, then this, then this. The roadmap was real in the sense that I’d been operating against it for weeks. It was also, I realized when I went to write it down properly, entirely undocumented — it had only ever lived in the session-to-session handoff notes I write when I close out one working session and open the next. It had never been logged as an actual decision.

So I sat down to log it. And the obvious move — the move I almost made — was to write the six positions into the decision record as the ratified roadmap. They were the plan. I’d been following them. Logging them as decided would just be catching the record up to reality.

Here is what stopped me, and it’s the whole point of this essay. Only one of those six positions had ever actually been reasoned through. The first one — the foundational fix everything else depended on — I had examined, argued, grounded in a specific defect it was solving. The other five were just the words that were in the handoff. They’d been carried forward from session to session, narrated as “the plan,” and never once subjected to the question: is this actually the right next move, or is it just the move I wrote down once and kept copying?

If I logged all six as ratified, I would have laundered five unexamined inherited positions into the permanent record as decisions. A future reader — me, in two months, grounding some new piece of work against “the roadmap” — would have pulled those five positions out of the log and treated them as settled, reasoned, load-bearing. They’d have carried the authority of a decision while having none of the substance of one. The record would have told a confident lie, and I’d have believed it, because I’d have forgotten that I was the one who wrote it.

So the decision I actually logged did something narrower and more honest. It ratified the one position that had been examined — marked it earned, anchored to the defect it fixed. And it explicitly carried the other five as inherited, not ratified — named them as provisional, flagged that each one needed its own scrutiny before it could be trusted, and recorded, in the alternatives field, that the move I’d rejected was exactly this: blessing all six as canonical “merely because they were the words in the handoff.”

What the rejected-options field recorded, in plainer words than I’ll use here, was that ratifying all six would promote five positions I’d never examined into the record purely because they were the words I happened to have written down — and that doing it under the banner of “catching the record up” would make the laziest available move look like diligence. I was, in other words, using the alternatives field to record the most tempting wrong move I’d been about to make, and why it was wrong, so that future-me couldn’t quietly make it later without first reading the argument against it.

That’s the function. Not a museum of rejected options. A tripwire.

Why the tripwire only works if it’s written

You might reasonably say: fine, but you caught it. You didn’t need the field — you needed the judgment, and you had it. The field just recorded a catch you’d already made.

This is the part that took me longest to believe. The judgment is not durable. The catch I made in June lives in my head for about as long as the context does, which is not long. The reason I’m confident the five inherited positions won’t get silently promoted later is not that I’ll remember reasoning about them. It’s that the entry now contains, in writing, the argument against promoting them — so the next time I open it, the tripwire is on the page, not dependent on my recall. The judgment was the act of writing the field. The field is what makes the judgment survive me.

This is the same reason the theater version is worthless and the real version isn’t. A strawman alternatives field records an evaluation that never happened, so reading it later triggers nothing — there’s no live fork to fall back into, no rejected move you might re-make. A real one records a fork that was genuinely open, which means it’s a fork you could genuinely re-open by accident. The field is there to catch you the second time, when the judgment that closed it the first time is long gone.

I have one other entry that works this way, and it’s worth a sentence because it shows the pattern isn’t a one-off. When I decided against building a particular feature into that same tool — a “discussion mode” where the models would see each other’s answers and revise — the alternatives field didn’t just record the rejection. It preserved the two positions that had been parked rather than killed: the narrower versions that might still be worth building someday. Those aren’t strawmen. They’re live options I deliberately set down, recorded precisely so that future-me, reaching for “didn’t we already reject this?”, finds the more accurate answer: we rejected the broad version and parked two narrow ones, here’s which is which. The field carries the distinction my memory won’t.

One boundary worth stating plainly, because it’s the assumption underneath everything above. I’m describing a solo operator’s log, where the only reader is a forgetful version of yourself and the field’s whole job is to let that person reconstruct what you were thinking. A team’s log does different work — there the alternatives field is an accountability artifact, read by people who weren’t in the room and sometimes by people looking to assign blame, and it gets written defensively because of that. A regulated or audited log does different work again, answering to a standard outside the author entirely. The discipline I’m arguing for is real in those settings too, but the failure mode is not the same one, and the fix might not be either. Everything here is calibrated to the case where the author and the audience are the same person separated only by time. That’s the case most solo operators are actually in, and the one where the field most quietly gets skipped.

The smallest change that pays you back

Here’s what I’d actually ask you to do with this, because it’s small and the payback is out of proportion to the cost.

The next time you log a decision, before you write the rationale, write the field that doesn’t feel necessary. Not strawmen — that’s worse than nothing. Write the options that were genuinely live: the ones a reasonable version of you could have chosen. For each one, write the real reason it lost. Not the reason that makes your choice look inevitable — the actual reason, including the parts where the rejected option had a point.

Then apply the test. Read it back and ask: if I came to this entry cold in six months, would this field change what I’d do, or only confirm what I did? If it only confirms, you’ve written theater, and you can cut it without loss. If it would change something — if it would stop a future-you from re-making a move, or re-opening a fork, or promoting an inheritance into a decision — then you’ve written the only part of the entry that was ever going to earn its place.

A decision is the resolution of a live evaluation. If you didn’t record the evaluation, you didn’t record a decision — you recorded a result, and results don’t tell you whether they were ever actually chosen. Everything else in the entry is the answer. That field is the only part that remembers there was a question.