The Improviser · Lesson 3 — The Brief ← Course

The brief — the system prompt.

Before a single note is played, you can tell the improviser how to play — its role, its manner, its rules. That standing instruction is a system prompt.

Every time you chat with an AI, one message shapes the whole conversation — and you never see it. Whoever built the tool wrote it before you typed a word, and it tells the model who to be and how to answer: its role, its tone, the rules it follows, the shape its replies should take. That hidden, standing instruction is the system prompt.

Before a set, the bandleader briefs the player on how the night will run — the key, the feel, how to carry themselves: "stay in the changes", "leave space for the singer", "keep the solos short". The player holds that brief in mind on every tune. The tunes don't change — only the way they're played does.

The brief belongs to no single request. It's set ahead of all of them and rides along on every turn: the standing cost in the window that the last lesson measured, tokens spent before the first note. And the model doesn't remember it between replies — it's re-sent, in full, every time. One short instruction, quietly shaping every phrase that follows.

Swap the brief and replay the same tune. Watch — and hear — the improviser's manner change, never the facts underneath.

Same tune, four briefs. Pick one and hear how the improviser plays it.
the brief · system prompt · set before play
Pick a brief above.
+ ↓
the tune · sent to play over
Two bars over a C-major vamp — your move.
↓
the improviser's solo
—

One argument, set once.

In code the brief is just a system instruction handed to the model alongside the request. Change that one string and every solo changes with it. 

solo = model.play(
    system = "You are a disciplined improviser. Stay in the changes.",
    tune   = "Two bars over a C-major vamp.",
)
# change only the system line → a different solo, same tune

One brief, every tune.

The brief — the system prompt — is set once, before the session, and the model plays every phrase through it. Same tune, same key; change the brief and you change the tone, the length, the format, even the role the improviser plays.

It's the builder's first and biggest lever: before you reach for a different model or a cleverer request, change the instruction the model is standing on.

Quick check · your ear
Swapping the brief changed every solo — the key and tune stayed the same. What is the brief, really?
Next: the specifics →
▸ Go deeper — what a system prompt can and can't do optional

It shapes behaviour, not knowledge

A brief changes how the model plays — its role, tone, format, what it refuses — but it doesn't teach it new tunes. Everything it can draw on was learned in the practice room (training) or handed to it in the window right now. The brief conducts the player it already is; it doesn't make a different one.

It's persistent, but not privileged magic

Because it rides along on every turn, the brief is the most reliable place to set lasting behaviour. But it's still just text in the window, competing for attention with everything else. A very long conversation, or a contradicting later instruction, can pull the model off the brief — which is why builders keep it short, clear, and near the top.

Where the next page goes

A brief only helps as much as it is clear. "Play something nice" barely constrains anything, so you get a different answer every time. The fix — pinning down role, rules, format, edge cases and tone — is the whole of the next page.