Interpret. Structure. Produce. Deliver.
The four moves behind each Foundry engagement. This is the argument for why they are sequenced this way, and why collapsing any two of them into one produces the failures the industry has learned to normalize.
Most training programs, whether authored by humans or assisted by an LLM, execute a single undifferentiated move. A subject matter expert or an author reads some source material, decides in the same breath what the program should teach, and writes the content that teaches it. Interpretation, structure, production, and delivery all happen inside the head of one person, in one working session, undocumented.
The result is a program in which no phase has an artifact of its own. There is only content, and the content is the only object the organization owns. Each downstream question (coverage, verification, audit, drift) is asked of the content, and each answer is a rereading of the content.
One move, undifferentiated
The single move default is not stupid. It is efficient in the short run and legible to stakeholders who buy content. It fails on a longer horizon, when the organization is asked to defend a claim it made two years ago, in a language it no longer speaks, about a source that has since been amended.
“Each move is a discipline. Each move produces an artifact the organization can defend. The sequencing is not aesthetic. It is the argument.”
Four moves, four artifacts
Structure governs the sequence. Each move takes the previous move's artifact as its input and produces its own artifact as output. Human sign off gates the transitions.
- Interpret. Extract, from policies, standards, and subject matter, the requirements the program must satisfy. Sentence by sentence, with provenance preserved. Generation before interpretation is guesswork wearing a uniform.
- Structure. Propose a framework (concept nodes, typed relationships, prerequisite chains, assessment definitions) grounded in what interpretation produced. The framework is the object of record from this point on.
- Produce. Generate instruction, activities, and verification against the approved framework. Each produced element carries a link to the node it satisfies and, through the node, to the source clause.
- Deliver. Package and release under governance. Versioning, sign off, and deprecation are first class operations. Delivery opens the next iteration, not the end of the loop.
What collapses when the moves merge
Skip Interpret and each downstream artifact inherits a guess about what the source requires. When the guess is wrong (discoverable only by rereading the source, which is the work you skipped) the program cannot be corrected in one place. It must be corrected everywhere the guess propagated.
Skip Structure and you are back in the default failure mode. Authoring that begins with content, with structural decisions smuggled into paragraphs. Coverage becomes unmeasurable. Revision becomes catastrophic. Verification instruments are chosen after the fact rather than defined at the level of the concept.
Invert Structure and Produce (write the content first, then reverse engineer a framework from it) and you get a framework that mirrors the content instead of judging it. The framework becomes a documentation exercise, not a design instrument. Auditors spot the inversion quickly.
A sequencing discipline, not a marketing frame
Each move is the input to the next. Each move produces an artifact the organization can defend. Each artifact is traceable to the one upstream of it and testable against the one downstream. That is what the four move methodology is for. Not a naming convention, but a sequence that keeps the phases separate long enough to hold each of them to its own standard.
Bring a subject to the Foundry. We build the framework in 45 minutes and you keep it.