
Aki Wijesundara
Manu Jayawardana

By the end you can say out loud which layer your problem lives on.



If you cannot write one sentence for what the current layer cannot represent, stay put.


Output shape is wrong. Tone slipped. A required field is missing. All fixable with wording, ordering, or a schema example.
No instruction fixes missing information. If you tell it more forcefully to be right, you get more forceful wrongness.


System misses it, or picks a lookalike. Quality drops as the thread grows.
No pre-load can represent that. If the plan changes after seeing a tool result, no context strategy fixes it.

Can it do the task once?
Can it do the task every time?

pass^8. GPT-4o agent, retail (tau-bench). ~60% drop from pass^1.
ReliabilityBest models now clear pass^1. pass^k curves are still far from ideal (2026).
CapabilityRuns diverge. Failures do not reproduce cleanly.
One sequential trajectory cannot cover them.


Every fix has a layer. When your fixes stop working, that is not a signal to fix harder. It is the layer's ceiling, telling you to climb. Read the sentence again. Believe it.

The prompt-layer fixes and the graph-layer fixes are less common than they feel. The two middle layers are where the actual engineering lives.


Write the sentence for what this layer cannot represent. If you cannot, the problem is still here.


We will tell you which layer it is on. This was the opening of week one. Bootcamp: build the loop with real evals. Measure pass^k on your system.
Nine weeks. Loop to production. Certificate for engineers and AI PMs. Cohorts start monthly.
Where this leadsPost one symptom. One line. Aki or Manu will diagnose the layer live and tell you where the fix lives.
Open floorSend us the symptom, the layer, the sentence, and the fix. We reply with an audio review before the bootcamp starts.
The receipt