Hardening the Foundry Story / Sales Pitch

I am struggling because people think the idea is confusing. The sales pitch feels very sharp to me but it is clearly just not. People are telling me it is confusing and asking questions that make it clear the scope / purpose is not particularly intelligible. I take full responsibility for this - certainly extracting a pattern I call "the foundry pattern" from a particular application that I used to call "The Foundry" and now call the "The Workflow Foundry" is confusing - that is natural evolution to some degree but is is tragically confusing. Introducing new language such Foundry, Cast, Mold, "casted skill", and relying on language that is non-specific and evolving like Knowledge Base and Skill are not a firm grounding to build on.

@dannon brought up the very good point that without a variant of this pattern - skills just aren't very amenable to composition. Of course skills should be compiled down from something because different actions need to reuse resources. That is a good point that needs documentation on this site.

No file, test, or entry point is named. Begin by reviewing the site's current explanation of the Foundry pattern and its terminology; done means the scope, purpose, and relationship between skills, composition, resources, and the pattern are documented clearly enough to resolve the reported questions.

Written by the indexing model from the issue text.