Automation architecture

Goal

Turn a customer use case into an exact, minimal Nexor configuration: named primitives with concrete field values, connected end to end. The deliverable is a configuration, not a recommendation.

The three laws of decomposition

Apply these before choosing any primitive. They are not style preferences: each names the only shape the platform can gate, trigger, template, or verify. A design that breaks one is unreliable even when it demos correctly, because the platform cannot see the part that lives in prose.

Law 1 — every piece of information the system needs is a variable

If the build depends on knowing something, it exists as a named workflow field or as lead metadata. Never as prose in a prompt, never as "the agent will remember it from the conversation."