new lesson: Terminal lesson 1

[mu1titudes]

Written by ToddlerNFT

[tpompon]

📚 Lesson review — jupiter-terminal-1.mdx

Automated review by the Academy lesson agents. Read-only — nothing was changed. Reviewed commit 9ea91aa.

Summary: 🔴 3 blockers · 🟡 13 suggestions across 4 checks

Integrity (illustrations · video · links · frontmatter · glossary)

Verdict: 2 blockers, 3 suggestions

Sev	Where	Finding	Suggested fix
🔴	line 51 / T1_bonding_lifecycle.png	broken illustration (404, confirmed on retry)	re-upload to the CDN path, or correct the src
🔴	line 78 / T2_safety_checklist.png	broken illustration (404, confirmed on retry)	re-upload to the CDN path, or correct the src
🟡	lines 51, 78	illustrations use .png; repo convention is .avif	re-export as .avif and update src
🟡	line 49	AMM, liquidity pool not wrapped in <Term>	wrap with <Term id="amm"> / <Term id="liquidity-pool">
🟡	line 63	"bonding curve" has no glossary entry	add bonding-curve term and wrap first use

🔎 Accuracy vs docs.jup.ag

Verdict: ✅ PASS — 0 blockers, 2 to verify
Docs consulted: terminal index / alphascan / token-discovery / token-page / launchpad-screener-and-runners / risks · vrfd index / verified-insights

Sev	Lesson says (line)	Docs say (source)	Action
🟡	"Cooking … tokens currently gaining momentum. The default view" (l.38)	docs: "tokens most purchased in the past 24 hours that also have a positive price change"; no "default view" mention	update description; confirm default tab with team
🟡	"Top 10 Holders % … Ideally below 50%" (l.73)	docs cite no specific threshold	confirm the 50% benchmark with team or remove the number

✍️ Quality (language · coherence)

Verdict: 1 blocker, 8 suggestions

Sev	Where	Finding	Suggested fix
🔴	line 89	comma splice: "Pre-migration tokens have thin liquidity, small trades can move price 10% or more."	split into two sentences
🟡	line 20	intro paragraph crams "what Terminal is" + lesson scope	split into two short paragraphs
🟡	line 38	Cooking bullet breaks parallel structure with extra aside	tighten to match other bullets
🟡	line 45	"other relevant metrics depending on the view" vague	give a concrete metric example
🟡	lines 63–65	Organic Score caveat reads as inline afterthought	move to a bold note / blockquote
🟡	line 63	"Organic Score" defined twice in consecutive sentences	merge into one sentence
🟡	line 75	"DB" abbreviation introduced but never reused	define both DB/DS clearly or drop DB
🟡	line 90	Sniper-bots bullet is a redundant run-on	trim to two short sentences
🟡	throughout	no <Term> components	wrap "bonding curve" and "AMM" on first use

Quiz (proposed)

Verdict: proposed 4-question quiz

• Q1 — Terminal vs Swap
• Q2 — AlphaScan "Soon" column
• Q3 — Freeze Authority safety indicator
• Q4 — Organic Score meaning and limitation

{
  "questions": [
    {
      "question": "What is the key difference between Jupiter Swap and Jupiter Terminal?",
      "options": [
        "Terminal supports more blockchains than Swap",
        "Terminal adds discovery feeds, safety indicators, and launch screeners on top of the same routing engine",
        "Swap is only for memecoins while Terminal handles all tokens",
        "Terminal requires a separate wallet connection from Swap"
      ],
      "correctAnswer": 1,
      "explanation": "Terminal is a discovery and intelligence layer built on the same routing engine as Swap, adding feeds, screeners, safety checks, and quick-execution tools designed specifically for memecoin trading."
    },
    {
      "question": "In AlphaScan, what does it mean when a token is listed in the \"Soon\" column?",
      "options": [
        "The token will be delisted from Jupiter soon",
        "The token is about to be audited by the Jupiter team",
        "The token is approaching 100% bonding curve completion and migration to an AMM pool",
        "The token was recently bonded and now trades with deeper liquidity"
      ],
      "correctAnswer": 2,
      "explanation": "The \"Soon\" column in AlphaScan shows tokens whose bonding curve percentage is near 100%, signaling that migration from the launchpad to a standard AMM liquidity pool is imminent."
    },
    {
      "question": "Which of the following safety indicators, if NOT revoked, means the token creator can freeze trading on individual wallets?",
      "options": [
        "Mint Authority",
        "Dev Holding %",
        "Bonding Curve %",
        "Freeze Authority"
      ],
      "correctAnswer": 3,
      "explanation": "Freeze Authority allows the creator to freeze trading on individual wallets; it should be revoked on any token you consider safe, as an un-revoked Freeze Authority is a direct rug-pull vector."
    },
    {
      "question": "What does a high Organic Score indicate about a token, and what is its limitation?",
      "options": [
        "It guarantees the token is free from bot activity because Jupiter verifies every wallet on-chain",
        "It means the token has passed a full security audit and is safe to trade",
        "It estimates more activity comes from real wallets than bots, but sophisticated bot networks can still inflate it",
        "It shows the token has above-average 24-hour trading volume across all DEXes"
      ],
      "correctAnswer": 2,
      "explanation": "Organic Score is a heuristic that estimates genuine user activity versus automated trading, but the lesson notes that sophisticated bot networks can still inflate the score, so it is not a guarantee."
    }
  ]
}

---

🤖 Ready-to-use prompt for Claude Code

Copy this into Claude Code on the PR branch to apply the fixes:

Apply the Jupiter Academy lesson review for lessons/jupiter-terminal-1.mdx.

Blockers (must fix):
1. Line 51: illustration T1_bonding_lifecycle.png returns 404 — re-upload to the CDN path or correct the src.
2. Line 78: illustration T2_safety_checklist.png returns 404 — re-upload to the CDN path or correct the src.
3. Line 89: fix the comma splice — "Pre-migration tokens have thin liquidity. Small trades can move price 10% or more."

Suggestions (apply if you agree):
1. Lines 51 & 78: convert illustrations from .png to .avif to match repo convention.
2. Wrap glossary terms in <Term>: AMM (l.49), liquidity pool (l.49), bonding curve (add a glossary entry first).
3. Line 38: update the Cooking description to match docs ("most purchased in the past 24h with positive price change") and confirm whether it is the default tab.
4. Line 73: confirm the "ideally below 50%" Top-10-Holders benchmark with the team or remove the specific number.
5. Line 20: split the intro into two short paragraphs.
6. Line 38: tighten the Cooking bullet to match the parallel structure of the others.
7. Line 45: replace "other relevant metrics depending on the view" with a concrete example.
8. Lines 63–65: move the Organic Score caveat to a bold note/blockquote; merge the double definition.
9. Line 75: define both DB/DS clearly or drop the unused "DB".
10. Line 90: trim the Sniper-bots bullet to two short sentences.

Then commit and push to this PR branch. Do not invent facts — cite docs.jup.ag where the review did. Keep the Academy tone (educational, no financial advice).

(Quiz proposal in the comment above is for the app repo — not this content repo.)

_{Re-run with /review-lesson-pr 29 after pushing — this comment updates in place.}

[mu1titudes]

Agentic feedback addressed. No further comments