Principlev1

Define workflow inputs and outputs with operational

Define workflow inputs and outputs with operational precision before attempting to chain or automate workflows, specifying not just what enters and exits but the format, source, and acceptance criteria for each.

Why This Is a Principle

This is a derived principle for workflow design. It follows from Working Memory Capacity Limit (working memory limits make vague inputs costly), Exponential Information Decay (unrehearsed information decays, requiring explicit capture), Meaning as Receiver Construction (meaning is constructed by receivers from their models, not transmitted intact - so specification must be explicit), and Abstraction Necessarily Discards Information (abstraction discards information, so you must be explicit about what to retain). The principle prescribes how to design workflow interfaces to enable composability and reduce cognitive load.

Source Lessons

L-0811

Workflow inputs and outputs

Define clearly what goes into each workflow and what comes out. Without precise input-output specification, you cannot chain workflows, automate steps, or diagnose failures.

Connections

Derived From (4)

AxiomWorking Memory Capacity Limit AxiomExponential Information Decay AxiomMeaning as Receiver Construction AxiomAbstraction Necessarily Discards Information

Back to Concepts