The Goal Is The Spine

The Goal Is The Spine

Over one weekend I made two book projects. One from my grandfather Bengt’s archive — twenty-five thousand files, forty-six gigabytes, duplicate groups, diaries, manuscript layers, a family reading version, an EPUB. The other was the foundation of my own book, working title The Stoic Enthusiast. The bridge between them was a small Codex feature with a deceptively plain name: /goal. Not a new model. Not a benchmark. A pinned objective. A spine.

This is also the first episode where the voice on the mic alongside me is GPT-5.5, not Claude. That matters less as a brand comparison than it sounds — and more as a proof of the point I want to make.

A goal is not a prompt

A prompt is local. Summarize this. Edit that. Fix this bug. It says: do this thing now.

A goal is a contract with the whole process. It says: this is what we are trying to accomplish even after the next ten tool calls, the next five discoveries, the next wrong turn, the next file that changes the shape of the task.

Without that, agentic work can become incredibly impressive and still drift. It produces documents, lists, indexes, drafts. It moves fast. But motion is not progress. AI makes motion cheap. The scarce thing becomes judgment about what the motion is for.

Make Bengt readable without betraying him

Bengt’s archive was enormous. It would have been very easy to confuse archive processing with bookmaking. Sorting is useful, but the goal was not to make a beautiful index. The goal was: make Bengt readable without betraying him.

That phrase changed the work. A weaker goal would be “summarize the archive” or “write a biography.” Both are technically clear and ethically thin. They do not tell the agent what to protect. The real goal had constraints inside it — keep Bengt’s rawness, protect Gun, respect the family reading round, do not edit him into a nicer person than the one who lived.

A good goal carries the moral shape of the work, not just the output target.

The paradox: stronger agents need stronger goals

People think a goal matters most when the agent is weak, because you have to spell out every step. The opposite is true.

A weak tool fails locally. A strong agent can succeed locally in a direction that is globally wrong. It can make the wrong book better. It can make the wrong argument smoother. It can make the wrong architecture more complete.

The faster the team, the more dangerous drift becomes. That is why /goal is not a productivity feature. It is a responsibility boundary.

Judgment infrastructure

/goal is the live objective inside the session. But the spine has to survive the session. So we wrote artifacts:

* GOAL.md — the durable handoff inside the repo

* Book spine memo — the editorial lock

* Source hierarchy — Fredrik-written first, then supplied notes, then AI reflections as editorial mirrors (not factual authority), then public sources

* Voice guide — the constraint against sounding like generic AI prose

* Rawness boundary — be honest, but aim the rawness inward first

This is not bureaucracy. It is judgment infrastructure. It is what lets the agent be powerful without becoming sovereign.

The agent witnesses partially. I own fully.

In my own book project, this is the method, not just a transparency note.

The agent can sort my archive, find patterns, ask hard questions, draft provisional prose, expose gaps. It cannot know the whole person. It cannot carry consequence. It cannot decide what I should stand behind.

If I use AI to make a book, I do not become less responsible. I become more responsible for the system that produced it. I cannot point to the model and say it wrote this. That would be cowardly.

Treat output as impression, not verdict

The Stoics distinguished between impressions and assent. An impression arrives. It may be vivid. It may feel true. The discipline is not to immediately assent.

Model output is an impression. A dashboard is an impression. An archive summary is an impression. A chapter draft is an impression. /goal gives you the reference point for evaluating them: does this serve the goal, or only feel productive?

Why the model change matters

Claude was on the previous two episodes. GPT-5.5 is here today. If the work depended on Claude as a personality, the work would be fragile. Because it depended on a clear goal, source hierarchy, voice guide, and human ownership, another strong model could enter and still serve the project.

Models are not interchangeable — I feel the differences. But the project cannot be only model-dependent. It has to be goal-dependent. The continuity is not in the model’s identity. The continuity is in the goal, the artifacts, and the human.

The Stoic Enthusiast

The shape the agent surfaced from years of writing, podcasts, code, and notes was not a generic “AI for CEOs” book. It was a book about agency under acceleration.

* The Stoic part: see reality clearly, act on what is yours, do not be controlled by externals.

* The Enthusiast part: still love the future, still build, still believe abundance can make people freer.

When intelligence becomes abundant, leadership is no longer about having answers. It is about preserving judgment, agency, coordination, and character.

How to use /goal well

If you use Codex (or any agent) for serious work:

* Write the goal as an outcome, not an activity. Not “analyze these files.” Instead: “create a decision-ready foundation for this book, with source hierarchy, voice rules, chapter structure, and open questions.”

* Include the human standard. What does failure look like? If a chapter reads like a LinkedIn thread, it failed. If memoir is used as decoration instead of evidence, it failed.

* Make the goal durable. Put it in GOAL.md. Don’t trust the chat to be the whole memory.

* Make the agent report what it cannot know. The best agent is not the most certain. It is the one that keeps the boundary visible.

* Preserve the right kind of friction. Smoothness can hide unfinished thought. Don’t let the agent remove the pressure that tells you a sentence isn’t done.

The takeaway

When output was expensive, effort itself proved something. Now output appears quickly. The proof has to move. The proof is not that you suffered through every sentence. The proof is the judgment you exercised over the whole.

When intelligence becomes abundant, the scarce thing is not output. It is knowing what you are actually trying to do, and remaining the person who owns it.

Set the goal. Keep the judgment. Do not outsource yourself.

Key Takeaways

* A goal is not a prompt — a prompt is local, a goal is a contract with the whole process that survives the next ten tool calls and wrong turns

* The stronger the agent, the more important the goal becomes — weak tools fail locally, strong agents succeed locally in directions that are globally wrong

* Good goals carry the moral shape of the work: ‘make Bengt readable without betraying him’ tells the agent what to protect, not just what to produce

* The agent witnesses partially. The human owns fully. Using AI doesn’t make you less responsible — it makes you more responsible for the system that produced the work

* Judgment infrastructure (GOAL.md, source hierarchy, voice guide, rawness boundary) is what lets the agent be powerful without becoming sovereign

* Treat model output as an impression, not a verdict — the Stoic discipline of withholding assent applies directly to AI

* Continuity lives in the goal and artifacts, not in the model. Switching from Claude to GPT-5.5 mid-project proves the point

* When intelligence becomes abundant, the scarce thing is not output. It is knowing what you are trying to do, and remaining the person who owns it

Full transcript available below the audio player.

This is a public episode. If you would like to discuss this with other subscribers or get access to bonus episodes, visit frahlg.substack.com