Create the new AAanalysis data-flow infogram (df_seq → df_parts → df_feat → model → explain)

[breimanntools]

Problem

The current data-flow diagram on the Usage Principles page (docs/source/_artwork/diagrams/components.png, shown at usage_principles.rst:49) predates the current API vocabulary and visual style. It is the figure slated for replacement, but no replacement asset exists yet — so the page refresh (#226) is blocked on artwork that has to be designed first.

Goal

Produce one clean, current data-flow infogram asset (the canonical load → parts → feature → model → explain → plot flow) that #226 can drop straight into the Usage Principles page — in a visual style consistent with the new ecosystem map.

Requirements

• Design a single infogram covering the canonical dataflow: df_seq (+ df_scales / df_cat) → df_parts (via SequenceFeature, split_kws) → df_feat (via CPP) → model (TreeModel) → explanation (ShapModel) → plot, with the side branches AAclust (redundancy reduction) and dPULearn (negatives from unlabeled data).
• Use the current vocabulary and class names exactly (df_seq, df_parts, split_kws, df_feat; SequenceFeature / AAclust / CPP / dPULearn / TreeModel / ShapModel) — cross-check against docs/module_map.md.
• Export to docs/source/_artwork/diagrams/ as both a vector (.svg) and a raster (.png) at docs page width.
• Match the look-and-feel of the ecosystem map (_static/aaanalysis_ecosystem.html) — same palette / typography family — so the two read as one design system.
• Keep the source/editable form (or the generating script) discoverable for future edits.

KPIs / Acceptance criteria

• New .svg + .png committed under _artwork/diagrams/, legible at 100% page width (no clipped labels).
• Every stage label matches a real public symbol / data-object name in the current API (no stale names).
• Renders cleanly when referenced by a .. figure:: directive (make html, no warnings).
• Approved as the visual to consume in Refresh Usage Principles landing-page diagrams: swap in the new data-flow infogram + drop the mini-ecosystem figure #226.

Scope / non-goals

• Out of scope: editing usage_principles.rst prose / swapping the figure in — that is Refresh Usage Principles landing-page diagrams: swap in the new data-flow infogram + drop the mini-ecosystem figure #226 (this issue only produces the asset).
• Artwork only; no library code changes.

Dependencies

• blocks Refresh Usage Principles landing-page diagrams: swap in the new data-flow infogram + drop the mini-ecosystem figure #226 (Usage Principles diagram refresh consumes this asset).
• relates epic: ecosystem integration — consume upstream + descriptors, expose downstream (sklearn / XAI / design) #210 (ecosystem-integration epic) and the ecosystem map style it should align with.

Standards checklist

• Artwork only; no CONFIRM-FIRST code surfaces.
• Names verified against docs/module_map.md / current public API.