Architecture first, code second.

Nodes and edges are the project, not a picture of it. The agent proposes changes to that graph, you accept them, and every accepted change becomes a version you can diff against the one before.

Crited reads Notion, Slack and GitHub, pulls candidate tasks out of the discussion, and flags which part of the architecture each one touches. Every suggestion waits for a person to accept or reject it — nothing is applied on its own.

Point Crited at a repo and it reads the code into a first-cut architecture: modules, services, tables and how they connect. A draft to correct, not a verdict.

Pick a theme and see it rendered by the compiler's own stylesheet, over your own screens — not a mock-up drawn alongside the build and free to drift from it. What you approve and what gets compiled are the same tokens.

Connect your editor over MCP and it reads the specification, proposes changes to it and previews the compiled migration before anything ships. Changes arrive as ordinary versions with an author, revertible like any other.

Every build is pushed to your GitHub as a single commit. Everything under src/custom/ stays yours: the compiler never reads it and never overwrites it, so hand-written code survives each rebuild.

The data map, access matrix, retention rules and subprocessor list are derived from the same specification the app is built from, so they describe what is actually deployed and go visibly stale the moment it changes.

Add a chat box grounded in your own records, with optional semantic search over them. It runs on your API key in your deployment and reads through the signed-in user's session, so it can never see more than that person could. Install the key through Crited, or add it in Vercel yourself and we never hold it.

Run more than one agent in parallel, each in its own tab with its own context, so a long thread about one part of the system doesn't drag the rest of the project through it.

Each kind of task is routed to a model picked for it — the strongest for architecture and code, the cheapest for bulk classification — and what a run costs is recorded and shown as it accrues.

Install a published project as the starting point for your own, or publish one of yours. A template arrives as an ordinary specification you can edit and diverge from — not a locked scaffold you grow out of.

A signed desktop build for macOS and Windows that updates itself, for when a long agent run should not depend on a browser tab staying open.

Your infrastructure, your data, your keys — nothing runs on hosting we hold, and there is no lock-in to unwind later. Schema changes ship as numbered SQL migrations applied in order, each one reversible; destructive ones ask before they run. A domain can be bought from the deploy screen, on your own Vercel token into your own account, so the registration is yours and not a line on our invoice.