What data structure would be best for a non-tree (in the graph theory sense), path-saved, troubleshooting flow for a web troubleshooting site?
In plainer words, if I'm wanting to model a troubleshooting flow, such that it's not strictly in a "downward" direction towards a resolution or contact point, is there a more specific structure than just a graph? I'm not worried about efficiency, instead I'm worried about easy of description; the goal is for this to be defined in YAML or some other markup that non-programmers can implement and maintain.