Audit Branching Complexity

Audit complexity and production risk, not artistic ambition.

A large branch can be justified. A small graph can still be fragile if state combinations are poorly controlled.

Inputs

Use any representation available:

• node / edge graph
• flowchart
• quest outline
• Ink, Yarn, JSON, YAML, spreadsheet, or script structure
• variable definitions
• conditional dialogue
• design document

If code or structured data is supplied, preserve identifiers so findings can be traced back.