Text-only system boundary, training stages, and training-time evaluation in practiceDefining the text-only system boundaryTraining stages require different evaluation lensesThe training-time evaluation loopData quality gates: Provenance, deduplication, toxicity, format consistency, instruction hygieneProvenance and deduplicationToxicity and safety content screeningFormat consistency and parser stabilityInstruction hygieneCoverage and representativeness across slicesCoverage is slice completeness, not more tokensLong-tail behavior and edge-case budgetsLeakage and contamination: Overlap, benchmark contamination, and memorization riskWhat counts as leakage in practiceBenchmark contamination is leakage with higher stakesDetecting overlap at scalePretraining objective validation: What training loss can and cannot tell youInstruction-tuning evaluation: Instruction-following, constraint adherence, and structured outputsTreat instruction following as a set of behaviorsConstraint adherence: evaluate rules as explicit checks where possibleStructured outputs as a first-class axisPreference tuning evaluation: Trade-offs, over-refusal, and mode collapseMake trade-offs explicit with a small drift scorecardOver-refusal is a slice problem, not a global problemMode collapse: "safe but unhelpful" repliesVerbosity driftGating preference tuning outcomesTask-specific fine-tuning: Accuracy, error taxonomies, and edge-case budgetsSafety alignment during training: Harmful completion rate and jailbreak robustnessHarmful completion rate and refusal outcomesJailbreak robustnessGeneralization and robustness: Out-of-distribution (OOD) sets, paraphrase stability, and adversarial suitesEfficiency signals that matter later: Tokens, lengths, and compute implicationsRelease readiness: Thresholds, model cards, dataset cards, and changelogsDecision framework: Selecting a stronger base model versus fine-tuningSummary