When Levi needs a platform build

Levi, your AI teammate · nineloops support

Some asks need real backend. Those become a request that is checked automatically and waits for a person, and AI written SQL is never executed.

Most of what people ask for is records with fields, and that is a tab Levi can build for you. Some things are not: a dedicated table for very large volumes, a connection to another company's system, or logic that has to run on our servers. Levi cannot conjure those, and it is told never to pretend it has.

It becomes a request

Levi files a build request. It carries your own words kept verbatim, what it thinks should be built, and why an ordinary tab is not enough. That last part is required, because it is what the reviewer judges.

The automated checks

Every request is checked by the database before a person sees it. The checks are deterministic, they run against the request itself, and each one records what it found:

The blueprint it wants to use exists, is switched on, and is one a person wrote.
The request is complete: everything that blueprint needs is present.
The name is valid and does not collide with anything the workspace already has.
Nothing in it reaches into a protected part of the system.
Every link it wants to make points at something the workspace can already see.
The number and shape of the fields are buildable, and fields that look like personal or financial data are flagged for the reviewer.
Whether an ordinary tab would in fact have done the job, so a physical table has to justify itself.
Whether the build can be undone afterwards, and what undoing it would mean.

A check that fails at blocking severity stops approval outright. Nobody can click past it, including the owner.

Then a person approves it

A request that would only create metadata a workspace admin could have built by hand can be approved by a workspace admin. A request that changes the product itself has to be approved by the product owner, and being an admin of your own workspace is not enough for that.

Why AI written SQL is never executed

An approved request can only instantiate a blueprint, and every blueprint was written by a person and shipped in a migration. Free form SQL cannot be expressed in a request at all, so there is no path from the AI writing SQL to the database running it. Where no safe template exists, the honest outcome is a written specification for a human to build, and that is what the request produces.

A build request is a request. Until someone approves it, nothing has been built, and Levi is instructed to say exactly that. If your request matters to you, raise a ticket as well and tell us why: we would rather hear it from you than read it second hand.

Still stuck?

Raise a ticket and a person who works on nineloops will pick it up.

<a href="/support">All support articles</a>