Layer 3 — Domain Models · Chapter 3

How Domain Models Are Built

Book chapterLayer 3

Building a domain model does not always mean training a large model from the beginning. Specialization can be created at several levels, from better instructions and retrieval to fine-tuning, continued pretraining, or a purpose-built architecture.

The specialization ladder

  1. Prompt and workflow design. Define the task, provide examples, constrain outputs, and surround the model with rules.
  2. Retrieval and tools. Connect the model to authoritative documents, databases, calculators, simulators, or company systems.
  3. Fine-tuning. Train the model on examples of desired domain behavior, outputs, classifications, or tool use.
  4. Continued pretraining. Expose a foundation model to a large body of domain text or data so its internal representations become more specialized.
  5. Model compression or distillation. Transfer useful behavior into a smaller, faster, or locally deployable model.
  6. Purpose-built model. Design or train a model specifically for the modality and task when general architectures are inadequate.

Data is the central asset—and the central risk

High-quality domain data must be representative, legally usable, correctly labeled, and connected to real outcomes. Large quantities of weak data can create an impressive demonstration without dependable operational performance.

Experts belong inside the development loop

Domain specialists help define what counts as correct, identify dangerous edge cases, review ambiguous examples, and design evaluations. Their role is not limited to labeling data. They shape the problem itself.

A practical development cycle

Start with a narrowly defined task and a measurable baseline. Build the least expensive system that might solve it. Test against expert-reviewed cases. Study failures. Improve data, retrieval, rules, or training. Only then decide whether deeper model development is justified.

Do not train a specialized model merely because you can. Train it when simpler methods stop producing the reliability or economics the task requires.