afdEP-comm is a general EP communication library for AFD: N Attention token sources communicate with M expert workers. Keep model/GEMM, routing, quantization policy, and serving scheduling 3B0F outside the core. Vendor DeepEP V2 kernels; no external deep_ep or vLLM runtime dependency.
README support owns architecture/topology support and tested hardware. Group the support matrix by architecture, not GPU model. Implementation limits belong to backends, not the library's identity. Do not claim unvalidated hardware or general N/M layouts are implemented. Do not treat unvalidated hardware as rejected unless the code actually rejects it.
docs/api.md owns tensor, weighting, stream, graph, and lifecycle contracts. Preserve DeepEP transport credits, PDL dependencies, stream events and every reader lifetime. New topologies require explicit validation. Validate index bounds and alignment.
Use named constants, explicit state owners, and module-scope imports except intentional lazy runtime loading. Avoid mutable globals and unrelated changes. Python/build changes: run unit tests and Ruff. Native behavior/build changes: run affected backend's GPU suite, including empty/skewed routes, changing graph inputs, delayed peers, and buffer reuse. CPU tests do not validate transport. Check installed distributions include runtime sources, licenses, and provenance.
Retain Apache/MIT notices and frozen origin hashes; document upstream-derived changes. Keep validation records tied to the exact source digest. Keep profiled/unprofiled runs separate, report memory metrics accurately, and do not attribute polling time solely to network or bookkeeping. No serving claims from communication-only evidence. Exclude credentials and private cluster data.