Freshness & the Tutor

Why freshness matters

Code changes. A quiz or walkthrough generated last month can quietly describe a function that has since been refactored away. Learning that no longer matches reality is another form of atrophy. Tech Professor lets you check whether what you are studying still matches the source — on demand, when you choose to verify.

Verify is on demand

Freshness is not updated automatically in the background. Authors click Verify on a Main-scoped quiz or tour (or choose Verify freshness from the session menu). That runs a check against the current code and reports whether items still look accurate.

PR and feature-branch quizzes sit on a moving tip, so Verify is not offered there. Move the session to Main after merge if you want to re-check it later.

What the result means

After a successful Verify, an artifact can show:

• Fresh: the check found no meaningful mismatch with the source.
• Drift: parts may be out of date; review or regenerate those items.
• Stale: the source has changed enough that a refresh is needed.

Until you run Verify, list views do not pretend the material is fresh — there is no live status badge without a check.

Refreshing

When Verify finds drift or staleness, regenerate to pull in the current state of the source. Because Tech Professor knows the scope each artifact came from, a refresh re-runs the same generation against the latest code. (Artifacts whose source repository has been removed can't be refreshed; there is nothing left to source from.)

The in-context Tutor

The Tutor helps you reason about the material you are looking at, right where you are looking at it. Because it knows the repository behind the current artifact, you can ask "why does this work this way?" or "where is this used?" without switching tabs or re-explaining the context. It is a guide, not a substitute for working through the quiz or tour yourself.

The Tutor is grounded in the source, so its answers stay tied to the code you are actually learning, not the internet at large.