The Pattern
The Pattern
The descriptive spec: a knowledge base of Molds, cast into frozen artifacts with provenance — a pattern each domain instantiates and extends. Start with the Story for why a Foundry exists, the Model for how it works, and the Guiding Principles behind it — then Principles in Action for those principles incarnated in the two instances' real decisions, and Anatomy for what every instance shares versus what each domain adds. Setting up a Foundry turns Anatomy into steps. The Glossary is the reference.
Make the knowledge base actionable — and the most obvious thing you cast from it is a skill that doesn't rot. Why the source of record should be an inspectable knowledge base, not the skill.
The Foundry's machine in one read — a Knowledge Base of Molds cast into frozen, provenance-stamped target artifacts.
The design pressures every Foundry obeys, abstracted from the diff between its two instances — the discipline a domain inherits before it extends the substrate.
The principles incarnated — how the two Foundries' actual setup and implementation decisions enact each one. The one Pattern page that goes concrete on purpose.
What every Foundry shares (the substrate) versus what each domain adds (the extension surface) — the pattern is a base to extend, not a template to stamp.
The imperative companion to Anatomy — how to stand up a new Foundry, step by step. The substrate is given; the work is bringing domain knowledge and extending the base with what the domain needs.
Canonical definitions for the Foundry Pattern's vocabulary — the invariant substrate, casting and provenance, the per-domain extension surface, and the source-vs-package distinction.