Skip to main content

Current operating model · Updated July 10, 2026

How I Work With AI

My AI stack got smaller as the general-purpose systems learned to use tools, work across files, and stay with a task longer. The useful question is no longer “which app can do this?” It is “which system should own this step, and what context does it need?”

The model is not the operating model. The operating model is the loop around it: source material, tools, boundaries, verification, and a durable place for the work to live.

The current loop

Four jobs. Fewer handoffs.

These are roles, not rigid tool boundaries. The point is to keep the decision thread intact while each system does the work it is best positioned to finish.

01 · Frame

ChatGPT

Think above the artifact

I use ChatGPT for operating models, product strategy, research synthesis, process architecture, and the conversations where the problem is still taking shape.

Best for: Ambiguity, competing frames, and decisions that need a clear throughline.

02 · Build

Claude + Codex

Work inside the system

This is the execution layer: repositories, terminals, browsers, files, tests, and long-running work that has to end in a finished artifact rather than a persuasive answer.

Best for: Implementation, inspection, debugging, and verified multi-step delivery.

03 · Capture

PLAUD + source files

Keep the raw signal

Ideas and conversations are captured before they are polished. The transcript or source artifact stays available so later synthesis can be checked against what was actually said.

Best for: Voice notes, meetings, early requirements, and evidence that should not be overwritten.

04 · Preserve

Project repos + curated knowledge stores

Give the work a memory

Important work lands in a durable home with decisions, source material, current state, and clear boundaries. The model changes. The context should survive it.

Best for: Long-running projects, repeatable workflows, and anything another agent may inherit.

GPT-5.6 routing

Sol, Terra, and Luna are lanes, not a leaderboard.

OpenAI’s durable tier names make the routing decision visible. Sol is the flagship. Terra balances capability, speed, and cost. Luna is the fastest and most efficient. In ChatGPT Work and Codex, the useful choice is the lane that can finish the task with the least total review debt.

Flagship reasoning

Sol

The highest-capability GPT-5.6 tier for complex professional work across coding, research, knowledge work, computer use, science, cybersecurity, and design.

Route here when

  • The problem is ambiguous or cross-functional
  • Several tools or sources must be coordinated
  • A plausible but wrong answer would be expensive

Balanced execution

Terra

The capability, speed, and cost balance in the family. This is the useful default for everyday professional work that still needs planning and tool use.

Route here when

  • The job is multi-step but well framed
  • You need dependable tool use without flagship cost
  • The output is important and straightforward to review

Fast, efficient throughput

Luna

The fastest and lowest-cost GPT-5.6 tier. Its value is not “less important work.” It is bounded work where speed, volume, and easy verification matter most.

Route here when

  • The transformation is tightly specified
  • The result can be checked automatically or at a glance
  • You are classifying, extracting, formatting, or fanning out

Sol is rolling out in standard ChatGPT reasoning modes. Terra and Luna are available in ChatGPT Work, Codex, and the API rather than as standard chat model-picker options.

Claude’s lane

Agentic execution still deserves a specialist.

Claude remains where I build and do. Sonnet 5 strengthened the part of the product I already valued: sustained coding, browser and terminal use, tool calling, and the ability to carry messy work through the verification pass.

ChatGPT and Claude overlap more than they used to. I still get better results when I give them different jobs. ChatGPT holds the higher-altitude frame. Claude works closer to the artifact. Codex joins that execution layer when the repository and the release path are the center of the task.

The handoff rule

Do not hand off a polished answer. Hand off the source, the decision, the boundary, and the definition of done.

That is what lets another model continue the work without inventing the thread you forgot to preserve.

The agent test

Five questions before I call it an agent.

A chat with instructions is useful. An agent is a repeatable system with a trigger, a process, tools, context, and explicit stopping rules.

01TriggerWhat starts the work, and should it run at all?
02ProcessWhat steps make the output repeatable instead of lucky?
03ContextWhich sources are authoritative, current, and allowed to mix?
04ToolsWhat can the agent read, change, create, or send?
05GuardrailsWhere must it stop, ask, verify, or hand control back?

What I retired

The old Agent Bible became the wrong artifact.

It proved that dense information could become interactive. It also froze a moment when the tool layer was fragmented and hypothetical use-case catalogs felt useful. The market moved. My own practice moved faster.

  • A giant catalog of hypothetical agent use cases
  • Choosing the automation platform before defining the job
  • Permanent model rankings in a market that changes every month
  • Adding another orchestration layer when the general tool can already finish the work

The code remains in the repository history. The public page now reflects the operating model I would actually defend.

Source shelf

Capability and availability claims were checked against the current GPT-5.6 announcement, ChatGPT availability guide, workspace-agent guide, and Claude Sonnet 5 release. The curation model was informed by how FutureTools separates recommendations from the full archive and how AI Daily Brief keeps current changes concise. The structure and point of view here are my own.