Hypercrux on HyperCrux.com

How Long a New HyperCrux Engine in C Would Take: Four to Six Weeks, Phase by Phase

Wed, 07 Oct 2026 00:00:00 +0000

The Beta plan describes a new database engine for HyperCrux, written in C, with all four handles built in. A plan like that needs a time estimate before anyone decides whether to start it. Here it is: about 19 to 30 working days of development to reach the Beta gate, which comes to roughly four to six weeks of calendar time with a working session most days. A first working version with all four handles would come in about a week.

How HyperCrux Got Its Name: Hyperlinks, Hyperspace and the Crux

Tue, 06 Oct 2026 00:00:00 +0000

HyperCrux is a database where every record has four handles. You can reach it by its key, by SQL, by following its links or by how close its vector is to a question. The name describes the spot where those four meet, and it borrows from two old words to do it.

Crux

Crux is Latin for a cross. The constellation of the Southern Cross is officially named Crux, and sailors used it to find south. English borrowed the word for the hardest part of a problem, the point everything turns on: the crux of the matter.

How HyperCrux Was Tested: 200 Killed Writers and Not One Mismatched Record

Tue, 06 Oct 2026 00:00:00 +0000

HyperCrux makes one promise above the others. A record can be reached four ways, by key, by SQL, by its links and by its vector, and the four never disagree. A deleted record doesn’t linger in search results. A link never points at a record that isn’t there. A vector never belongs to a row that was only half written.

Promises like that are easy to make when nothing goes wrong. So the tests go looking for things going wrong, and the results are published with the code, in test/results on GitHub.