Master says "this material needs ten extra minutes drying"—dev writes a branch. Next year material changes—nobody dares touch that line. Industry experience enters systems correctly as configuration: temperature, time, tolerance, exclusion rules in process tables and rule engines—not hidden in code. Configuration lets the floor change; versions stay auditable. Hard-coded experience leaves with the programmer.
What lasts isn't the if-statement. It's that the floor can still change it—and audit sees what changed.
Tricks Become Config Items
Process parameters have owners and effective versions. Exceptions use controlled deviations with expiry. Engineering provides capability—conditions, actions, validation—not another "for now" patch branch.
- Ban patching verbal experience directly into production branches.
- Config changes log and pair with work-order versions.
- Second site copies the same config—not a code snippet.
Configuration Is the Container for Experience
The XYN digital intelligence system puts process and business rules in a configurable layer—industry know-how lives with the line. Code solves capability boundaries; configuration solves how this line runs today. Boundaries can be stable; practice must change.
Find three rules existing only in code comments or veteran heads. Migrate to config tables before the next custom dev round.
