Validate

pawabase validate runs entirely on your machine. It contacts nothing and needs no key.

pawabase validate
pawabase validate --json        # machine-readable, for CI

What is checked

Area	Examples of what it catches
Names	Invalid characters, reserved names (`docs`, `platform`…), duplicates
Fields	Unknown types, an invalid `pattern`, a `Ref` to a schema that doesn’t exist, duplicate field names
Policies	An unknown operator, a malformed condition, a reference to a policy that isn’t defined
Relations	A relation whose resource or field doesn’t exist
Indexes	Unknown columns, too many columns, unsupported methods
Flows	A block that doesn’t exist, a link to a missing block or handle, unreachable blocks, invalid block settings, template syntax errors
References	A route’s handler flow, a subscription’s `run`, a bucket’s policy: each must exist
Secrets	A required `env("NAME")` is named correctly (its value is only needed to deploy)
Conformance	Each definition’s body matches the server’s own request model

Everything is checked together, so a reference between two files is verified too.

Reading errors

Errors name the definition and the place:

✗ flow issue_invoice: block "fees": filters.grade: unknown template path "student.output.grade"
✗ table orders: relation "customer": resource "customers" is not defined
✗ policy staff: unknown operator "and"

Fix the first; later ones often disappear.

Common fixes

Message	Fix
unknown operator	Use `&`, `\|`, `~` and comparison operators, not Python’s `and`/`or`
resource X is not defined	Create it, or fix the name; pass the object instead of a string
template path not found	Name the block (`.named("student")`) and use `ctx.steps.student.output…`
unreachable block	Link it with `>>` from the trigger, or remove it
a Ref needs a schema	Define the `Schema` and pass it

Make it part of every change

Run it in a pre-commit hook and on every pull request (CI/CD). It is fast and offline.

Plan and deploy

Next: compare with the real environment.

Emulate

Rehearse a deploy.

Overview

Infrastructure as code

Define your backend

Logic and events

Files and mail

Ship it

Reference

SDK clients

What is checked

Reading errors

Common fixes

Make it part of every change

Plan and deploy

Emulate

​What is checked

​Reading errors

​Common fixes

​Make it part of every change

Plan and deploy

Emulate

What is checked

Reading errors

Common fixes

Make it part of every change