Practical reference library
Practical specifications and release checks for AI-built applications.
Guide 01
Write acceptance criteria as observable outcomes for a named user, record and action. For a client portal, define who can view a project, submit a file, approve work and recover from an error. A generated screen is ready for review when those outcomes work with persistent data and the intended permissions.
Read the guide →Guide 02
Test tenant isolation with two accounts in different organizations and an explicit list of protected actions. Use Account A to create a record, then use Account B to request that record through the application's normal API. The server must apply the intended access policy even when the interface hides the record.
Read the guide →Guide 03
Test a duplicate webhook by delivering the same synthetic event more than once and checking the business outcome. The receiver should authenticate the event, record a stable deduplication key and apply the intended change once. Also test a crash between recording receipt and completing the action.
Read the guide →Guide 04
A restore rehearsal proves that a backup can recreate a usable application in an isolated environment. Restore a known dataset, connect a compatible app version, verify important records and permissions, and measure the time required. Record what data would be lost between the backup and the incident.
Read the guide →Guide 05
Before inviting a paying customer, assemble a small release evidence pack: the customer workflow, test results, permission checks, billing behavior, recovery procedure and named support owner. Record what was actually tested on the release build. Separate demonstrated behavior from features that are still assumptions.
Read the guide →