The landing page for Selvage (the project) and the Selvage Session Protocol (the protocol it
publishes), served at https://selvage.dontblameme.dev. It is one Next.js App Router project: the
route / carries the page, and app/not-found.tsx is the route beside it. The canonical material
lives in the other repositories:
selvage-protocol/specification for the
protocol, prose and vectors, selvage-protocol/reference_server
for the server and client library, and selvage-protocol/vscode_client,
selvage-protocol/nvim_client and
selvage-protocol/jetbrains_client for the
three editor clients, selvage-protocol/web_client
for the browser page, and selvage-protocol/mcp for an
agent's way into a room, over the Model Context Protocol.
$ npm ci --no-audit --no-fund
$ npm run dev
# then open http://localhost:3000/Production, the way the deployment builds it:
$ npm run build && npm start
# then open http://localhost:3000/npm run dev is the framework's development server, and a dev server restarted underneath a reader
can look like a page that keeps refreshing itself; the next build output carries no way to reload
a page, and the deployed policy refuses every origin but its own.
Node comes from .nvmrc (nvm use, or any manager that reads it). package.json engines carries
a floor (>=24), not a pin: Vercel deploys only the Node majors its build image offers today
(24.x default, 22.x), and a version it does not offer — whether pinned by major (26.x) or exactly
(26.11.1) — fails the deployment before anything builds. A floor still admits the newer runtime
developers and CI use.
The page's copy, the wordings it must not carry, the facts it is held to and the figures' rules are
docs/. Those wordings are enforced rather than remembered: scripts/ci-local.sh runs the same
checks as .github/workflows/ci.yml.
- The page, and its copy: the parts of the page, and the wording behind each.
- What the page must never say: the forbidden wordings, with reasons.
- The claim filter: what the check enforces, and the limits of a phrase list.
- The product figures: the window, the four drawings, and their rules.
- Deploying it: Vercel, the response headers, and why it is not a release.
MIT OR Apache-2.0, the pair the clients carry; see LICENSE-MIT and LICENSE-APACHE.
The workflow sentence is adapted from the Neovim client's public README, under the same license.
The copy contract and its public evidence are documented in docs/; maintaining the page needs
no separate planning repository.