From the button to the row.

Node is the engine outside the greenhouse

The browser runs JavaScript inside the page. Node runs it on the server, where the disks, the database, and the network live. It can watch many events without stopping the line for each one.

Packages, tables, and the four moves

A package is a tool someone else already built. package.json is the list of seeds and versions. node_modules is the barn they land in. A table is rows and columns with a name. Create plants a row, read inspects it, update changes it, delete clears it. The browser asks. The server checks the ask and is the only one that talks to the table.

Secrets stay in the barn

If a provider key is in the page, anyone can read it and spend your account. The browser sends the question to your server. The server reads the key from its own environment and calls the provider. The class used that pattern. This page does not reprint a key, not even a fake one.

MCP, the next idea in that class, is a standard hitch so a model can use a database or another tool without a fresh pile of glue for every product.