R109 · Agent principles and patterns › Workflows over agents

Jake Van Clief, Eduba and his central theses

Read the original

deterministic-workflowsagent-workflowscontext-engineeringpsychology-of-programmingeducationagent-platformscompany-research

Jake Van Clief ("Clief") is a USMC veteran and Edinburgh-trained founder whose company Eduba sells AI training, consulting and a multi-party AI workspace. His work rests on one idea: AI is the interpreter inside a program people design, so structure, intent and human review matter more than agents.

Who he is

"Clief" is Jake Van Clief, who runs the Clief Notes Skool community and is Founder and CEO of Eduba (Crunchbase).

Eduba

Eduba is Van Clief Media LLC (Palm Coast, Florida), a "veteran-owned AI consulting and training firm" with one software product and a learning ladder that feeds it (eduba.io; Terms, updated 14 July 2026). Crunchbase places the founder in Edinburgh.

PartWhat it isNotes
Consulting and trainingWorkflow teardown by department, then training staff to buildSelf-reported: Pacific Life and Colgate-Palmolive, 600+ trained, "95% adoption after 30 days"; KPMG UK, 40+ executives (works)
chat.eduba.io"A workspace for thinking with humans and agents in the loop"Units are incubators: a topic, a system prompt, Markdown context files and participants, who can be people or agent personas (features)
Enterprise tierOrg admins define personas over admin-approved model providersRole-based access per org and incubator, full message history, per-org subscription with an "ask allowance and credit balance" (enterprise)
Edubaware, LedgerNamed in the Terms: a platform for "structured AI context systems" and a talent placement siteUnclear whether Edubaware is the chat product
The LyceumTwelve-week, capstone-based certification, cohorts by skill levellyceum.eduba.io
Clief Notes (Skool)Free community and courses: Foundation, Archive, Implementation Playbooks, Building Your Stack, Vault"12,500+ members" on eduba.io, versus 30,000+ claimed in his course; neither verified

The workspace has no public price list and names no models. Explore (hierarchical knowledge), card actions and flashcards generated from your own incubators are its listed features. The Terms exclude HIPAA, FISMA and GLBA data and say hosting is US-only.

For engineers, the product is ICM made multi-party: an incubator is a scoped context (system prompt plus Markdown files) shared by humans and model personas, the same "right files for this job" idea as a routed folder.

Central theses

Six claims recur across the paper, essays, videos and Eduba's sales copy. They stack: the first is the premise, and the others follow from it.

  1. AI is part of a program, not the program. A program is instructions, something that runs them, and surviving state; the model is only the runner. "We are turning English into a programming language whether we meant to or not" (Substack, 20 Oct 2026). So the engineering lives in the instructions and state, not the model.

  2. You rarely need agents; you need structure. "Agent" is a naming convention for a bundle of prompt, tools and context. One model with a read/write/search harness, numbered stage folders, a routing CLAUDE.md/AGENTS.md and per-stage CONTEXT.md contracts replaces a multi-agent framework for sequential, human-reviewed work. Principles: one stage per job, plain text as the interface, layered context loading, every output an edit surface, "configure the factory, not the product" (ICM paper; video).

  3. Augment, don't just automate. Drawn from Engelbart's 1962 Augmenting Human Intellect and Weinberg's 1971 "Levine the Tailor": software has made people fit it; AI is the first layer that can bend software to the person. One-pass efficiency gains are "barren"; value comes from regenerative human-tool interaction (video; Engelbart walkthrough).

  4. Most workflows do not belong to AI end to end. Break each department's work apart and sort every step into traditional software, rule-based logic, AI, or "do not build this". Steps that stabilize become scripts; a check (person, script or small model) ends every step (eduba.io; icm-architect).

  5. Value migrates up the abstraction ladder. Three layers of AI use: prompts to outputs (the "book"), built flows (the "movie"), and flows improved from reviewed results (the "game"). Raw output commoditizes, so value moves to process, context and judgment; beware building what the platform will absorb next release (video).

  6. Framing and intent outrank code. Psychology of programming matters more than programming for the next decade; human flexibility "abstracts up. Every time", and "the need for why never goes away". Teach principles that survive platform changes, and put governance in the build, not after rollout (R015; Substack; eduba.io).

The stance is anti-hype by design: Eduba's tagline is "We start with truth, not hype", and its KPMG case asks "when should the answer be no?". Older Substack titles ("The Orchestration Imperative", "The Rise of Computational Orchestration", 2025) show the same line before ICM: AI rollouts fail because nobody orchestrates the work around the model.

Assessment for engineers

The architecture claims are sound and match what strong harness teams already do; the evidence behind the bigger claims is thin and self-reported.

What holds

What is unproven

Failure modes to expect

Review checklist

Use these when a team proposes an ICM-style folder workflow or a tool like Eduba's workspace.

Sources

Connections

See R109 on the knowledge map

Part of the Research notes on nowucca.com. Figures and claims are the source's own unless the summary says otherwise.