Exercise 1: A One-Time Free, Not a Live One — Possible Solution
====================================================================

WHAT rails generate scaffold PRODUCES
------------------------------
Per this chapter, rails generate scaffold produces a full set of real, ordinary source files for a given resource in one command - a model, a migration, a Controller with all seven RESTful actions, and ERB views for index, show, new, and edit.

WHY "ONE-TIME FREE" IS A MEANINGFUL DISTINCTION FROM DJANGO'S ADMIN
------------------------------
Per this chapter, Django's admin is a live, framework-owned interface that reads the model at runtime through admin.site.register() - there's no file to open and edit, and it stays automatically current as the model changes, for as long as it stays registered. Scaffold's own output is the opposite kind of thing: real files, generated once, that immediately become ordinary application code the developer owns and edits going forward, with no further connection back to the generator that produced them. One is a permanent, always-current framework feature; the other is a one-time starting point.

WHY THIS WORKS AS AN ANSWER
------------------------------
It correctly describes what scaffold generates, and correctly explains the meaningful distinction between a one-time code-generation event and Django's own ongoing, live, runtime-introspected admin interface.