This example demonstrates how Baxxon serves as a robust backend for modern, interactive applications. 

### Behind the Scenes: The Visual Contract
This SPA entry point is located at `modules/index.js`. Because the URL (`/`) has no dot, Baxxon routes it here. However, the data you see is fetched from `modules/spa-responder.js`, demonstrating how pages and APIs share the same structure.

### Consistent API Logic
Every interactive element on this page (filtering, sorting, saving) communicates with a **JS Module** acting as an API. In Baxxon, there is no difference between a "Page" and an "API"—they both receive the same `bx` controller and use the same deterministic routing.

### Files as Database (TextDB)
The data you see in the table below is powered by **TextDB**. Instead of a complex SQL database, your records are stored as human-readable `.txt` files in the `data/` directory. 

