Restore the Space card (sdk: static)

README.md

@@ -0,0 +1,48 @@
+---
+title: Event Horizon
+emoji: 🌌
+colorFrom: indigo
+colorTo: purple
+sdk: static
+app_file: index.html
+pinned: false
+license: mit
+short_description: Ask a database a question in English, in the browser
+---
+
+# Event Horizon
+
+A database rendered as three stacked skies — tables, the semantic model above
+them, business rules above that — plus a live [Swan](https://github.com/maxdemarzi/swan)
+engine you can ask questions of.
+
+**Everything runs in this tab.** DuckDB, the Swan extension and PyRel are
+WebAssembly; the model, the 117 rules and the query all execute in the browser.
+Schema rendering, few-shot selection, the sandbox, error translation and retries
+are all in the browser too.
+
+The one thing that leaves is the prompt, which goes to a fine-tuned 1.5B model to
+be turned into PyRel. Two hosts are tried in order — a
+[proxy](https://huggingface.co/spaces/maxdemarzi/black-swan-proxy) onto f16
+weights on a GPU, then a [CPU Space](https://huggingface.co/spaces/maxdemarzi/black-swan-pyrel)
+running the same model quantized — and the status line names the one that
+answered, `gpu` or `cpu`, with `↓` when it fell back.
+
+The proxy exists because ZeroGPU bills GPU time to a Hugging Face account, and an
+unauthenticated caller gets 2 minutes a day against a PRO account's 40; a request
+from your browser names no account, so it runs out almost immediately. The proxy
+lends one. That daily quota is shared by everyone reading this, so falling back
+to `cpu` is normal rather than a fault. `?nlq=off` disables generation entirely and the rest still
+works — you just write the PyRel yourself.
+
+Source: [github.com/maxdemarzi/event_horizon](https://github.com/maxdemarzi/event_horizon)
+
+## First visit is slow
+
+The engine is ~115 MB of Pyodide, DuckDB and Swan, fetched once and then cached
+in the browser. Loading the demo dataset is behind a button rather than automatic,
+because spending that before anyone has asked for anything reads as a broken page.
+
+After the first load the database is kept in IndexedDB, so a second visit
+restores it instead of rebuilding — and the rules are declared rather than
+recomputed, which is the difference between about 25 seconds and about 19.