87. The JEPA Family and Your Prompts
Consolidate the JEPA idea - selectivity of prediction - into concrete prompt-engineering habits, and know where the whole JEPA family lives in the TPEE papers library.
By Jacques Botte, founder of Toptronic®. Last updated 19 September 2026.
The lesson
Two lessons, one idea: predict what matters, drop what does not. This lesson turns that idea into prompt-engineering practice and maps the JEPA family as it exists in the TPEE library of scientific papers - the same library rendered as a browsable date timeline on tpee.app/papers.
Start with the contrast. A generative model spends capacity reproducing the surface: every pixel, every sample, every token, including the noise. A joint-embedding predictive model predicts only the abstract content of what is missing - the semantic part - because its training signal lives in representation space. LeCun's 2006 energy-based-learning tutorial (in the library) framed this decades earlier: models should judge plausible from implausible, not regenerate reality.
The library holds the family tree. Non-contrastive joint embedding: Barlow Twins (2021) and VICReg (2022) taught two views of the same thing to agree without negative pairs. Images: I-JEPA (2023) and DINOv2 (2024, in the library) - DINOv2 showed joint-embedding features transfer to tasks their training never mentioned. General: data2vec (2022, in the library) applied prediction-in-representation-space to speech, vision and language at once. Video and robotics: MC-JEPA and V-JEPA 2. Even edge hardware: JEDI (2026) distills JEPA models downward.
Now the prompt-engineering payoffs, as habits. (a) Name your target blocks: instead of "improve this prompt", say exactly which sections should change and what "better" means - you are choosing the semantic targets, the JEPA masking strategy in words. (b) Feed an informative context block: I-JEPA's context must be spatially distributed and informative; your Context and Data sections must carry real evidence, not filler. (c) Reject generative filler: when a model pads answers with low-information tokens, tighten Format and Audience - you are telling it which parts of output space are semantic.
Critique prompts benefit too. When you ask a model to critique a draft (lesson 84's pattern), a JEPA mindset tells it what NOT to flag: unpredictable stylistic detail is not an error. Ask it to check the predictable structure - requirements met, ordering, missing constraints - the semantic skeleton, not the texture.
A caution against over-extending the analogy. JEPA is a training architecture; your prompt is inference-time conditioning. What transfers is the design philosophy - selectivity, rich context, semantic targets - not a claim that prompting your LLM "is" running a JEPA. Keep the boundary honest in your own writing: "my prompt uses JEPA" is wrong; "I applied JEPA's target-selection principle" is right.
Where to go next, all inside TPEE and its library: browse tpee.app/papers and search for JEPA to see every paper in this three-lesson arc on the date timeline; revisit lesson 84 for the self-critique loop that pairs well with targeted evaluation; and remember the standing rule - the papers, the timeline and any JEPA model live OUTSIDE TPEE. This course is static offline text; TPEE makes no network call and speaks to no MCP server, and any model you study runs in its own separate application.
A crime analyst uses TPEE to state exactly which sections of a briefing should change before the critique pass runs.
A quality officer at a food plant applies target selection in TPEE, asking only for missing constraints and unmet requirements.
A curriculum lead writes a TPEE prompt naming the target blocks of a lesson plan, so the model improves the structure instead of rewriting everything.
A credit analyst drafts a TPEE critique prompt that checks the summary against the requirements list and ignores stylistic detail.
A metadata librarian uses TPEE to name which catalogue fields need work, giving the model a clear target instead of a general request.
An advertising copywriter tightens the Format and Audience sections in TPEE to stop a model padding short copy with filler.
A junior developer writes a TPEE prompt that asks the model to check the semantic skeleton of a change: requirements met, ordering, and missing constraints.
A policy analyst drafts a TPEE prompt that asks which requirements are unmet, leaving the wording style alone.
A program officer supplies a rich evidence block in the TPEE Context section so the model works from real facts rather than assumptions.
A research assistant writes a TPEE prompt with a short, informative context block, giving the model enough evidence to run a focused critique.
Check yourself
Question 1: How does joint-embedding prediction differ from generative prediction?
- It predicts representations of what is missing; generative models reconstruct the raw output itself — correct
- It is another name for GPT-style next-token prediction
- It requires contrastive negative pairs like SimCLR
- It only works on audio
Answer: It predicts representations of what is missing; generative models reconstruct the raw output itself
JEPA (in LeCun's energy-based-learning framing) predicts in representation space and discards unpredictable detail; generative models spend capacity reproducing every token or pixel, much of it noise.
Question 2: How should a TPEE user apply the JEPA mindset when writing a prompt?
- Ask the model to output everything it knows
- Specify exactly WHICH aspects of the output matter and provide an informative context block, letting the model drop irrelevant detail — correct
- Avoid all structure so the model can be creative
- Use only one-word prompts
Answer: Specify exactly WHICH aspects of the output matter and provide an informative context block, letting the model drop irrelevant detail
JEPA's lesson is selectivity: define semantic targets and a rich context block. In TPEE terms: a sharp Format/Audience pair plus a rich Context section beats dumping everything.
Question 3: How does TPEE work with JEPA-style models such as V-JEPA 2?
- TPEE downloads and runs V-JEPA 2 in the background
- TPEE calls a model API when you select a JEPA model
- TPEE never calls them: lessons are static offline text and any model runs in a separate external application; you copy prompts manually — correct
- TPEE ships the V-JEPA 2 weights in TPEE_Data
Answer: TPEE never calls them: lessons are static offline text and any model runs in a separate external application; you copy prompts manually
TPEE is strictly offline: no network calls, no MCP. Papers and models referenced in lessons live outside TPEE; browse the papers on tpee.app/papers and run any model in its own separate application.
← Previous lesson · All 91 lessons · Next lesson →
The full course — 91 lessons and 273 quiz questions — ships inside the app. Get TPEE to study it offline.