recipe-audit-reportlisted

# Recipe: Audit Report (AI-Assisted Research) Make AI-assisted patent research verifiable: every finding traceable to a command, every command re-runnable. ## Step 1: Record the Environment ```bash flowleap --version flowleap --json doctor # backend, auth mode, provider-key status ``` Record: CLI version, backend base URL, date/time of the session, and the auth *mode* (OAuth session vs. API token) — **never token values or key material**. ## Step 2: Provenance Discipline During Research For every substantive finding, log the exact command and keep the `--json` output. The tools facade makes provenance explicit: ```bash flowleap --json tools list # capabilities available that day flowleap --json tools run server_info # backend identity/version ``` Note per result: the source system (EPO OPS, USPTO ODP, OpenAlex, Semantic Scholar, legal RAG), the query string, limits and date filters, and the `cached` flag from the response envelope (cached data may lag live records). ## Step 3: Verify Asset Status Claims Any statement like "patent X is in force" must be backed by a dated check: ```bash flowleap --json summary <patent-number> # legal status + family + term flowleap --json timeline <patent-number> # event history behind the status ``` ## Step 4: Reproducibility Pass Re-run the load-bearing commands at report time and diff against the original outputs. Patent registers move — note any finding that changed between research an