MethodEntity relationships, dependency paths, product profiles and bottleneck analysis are separated so that architecture does not collapse into a vendor catalogue.
What this map can answer- Where does a workload bottleneck move when compute scales?
- Which standards connect memory, chiplets and hosts?
- How do power, packaging and networking constrain model scale?
BoundaryVendor documentation is useful for architecture details but is not neutral evidence of performance. Benchmark claims should be checked against reproducible results and workload constraints.