AI Self-Iteration

The useful loop is observe, patch, verify, then shrink.

1. AI calls AndroidUse MCP tools to inspect current state.
2. AI generates a narrow AUZM probe or payload change.
3. The payload is built and installed into the AUZM registry.
4. The target app is restarted.
5. AI calls the generated tool and inspects structured evidence.
6. The probe is collapsed into one stable MCP tool.

Why Screenshot URLs Matter

AndroidUse screenshots return protected HTTP URLs directly. This lets an AI agent inspect visual state without asking for a second tool call to copy a file out of the device.

Preferred flow:

screenshot
  -> returns url=http://127.0.0.1:8765/screenshots/shot-...png
  -> agent fetches URL with MCP secret
  -> no adb pull / file station copy required

This keeps iterations shorter and avoids leaking local device paths into tool prompts.

Evidence Rules

For app-side behavior, require one of:

• target-specific app callback
• response object from the app's internal API
• server or network receipt belonging to the target operation
• user-visible confirmation
• structured payload response with target package, process, route, and action proof

Queued request completion is transport evidence only.