Odoo-Modules/fusion_so_to_po/graphify-out/GRAPH_REPORT.md

Graph Report - /Users/gurpreet/Github/Odoo-Modules/fusion_so_to_po (2026-04-22)

Corpus Check

• 7 files · ~2,680 words
• Verdict: corpus is large enough that graph structure adds value.

Summary

• 28 nodes · 26 edges · 8 communities detected
• Extraction: 100% EXTRACTED · 0% INFERRED · 0% AMBIGUOUS
• Token cost: 0 input · 0 output

Community Hubs (Navigation)

• _COMMUNITY_Community 0
• _COMMUNITY_Community 1
• _COMMUNITY_Community 2
• _COMMUNITY_Community 3
• _COMMUNITY_Community 4
• _COMMUNITY_Community 5
• _COMMUNITY_Community 6
• _COMMUNITY_Community 7

God Nodes (most connected - your core abstractions)

1. PurchaseOrder - 6 edges
2. SaleOrder - 3 edges
3. FusionPurchaseOrderWiz - 2 edges
4. FusionPurchaseProductWiz - 2 edges
5. FusionMatchSaleOrderWiz - 2 edges
6. ResPartner - 1 edges
7. Match this PO to a Sale Order based on the Marked For field. - 1 edges
8. Batch match multiple POs to Sale Orders based on Marked For field. - 1 edges

Surprising Connections (you probably didn't know these)

• None detected - all connections are within the same source files.

Communities

Community 0 - "Community 0"

Cohesion: 0.29 Nodes (2): FusionPurchaseOrderWiz, FusionPurchaseProductWiz

Community 1 - "Community 1"

Cohesion: 0.29 Nodes (3): PurchaseOrder, Batch match multiple POs to Sale Orders based on Marked For field., Match this PO to a Sale Order based on the Marked For field.

Community 2 - "Community 2"

Cohesion: 0.4 Nodes (2): ResPartner, SaleOrder

Community 3 - "Community 3"

Cohesion: 0.67 Nodes (1): FusionMatchSaleOrderWiz

Community 4 - "Community 4"

Cohesion: 1.0 Nodes (0):

Community 5 - "Community 5"

Cohesion: 1.0 Nodes (0):

Community 6 - "Community 6"

Cohesion: 1.0 Nodes (0):

Community 7 - "Community 7"

Cohesion: 1.0 Nodes (0):

Knowledge Gaps

• 3 isolated node(s): ResPartner, Match this PO to a Sale Order based on the Marked For field., Batch match multiple POs to Sale Orders based on Marked For field. These have ≤1 connection - possible missing edges or undocumented components.
• Thin community Community 4 (1 nodes): __init__.py Too small to be a meaningful cluster - may be noise or needs more connections extracted.
• Thin community Community 5 (1 nodes): __init__.py Too small to be a meaningful cluster - may be noise or needs more connections extracted.
• Thin community Community 6 (1 nodes): __init__.py Too small to be a meaningful cluster - may be noise or needs more connections extracted.
• Thin community Community 7 (1 nodes): __manifest__.py Too small to be a meaningful cluster - may be noise or needs more connections extracted.

Suggested Questions

Questions this graph is uniquely positioned to answer:

• Why does PurchaseOrder connect Community 1 to Community 2? High betweenness centrality (0.148) - this node is a cross-community bridge.
• What connects ResPartner, Match this PO to a Sale Order based on the Marked For field., Batch match multiple POs to Sale Orders based on Marked For field. to the rest of the system? 3 weakly-connected nodes found - possible documentation gaps or missing edges.