citizen404

Start with one bounded use case matching the product's core job: Interactive AI mystery game built around finding an autonomous digital character. Define the expected result and the information or permissions required.

Run a normal example and at least one difficult case. Inspect outputs, actions, logs, citations, or previews where available. Check for unsupported assumptions, missing context, latency, and recovery behavior.

Grant only the permissions needed for the test. Keep human approval for production code, security changes, customer communication, financial actions, or other consequential operations.

Once the workflow is reliable, save reusable instructions or integrations and expand usage gradually. Re-test important workflows after major model or product updates.