🛡️ Plans and safety

Building with Ada consumes AI credits. The builder should show the plan, usage, and remaining balance before a build starts.

Billing expectations

• Plans determine building capacity and available features.
• Credits can be purchased as add-ons without changing the plan.
• A failed or stopped build should charge only for work that actually ran.
• Temporary provider interruptions should be retried where possible instead of consuming credits for no result.

When testing billing, use the test billing environment and document the plan, interval, checkout result, and webhook result separately.

Data and credentials

Each app has its own data. Secrets should remain encrypted on the server and should not be written into the app bundle. Only values that are safe to ship belong in a client app.

Testers should never paste production credentials into prompts, screenshots, issue reports, or test fixtures.

Approval points

Pause for human review when a request involves:

• Authentication or account access.
• Payments or billing.
• Permissions or private data.
• Destructive actions.
• Database changes that rename, remove, or reshape existing fields.
• Changes affecting many screens or production users.

The expected behavior is explicit communication and an approval step before a risky change is applied.