NIMOS / ENGINES / EDGESTACK
← THE BUILD SYSTEMEDGESTACK
THE EDGE LAYER
Edge Compute, Security & Infrastructure
The boring layer in front of the site: auth, headers, edge routes, data and schema.
DRAWN BY THE HOUSE
One mark per engine, on one grid, in one hand.
10
TOOLS
PROJECT
WIRE
USED
THIS BUILD
Security headers in next.config.ts; sitemap and robots routes.
THE PROOF LEDGER →WHAT
What it is
Ten tools: Vercel Edge, KV, Postgres, Clerk, jose, next-auth, superjson, GraphQL, Apollo and Prisma.
WHY
Why it exists
Products live at the edge with auth and persistent data. This is the layer that must not break, kept separate from the build tools.
HOW
How it runs
npm into projects; legacy KV/Postgres entries noted as migration lanes toward Neon/Upstash; Prisma pinned to stable rather than an RC series.
WHEN
When it runs
Auth flows, edge routes, serverless data, GraphQL layers and schema work.
WHO
Who owns it
CEO owns production plumbing; Research watches deprecations; Build wires auth/data; Data keeps schema and migration ledgers; Ops gates every migration with a backup.
TOOLS
The registry
The engine manifest is the source of truth. These are its entries, including the ones that are not used on this build — the proof ledger says which is which.
@vercel/edge
npmNative configuration structures optimized for global edge routing.
@vercel/kv
npmLow-latency Redis structures for edge data transactions.
@vercel/postgres
npmServerless data storage matching live server setups.
@clerk/nextjs
npmFast user-access validation layers built for server components.
jose
npmLightweight cryptography signing for edge execution contexts.
next-auth
npmHighly adaptive security framework for distributed setups.
superjson
npmComplete object transformation across framework network boundaries.
graphql
npmSchema structures for data coordination layers.
@apollo/client
npmState-driven cache networks for custom query structures.
prisma
npmType-safe, code-first data access.
10 registry entries. The proof ledger on the Gantry page says which of them this build actually used.
RUN
Run it
ENGCTL / THE ENGINE FLOOR
$ engctl show edgestack$ engctl awaken edgestack$ engctl install edgestack --dir ./site`engctl` is the registry control surface. `awaken` checks wiring before it activates a cell; `install` writes the parts into a project.
PROOF
On this build
Security headers in next.config.ts; sitemap and robots routes.
N/A and PARTIAL are stated, not hidden. The ledger is generated from this project, not from a template.
LIMITS
What this does not claim
USED here for security headers and the sitemap/robots routes, not for auth or a database layer.
The engine is the how. The brief is the start.