Nisc · docs

Nisc docs.

Nisc is a full-stack app framework in which the whole application is data: screens, queries, permissions and automations are JSON documents. Each part is a package of its own, with a homepage, guides and a reference.

Start an app

npm create nisc

It makes a working app from a template, with an AGENTS.md that tells your coding agent the rules.

Or start with one package

Draw a screenNova: a screen from a JSON document, drawn by your components.Query PostgresVex: send what you want and its shape, and get rows back.Run a serverMoss: sign-in, permissions and a database behind one app.

The packages

Pick the one you need.

ScreensNovaScreens as JSON: shells, canvases, actions and layouts, drawn by your own components.Guides Reference

DataPrismEvery transform as a JSON config: shaping, formatting, branching.Guides Reference

DataVexYou send an intent and a shape. Postgres answers, and the model is asked once.Guides Reference

DataStrataMigrations for the screens and queries you saved, and for your tables. A release can change a format and what you saved still runs.Guides Reference

ModelsSignalThe call to a model: a schema sent the way each model takes one, and the answer checked against it.Guides Reference

ModelsSolidA JSON streaming library: structured output from a model that streams, as a whole object of your schema at every moment.Guides Reference

ModelsCortexThe loop that runs an agent: the messages it keeps for a model, your tools run for it, and its answer checked against your schema.Guides Reference

ServerMossThe app server. Each person’s app runs on the server, built from what the charter grants them, and the browser draws it.Guides Reference

ServerCharterAccess control by existence: your roles decide which screens and data your app is built from, and the rest was never put in.Guides Reference

ServerTideAutomations, as data: a JSON document names a trigger and the function to run. Schedules, database writes and webhooks, with retries and a record of every run.Guides Reference

How they fit

One app, from the browser to Postgres.

A user’s app runs on the server, in Moss. Charter decides which screens and rows it is built from. Nova runs it and draws it. Vex reads and writes Postgres, and Tide runs automations.

On the serverMoss

In the browserTerminalNova’s adapter, drawing.

OutsideA modelSignal calls it.

At sign-inCharterResolved for the user’s roles.

NovaThe shellOne user’s app, running. Prism shapes what its endpoints send.

Every read and writeVexEach under the user’s policy.

Your server codeFunctionsAn assistant, built with Cortex.

After a writeTideRuns the automations a write triggers.

What lastsPostgresStrata keeps its tables in step.

pressesscreenswhich screenswhich rowsSQLthe sessioneach write

On the serverMoss

In the browserTerminalNova’s adapter, drawing.

At sign-inCharterResolved for the user’s roles.

NovaThe shell

Every read and writeVex

Your server codeFunctions

After a writeTide

OutsideA modelSignal calls it.

What lastsPostgresStrata keeps its tables in step.

pressesscreenswhich screenswhich rowsthe sessioneach writeSQL

Signal, Solid and Cortex are for calling a model. Prism maps data everywhere, and Strata keeps saved documents and tables working across releases.

How these docs are laid out

Every package has three parts.

HomepageWhat the package is and why Nisc has it, shown with the package itself.

GuidesTutorials. Each is one file you can run, explained a step at a time.

ReferenceThe files the package ships, and its API: a page per method, operator or error, with an example.

For your coding agent

The docs, as files.

llms.txtEvery file the packages ship, as Markdown, listed at one address.

AGENTS.mdThe rules a Nisc app is built by ship with the nisc package, in node_modules/@niscorp/nisc/AGENTS.md.