display.archi · 9 accessions

Display
Archive

Every website I have built, with its condition recorded. Seven are deployed and two run but are not public yet.

The unfinished ones are listed on purpose. A register that showed only the successes would be a portfolio; this is meant to be a record.

Start a conversation The standard every entry meets

Shipped: 7
Built: 2

The register

DA-001Shipped2026

Orbis

A voice-first assistant with hands: it runs one Windows machine, its files, Chrome and repositories. Olympa is the public product built on it.

Deployed and reachable.

Next.js 16
React 19
Tailwind v4
TypeScript
Postgres 18
Vercel

Full entry Website

DA-002Shipped2026

Display Archive

This register. Every site in one place, authored against Postgres and published as a static snapshot, plus a service to keep a register of your own.

Deployed and reachable.

Next.js 16
React 19
Tailwind v4
TypeScript
Neon Postgres
Vercel

Full entry Website

DA-003Shipped2026

Agriadvisor

Point a phone at a plant and get its name, its health and a care plan. Fourteen grow-at-home guides, member profiles and a feedback board.

Deployed and reachable.

Next.js 15
React 19
Tailwind v4
TypeScript
Supabase
Vercel

Full entry Website

DA-004Shipped2026

Cozzette

A made-to-order clothing label by an eleven-year-old designer. A dress sews itself as you scroll. The shop is built; payments open later.

Deployed and reachable.

Next.js 16
React 19
Tailwind v4
TypeScript
Three.js
Drizzle
Neon Postgres
Vercel

Full entry Website

DA-005Shipped2026

Aste

A training tracker built on measurable gates. The server decides whether a rung passed from the numbers you logged, then reads it against your recovery.

Deployed and reachable.

Next.js 15
React 19
TypeScript
Prisma
Postgres
Better Auth
Capacitor
Vercel

Full entry Website

DA-007Shipped2026

Vibe Builders

Answer nine questions and get every third-party account a build needs, with the exact scope to grant and what it costs. Nothing leaves the browser.

Deployed and reachable.

Next.js 16
React 19
Tailwind v4
TypeScript
Vercel

Full entry Website

DA-009Shipped2026

Voidsmith

Describe a site in plain language and it forges the real files. Your own key, your browser, your project, with nothing stored on a server.

Deployed and reachable.

Next.js 16
React 19
Tailwind v4
TypeScript
Vercel

Full entry Website

DA-006Built2026

Novox

A free, all-ages platform for building 3D multiplayer games: its own engine, netcode, scripting and a signed-in website. Not deployed yet.

Real code that runs. Not publicly deployed.

Next.js 16
React 19
TypeScript
Babylon.js 8
Rapier
QuickJS
Neon Postgres

Full entryNot deployed

DA-008Built2026

Clavessa

Learn piano on the instrument you already own. A phone app that listens, watches, and shows the notes you actually played. No web build is up yet.

Real code that runs. Not publicly deployed.

Expo
React Native
React 19
TypeScript
Next.js 16
MediaPipe

Full entryNot deployed

Decisions behind the work

Four arguments from building these projects, each with a number you can check against the repository it came from.

Architectureorbis01 / 04

The website cannot hold the brain

copies of the model key in any cloud

The problem: The original plan put the conversation loop in serverless functions. Two facts killed it: a serverless function cannot hold a WebSocket open for the length of a voice turn, and the database was required to stay on a personal machine.
The result: Two requirements that looked opposed — host it on Vercel, and keep the database on my own machine — both hold, and the model API key never enters a cloud environment at all.

Designdisplay-archive02 / 04

An archive that reports condition

8 of 8

projects listed, four of them not deployed

The problem: When this register was first drawn up, one of its eight repositories held a single line of README and one commit, and three more had never been deployed. A portfolio showing only the four live projects would have been honest but thin; one implying the rest were finished would have been a fabrication.
The result: The sparse inventory became the subject instead of the problem. The register shows the real shape of a body of work, which includes the parts that stalled, and nothing on the page needs a disclaimer.

Securitydisplay-archive03 / 04

Enabled is not enforced

tables verified FORCE, not merely enabled

The problem: Row-level security was switched on for every table, and it did nothing. Postgres exempts a table's owner from its own policies by default, and the application connects as the owner — so every policy reported as enabled while permitting everything.
The result: The policies bind to the role that actually connects. The failure mode that mattered here was silent — a security control that reports success while doing nothing — so the check for it is now part of provisioning rather than a thing to remember.

Securitydisplay-archive04 / 04

The rate limiter that forgot

15 to 30 min

ladder that now outlives a restart

The problem: The login lockout ladder was ported from a working implementation that kept its state in a module-level map. Its own comment admitted the flaw: on serverless that state is per-instance and resets on every cold start, so an attacker who can force new instances gets far more attempts than the ladder implies.
The result: The escalating lockout survives a restart, which is the one thing the in-memory version could not do. The addresses themselves are encrypted at rest, because an IP address is personal data and a lockout table is not a reason to keep a plaintext log of who tried.

All four in full

For your own work

You can run one of these

Same numbering, same condition field, same standard every page here has to pass before it is allowed to go live. Your entries, your address, and the unfinished ones listed without apology.

Free to build and to publish a few. One payment — never a subscription — for the rest and for a domain you already own.

Make your own register

Further in

Decisions worth writing downThe arguments behind these projects, each with a number you can check against the repository.Questions, answered plainlyWhere the data lives, why the unfinished entries are here, and how a new one gets added.