Next.js

Next.js serves its own API, so naming it answers the "do we need a separate backend?" question — and it gets the full verification treatment, up to and including being started.

One service, not two#

Next.js is treated as full-stack. Naming it tells the planner the product does not need a separate backend service unless you ask for one, which keeps a small product from being scaffolded as a distributed one.

What has to pass before it ships#

  1. Install and buildDependencies resolve and the production build succeeds. A tree that does not compile fails before anything else is considered.
  2. Tests and new diagnosticsThe repository’s own suite runs, and only newly introduced type or lint diagnostics count against the change.
  3. Start and probeThe application is actually started on a loopback port and its declared routes are requested. It answers, or it does not ship.

It never takes your dashboard port

The port your local Tharas dashboard runs on is reserved and the allocator re-rolls. Probes bind loopback only, never every interface.

StacksReactA React front end scaffolds as a web service in its own directory, so it can sit alongside a separate backend without either plan touching the other’s files.StacksNode.jsNode fills the backend role. It gets the full verification path, including being started and asked whether it is alive.FeaturesVerificationEvery gate used to reason about the tree without ever starting it. Now the tree has to compile, the suite has to run, and the application has to boot and answer before anything is called finished.