Vercel creates
The public Explorer
- Protocol, architecture, research, and documentation
- Public knowledge maps, Cosmos, and Memory Palace
- Read-only public vault index and API routes
- Git-connected preview and production deployments
Public interface · sovereign boundary
Vercel creates your hosted Starlight Explorer. Your private memory, agent runtime, credentials, and orchestration stay in the environment you control.
Zero required environment variables. Vercel shows every setting before creation.
Deployment trace
One source. Explicit boundary.
Source
frankxai/Starlight-Intelligence-System
Build root
site/
Runtime
Next.js on Vercel
01 / The boundary
The public Explorer communicates the protocol and exposes public artifacts. The sovereign runtime keeps the parts that carry identity, authority, and private context close to the operator.
Vercel creates
Your environment retains
02 / What happens
Vercel copies the public repository into your selected Git provider as “starlight-explorer”.
The project name is prefilled as “starlight-explorer” and the build root is fixed to site/.
Next.js compiles the public experience from inspectable source. No database, integration, or secret is requested.
Your Git repository becomes the source of future previews and production releases.
03 / Create your copy
Start with the working public system, inspect every line, then shape the routes, identity, and research surface around the intelligence you want to share.