Exercise 1: Standard-Library sqlite3 as a Reflection of This Course's Own Throughline — Possible Solution
====================================================================

THE FACT ITSELF
------------------------------
Per this chapter, "SQLite support is genuinely built into Python's own
standard library — no pip install required at all... neither MySQL
nor Postgres connectivity ships in Python's own standard library; both
require a third-party package (mysql-connector-python, psycopg2) just
to connect."

WHY THIS IS A SMALL BUT REAL REFLECTION OF THE COURSE'S THROUGHLINE
------------------------------
This course's own throughline, stated in sqlite1-1, is that SQLite
exists to let "a single application embed a real, full-featured,
ACID-compliant database directly into itself, with zero server
infrastructure required at all." Connecting to MySQL or Postgres
requires a network client capable of speaking that specific server's
own wire protocol — inherently a piece of NETWORKING functionality,
which reasonably lives outside a general-purpose language's own
standard library as an optional, install-when-needed package, since
not every program needs to talk to a networked database server.

SQLite, by contrast, requires no network protocol at all — connecting
to it is just opening a local file through an embedded library, which
is conceptually much closer to ordinary file I/O than to networked
communication. Because of this, it makes sense that Python's own
standard library — which already includes ordinary file-handling
capability as a matter of course — would also include SQLite support
directly, the same way it includes other basic, universally-useful
local capabilities, without needing a separate installable package the
way genuinely networked database access does.

THE CONNECTION TO THE THROUGHLINE
------------------------------
This is a small, concrete, real-world confirmation of sqlite1-1's own
architectural claim: SQLite really is treated, at the language-tooling
level, as being closer in kind to local file access than to networked
database connectivity — exactly the distinction this course has been
making all along. The standard-library inclusion isn't a coincidence
or an arbitrary convenience; it's a natural consequence of SQLite
genuinely not requiring the kind of networked, protocol-specific
client machinery MySQL/Postgres connectivity does.

WHY THIS WORKS AS AN ANSWER
------------------------------
It doesn't just restate the fact — it explains WHY the fact is true
(SQLite's own embedded, non-networked nature makes it a natural fit
for a standard library the way networked protocols aren't), and
explicitly ties that reasoning back to sqlite1-1's own architectural
throughline rather than treating it as an unrelated trivia point.