RAGE, Three Years On: The Engine Was the Right Word
RAGE said generation should stand on retrieved evidence. Three years on, I run that way, with pgvector and DiskANN, and two of its promises are still open.
197 chunks, zero reconnects: what happened when I actually ran the ingest
RAGE ingest results: 41 documents, 197 chunks, zero reconnects — and the two tunnel failures that taught more than the success did.
What it costs to remember: the RAGE ingestion path, and a map of the whole project
How RAGE ingests a corpus into pgvectorscale: 515s down to 0.49s on re-ingest, DiskANN over 48,800 bge-m3 chunks, and a map of the whole RAGE project.