Engineering case studies from building Jarvis itself — each one checkable against the repository. Not client stories; there are none yet, and that section below is honestly empty.
Architecture0 secrets in the hosting environment
The website cannot hold the brain
Problem
The original plan put the conversation loop in Vercel functions. Two facts killed it: a serverless function cannot hold a WebSocket open for a voice turn, and the database was required to stay on a personal machine.
What changed
The split inverted. Vercel serves the interface; the personal machine runs the brain, the tools and the database, reached over an outbound tunnel that needs no open ports.
Result
Two requirements that looked opposed — “host it on Vercel” and “keep the database on my PC” — both hold, and the model API key never enters a cloud environment at all.
Safety30-day recovery window on every delete
Reversibility instead of confirmation prompts
Problem
Deletes, sends and spending were explicitly left off the confirm-first list, to keep the assistant fast. That leaves an agent with filesystem access one bad inference away from destroying work.
What changed
Rather than reinstating prompts that were not wanted, destructive operations were made recoverable: deletions move to a dated trash kept for thirty days, hard resets stash first, overwrites keep the prior version.
Result
No friction was added and no work can be lost. The confirmation gate stays reserved for the two categories that genuinely warranted it.
Dependencies3 high → 0, before deploy
Three high-severity CVEs, closed before the first commit
Problem
The initial install pulled a framework version carrying four PostCSS advisories and a set of inherited libvips vulnerabilities through its image pipeline.
What changed
Rather than running the automatic fix — which force-upgrades blindly — the framework was moved to its current major deliberately, then re-audited and rebuilt to confirm nothing broke.
Result
A clean audit at the point the project was created, rather than a backlog item that would have shipped to production first.
Interface7 patterns banned, checked automatically
A homepage that boots rather than scrolls
Problem
Every AI product landing page is the same object: centred hero, subheading, two buttons, three feature cards with line icons. It is instantly legible as machine-generated, which undermines the claim being made on it.
What changed
The subject was fixed and the page made to move past it. Scrolling assembles the system layer by layer in its real dependency order — brain, hands, ears, memory, heartbeat, rails.
Result
The page argues its own point structurally. A build standard now hard-bans the seven patterns above, and an auditor fails the build when three or more appear.
Reviews
Nothing here yet. This section stays empty until there is a real person with a real quote — inventing one would break the same standard this site is built to satisfy.