VAIF Verament

VAIF Verament is the AI builder in VAIF Studio. You describe what you want in plain words, Verament plans the work, and nothing is built until you confirm the plan.

What Verament builds

A request names what to generate, or Verament picks it from your prompt:

• Schemas: tables, columns, relationships and indexes.
• Storage: buckets and their access rules.
• Functions: functions for your business logic.
• Backends: a server-side project built on your VAIF backend.
• Full stack: server code and a frontend together.

Verament reads your project’s existing schema and settings, so what it writes fits what you have. See Generation types for each one, and Tiers and effort for the engines it runs on.

Build something

1. Open Verament in your project’s navigation.
2. Describe what you want to build. Writing prompts has examples.
3. Review the plan card: the files Verament will write, what planning cost, the most the build can cost (planning included), and your balance.
4. Choose Confirm and build, or Cancel to drop the plan.
5. Review the files as they arrive, then apply them to your project.

How a build runs

1. Planning, shown on the plan card

Verament first plans the build: every file it will write and what each depends on. Planning is charged, and the plan card shows that charge up front, together with the most the whole build can cost and your balance. If Verament can’t tell how much you want built, it asks first, and the question is free.

The card also has a Docs row. Docs: README only is the default: the README is written from your code, at no charge. Add docs… adds an API reference, a user guide, architecture notes, or something else you describe in a short note. Each is one more file, written after the code and included in the maximum the card shows.

2. Confirm

Nothing is built, and the build isn’t charged, until you confirm the plan. Cancel drops it, and nothing more is charged. A plan can be confirmed once, before it expires; after that you plan again. If your balance is below the build’s maximum, the card offers Smaller run or Run until zero instead of starting a build it can’t finish. A request your plan doesn’t include is refused before any AI work, with the part your plan does build, and a refusal is never charged.

3. The build

Files are generated in batches, in dependency order: database schemas first, then server code, then frontend code, so every import points at a file that exists. The build is charged for the batches that run, and never more than the maximum the card showed.

4. Checks and checkpoints

Each file is checked against the plan. Progress is saved as the build runs, so a build that stops can resume where it left off.

From the API and the SDK

A build request through the API answers with the same plan card (preflightRequired), and nothing is built until you confirm it:

• Send the same message to POST /ai/copilot/chat with the plan’s sessionId and preflight: { confirmPlanId }. The answer carries the build’s files.
• POST /ai/copilot/job with the same body builds it in the background.
• In @vaifstudio/client the calls are copilot.confirmPlan(), copilot.cancelPlan() and copilot.queueConfirmPlan().
• GET /ai/copilot/session/{sessionId} returns the card a session is waiting on (pendingPlan).

To add docs, confirm with preflight: { confirmPlanId, docs: { kinds: ["api"] } }, naming kinds the card’s docs row offers (api, guide, architecture, or custom with a note). Without docs, the build writes the README only. A kind the card didn’t offer is refused with 400 PLAN_DOCS_UNKNOWN before anything runs.

For automation, send autoConfirm: { maxCredits } with the request. The build runs in the same call when its maximum is at most that many credits; otherwise the plan card comes back marked refused, and nothing is built. Generation types has an example.

Using the result

Review and edit the files in the Verament editor. To work on a backend or full-stack result on your own machine, download it with the CLI:

vaif workspace pull --session <session-id> --output ./my-app

Every request spends Verament credits. Verament answers questions about your project from the console; these docs have no AI assistant of their own.