The bait, then the rug-pull.
The opening line is an empathy mirror for every builder who has rebuilt their AI stack at least once: you feel behind because you are learning the wrong thing, not because you are slow. What follows is a 22-minute case that the right thing to learn has existed since the 1970s — it just does not make for a good demo reel.
Where the time goes.
01 · The FOMO hook
Opens with the AI overwhelm pain point — prompts went irrelevant, frameworks broke, courses outdated in 90 days. Establishes the core claim: you are learning the wrong layer.
02 · AI is not moving that fast
Reframe: the attention-is-all-you-need paper is almost 10 years old. Software fundamentals have been stable since personal computers. The problem is abstraction layer, not velocity.
03 · Origin story: Marine Corps and master's degree
Jake traces ICM to zero-defect avionics work in the Marines (fundamentals over expert opinion) and a 2022 master's program experiment organizing LLM outputs in files for context tracking.
04 · ICM defined: Folders Over Agents
Names the methodology: Interpretable Context Methodology. Folders over agents — the way you structure and route context is the real architecture. The agent just uses it. Architecture survives every model update.
05 · The five layers
Identity, Routing, Stage Contracts, Reference, Artifacts. No library to import, no framework name, no demo video. Just folders and discipline applied through the lens of AI.
06 · Proof: community results
30,000 members in two months, mostly free tier. 80 to 95 percent API and token cost reductions. Real wins: jobs, raises, clients, products that ship. Enterprise clients: Pacific Life, KPMG, UK government.
07 · The Lyceum pitch
Three cohorts — Technical (ship a production system), Business (AI-native company spec), Creator (content pipeline that runs without you). 100 seats per cohort, 300 total. Eduba certification.
08 · Program details and guarantee
Live sessions, lifetime recordings, private Discord, written curriculum. Guarantee: if you do not walk away with a working product, the team finishes it with you.
09 · Grace Hopper close and CTA
Parallel to Grace Hopper — working thing in hand, people said it was useless. Closes with waitlist CTA. Folders over agents, layers over libraries, methodologies over tools.
Visual structure at a glance.
Named ideas worth stealing.
ICM Five Layers of Context
- Identity
- Routing
- Stage Contracts
- Reference
- Artifacts
A five-layer hierarchy for organizing AI context in file systems. Identity defines what the AI is; Routing controls where information flows; Stage Contracts set expectations per step; Reference holds stable background material; Artifacts are working outputs.
Lines you could clip.
"You're not falling behind because AI is moving too fast. You're behind because you're learning the wrong layer."
"The agent is just the thing using the architecture."
"There's no demo video where I show you a sexy agent multiswarm system doing your job for you. There's no flashy framework name. There's no library to import."
"If you spend three months learning my processes, in five years you'll still be able to get value from it. If you spend three months learning the latest agent framework, nine months, most of it's gonna be either useless, absorbed, or you're gonna be relearning a whole new version of it."
Things they pointed at.
How they asked for the click.
"Join the waitlist now. There are only 300 seats total — 100 per cohort. When those seats are gone, they're gone."
Scarcity-anchored waitlist CTA with no price revealed — smart pre-launch move. Closes with a Grace Hopper parallel to reframe the invitation as joining a movement, not buying a course.
Word for word.
The layer underneath agents never needs rebuilding.
Agents, prompts, and frameworks expire — the folder structure and context routing they read from does not.
- Most AI tools become obsolete in 90 days because they are built at a high, volatile abstraction layer — the fix is to work one layer down, at context structure.
- The five-layer ICM hierarchy (Identity, Routing, Stage Contracts, Reference, Artifacts) gives any AI system a stable foundation regardless of which model or framework runs on top.
- Context routing — deciding deliberately what an AI reads at each step rather than dumping everything into one prompt — is the single highest-leverage change most builders can make.
- Organizing AI outputs into files from the start is how version control instincts transfer to AI workflows; the discipline matters more than the tooling.
- Cutting API and token costs 80 to 95 percent is usually an architectural fix, not a prompt fix — the waste comes from unstructured, repeated context.
- A system designed around durable fundamentals compounds as models improve; a system built around a specific framework resets every time that framework is deprecated.

































































