flowleap-patstatlisted

# FlowLeap Patstat (Portfolio Analytics) Auth and global flags: see `flowleap-shared`. ## Which engine? — the three-way routing rule FlowLeap runs three analytics engines, split by *criteria shape*, not by metric: - **Topic Analytics** (`flowleap analytics`, the Google-Patents corpus engine) — the question's essential criterion is **free-text keywords** over title/abstract ("quantum computing filings over time"). Publication-level counts, substring name matching, per-query cost. - **Portfolio Analytics** (`flowleap patstat`, this skill, the PATSTAT engine) — the question is expressible in **structured criteria**: named applicant (entity-resolved, harmonized names), CPC/IPC class, office, year, family, grant status. Family-level counting, zero marginal cost. - **Graph Analytics** (`flowleap patstat graph …` → `flowleap-patstat-graph`) — the question is about **a named node and the relationships around it**: who cites EP3477840, the citation/family path between two patents, where a family has coverage, an applicant's co-applicant network. Typed nodes and edges, each with a confidence tag and row-level provenance. Routing rule: free text → `flowleap analytics`; structured criteria, especially a named company → `flowleap patstat`; a *connection* rather than a count → `flowleap-patstat-graph`. If the answer is a table of counts it is here; if it is who-links-to-what, it is traversal — go across. Individual documents (one known publication or application) a