On Wed, 11 Mar 2026 11:50:47 +0100 Oleksij Rempel wrote:

Looking at the current patch:
- component (MAC, PCS, PHY, MODULE)
- name (subsystem label)
- id (local instance selector)
- direction (near-end / far-end): These terms become highly ambiguous in
  branching topologies (like CPU port on DSA switches).

mixed loopbacks across complex interconnects, userspace will eventually need a
Directed Acyclic Graph (DAG) model.

By adopting a DAG topology now, we can reduce the load on the initial
implementation and bypass much of the ongoing naming discussions, as components
are identified by their topological relations rather than arbitrary string
labels.

Not sure we need parentage chain or just "stage id" within each
component but FWIW if I interpret what you wrote right - I think 
I agree :) What matters is the topology not the naming of things.