Skip to content

Academy Primitive

Decision Clinics

Decision Clinics are short artifact-first drills. They do not teach the whole workflow. They force one call under pressure: inspect the packet, choose the move, and defend it before you see the reveal.

Clinic 01 Clinic 02 Clinic 03 Clinic 04 Clinic 05 Clinic 06 Clinic 07 Clinic 08 Back To Home

Step 1

Read The Packet

Start from artifacts, not explanation. Clinics should feel like opening someone else's run and deciding what matters first.

Step 2

Make The Call

Choose the model, the stop rule, the next move, or the refusal. The point is to commit before the answer is shown.

Step 3

Compare To The Reveal

After you write the note, compare your reasoning to the reference reveal and decide what evidence would change your mind.

All Clinics

# Clinic Focus
01 Public/Private Restraint Leaderboard restraint — visible gain vs. hidden risk
02 Leakage Or Signal? Feature availability — real signal vs. answer key
03 Review Budget Freeze Threshold policy under queue constraints
04 Overfit Or Underfit? Training curve diagnosis — opposite regimes, opposite fixes
05 Freeze Or Fine-Tune? Transfer strategy under small data budgets
06 Ensemble Temptation Marginal accuracy gain vs. operational complexity
07 Checkpoint Roulette Checkpoint selection from a training log
08 Threshold Under Asymmetric Cost Operating point when error costs are unequal
24 Published Result Trust Reproducibility judgment when a paper and a local run disagree

Why Clinics Exist

Topics teach one workflow move. Examples teach one runnable slice. Tracks teach the full connected workflow.

Decision Clinics do something different:

  • they start from artifacts instead of setup
  • they compress the lesson into one judgment
  • they train restraint, not just execution
  • they make hidden evaluation and weak-slice thinking feel normal

That makes them one of the clearest ways to keep AI Academy distinct from a general tutorial site.

Clinic Loop

Use the same loop every time:

  1. open the clinic
  2. read the artifact packet before the explanation
  3. write a short decision note
  4. reveal the reference answer
  5. state what evidence would justify changing your call

The note should stay short. Four to six sentences is enough if the reasoning is concrete.

What A Good Clinic Produces

A good clinic leaves behind:

  • one selected action
  • one rejected tempting action
  • one piece of evidence that drove the choice
  • one piece of evidence still missing
  • one short stop-or-continue rule

If the student only says which model "won," the clinic failed.

First Clinic

Start with Public/Private Restraint.

It is a strong first template because it trains three habits at once:

  • public gain is not proof
  • hidden evaluation matters more than visible rank
  • the right move can be to stop, not to keep searching

Suggested Sequences

Starter pack — evaluation discipline:

  1. Public/Private Restraint — leaderboard restraint
  2. Leakage Or Signal? — feature-availability discipline
  3. Review Budget Freeze — threshold and queue-policy discipline

Modeling judgment pack — model choice and diagnostics:

  1. Overfit Or Underfit? — diagnose before you fix
  2. Ensemble Temptation — accuracy vs. operational cost
  3. Threshold Under Asymmetric Cost — cost-driven operating points

Deep learning pack — transfer and training decisions:

  1. Freeze Or Fine-Tune? — transfer strategy under data constraints
  2. Checkpoint Roulette — select the right checkpoint from a training log

After Each Clinic

Route immediately into the matching workflow:

When To Use Clinics

Use a clinic:

  • after one example, before a full track
  • when the student keeps chasing the flattering score
  • when the weak slice is visible but the next move is unclear
  • when you want a short weekly judgment drill

Use a track instead when the student still needs the full workflow.