Decision Checklist — Backend Fundamentals
Use this checklist before code generation or preview.
| Question | Avora action | More detail |
|---|---|---|
| What data does the product store? | Create entities and enums | Entities and Fields |
| Which fields identify or protect records? | Configure keys, uniqueness, indexes, and validation | Keys and Validation |
| Can the related record live alone? | Use association or aggregation | Relationships |
| Is the child created with the parent? | Use composition | Relationships |
| What does the frontend need to call? | Create a request with method, path, inputs, and outputs | Requests and Responses |
| Should the caller be signed in? | Enable request auth | Auth and Roles |
| Should only some roles call it? | Select a role enum and allowed values | Auth and Roles |
| What must happen inside the route? | Build the request logic flow | Logic Flows |
| Does every path return a clear status? | Connect success and error outputs | Logic Flows |
| Does the generated API match the workspace? | Test it in Swagger preview | Preview and Swagger |
If the answer is unclear, start from Avora Overview or return to the relevant builder page linked above.