tlamatini-flw-doctor

To validate a .flw workflow file, run a doctor audit that checks JSON parsing, required keys, node types, connection integrity, and parametrizer queue constraints, producing an ok, problems, and summary report.

Workflow topology validation checks connection integrity by ensuring every connection references existing node IDs and that terminal nodes do not misuse target_agents, verifying inputs, outputs, and access controls.

To enforce single-lane queue constraints for parametrizer nodes, apply static analysis to verify proper inbound and outbound edge configuration during workflow validation, catching structural issues before execution.

A .flw workflow fails at runtime due to invalid agent types when node types do not match known agents, requiring structural validation to catch these semantic issues before execution.

Yes, you can use static analysis to check access controls, inputs, and outputs in FLW workflows by enforcing in-process validation that reports structural and semantic issues in a .flw file.

The best way to perform pre-flight checks on complex FLW workflows is to audit .flw files for correctness, generating deterministic reports on topology, valid agent types, and connection integrity to reduce runtime failures.