Before you start
A signed-in NodeFox workspace. Use synthetic data and prepare outputs before enabling external writes.
01Name by responsibility
Use labels that describe the operation: read contract, validate notice period, request revision. Separate the configured node type from its business purpose so both technical and operational reviewers can follow it.
02Keep contracts small
Define inputs and outputs before adding prompts or code. Validate at system boundaries and preserve provenance. Reuse stable logic through Network nodes rather than duplicating subtly different checks.
03Make exceptions visible
Draw the hold and failure paths with the same care as the normal path. Put consequential actions after explicit checks and decisions. Keep review packets concise enough for a person to use.
04Retest changes
Maintain synthetic fixtures for normal, exceptional and missing-data cases. Review callers when changing a reusable network’s variables. Preserve prior outputs so a change can be explained.
If the result is wrong
If only the original author understands the graph, simplify responsibilities and document the slot contracts.