The 404 was treated as a proper page rather than a fallback state.

The number is constructed as an architectural drawing. The 4 and the 0 are formed from walls at true thickness, with furniture laid out inside the resulting rooms and dimension strings running along both edges. It sits inside the same drafting system as the rest of the site rather than borrowing a display typeface.

The error message then repeats. Instead of a single dialog, identical windows cascade back across the canvas, each one carrying the same 404 notice. It reads as a system throwing an unresolved warning over and over, which is the exact behaviour Heron is built to prevent inside a model.

Error pages are never in the brief. They're a good measure of whether a team understood the product or just styled it.

Treating a 404 as an actual page instead of a dead end is such a good instinct, where did the architectural drawing idea come from, personal interest bleeding into the work?

Two case studies, two totally opposite registers.

One is carved in stone and says nothing.

One drips off a spoon and won't shut up about which field it came from.

Which one do you want first?

vectis — zero-knowledge privacy, dithered like a forgotten statue

HIVE INDEX — raw honey with a paper trail. No two lots taste the same, and we don't correct for that.

Vectis