Final decisionFrequency of extreme maximumsIt does not block by an isolated maxim; measures frequency and percentiles.Origin: Yolia's safe educational catalogExact route: /biblioteca?ruta=decision/reglas/max_temp_frequency FULL TOPICFrequency of extreme maximums Name and classification of the rule Frequency of extreme highs. Final Decision sheet that documents this rule of the climate and climate history category, with critical severity, part of the complete catalog of Final Decision rules that Yolia reviews before approving any formula generated for a real case within the system. What this rule is within the catalog It's the entry that explains the "Frequency of extreme maximums" rule: It doesn't block for a single isolated maximum; it measures frequency and percentiles. This rule is part of the climate and climate-history category within Yolia's complete Final Decision catalog that Yolia reviews in every analyzed case. What exactly this rule evaluates This rule specifically evaluates whether the climate and climate history data is present and sufficient for the decision engine to proceed with confidence, being classified as critical severity within the system's complete catalog of Final Decision rules. Why it matters within the complete process It is key because it does not block based on an isolated maximum; it measures frequency and percentiles. Without this verified data or condition, the rest of the analysis within the case loses precision and the decision engine cannot sustain the confidence level it declares to the user in the final formula delivered. Easy explanation It does not block based on a single maximum in isolation; it measures frequency and percentiles. Yolia checks this point before trusting a decision. If important information is missing, Yolia should lower confidence or stop instead of guessing, designed for someone looking for a general, accessible overview. Medium explanation It doesn't block on a single isolated maximum; it measures frequency and percentiles. This rule works as a gate: it changes which alternatives remain reasonable and which data is worth obtaining next. A decision changes when the crop, the stage, the environment, or the data quality changes. Advanced explanation It doesn't block on a single isolated maximum; it measures frequency and percentiles. The rule takes part in a validation chain with identity, context, phenology, evidence, compatibility, biological capacity, and safety limits. The reason for acceptance/blocking is explained without publishing weights. Mechanism behind this rule The mechanism behind this rule is that the decision engine compares the reported climate and climate-history data against the minimum threshold needed, blocking or warning according to the critical severity declared for this rule within the system's complete catalog. When and where this rule applies This rule applies within the climate and climate-history category of the Final Decision catalog, being mandatory in every case, regardless of the species or particular context being analyzed at that moment within Yolia's complete system. What other rules or engines it relates to It relates to the rest of the rules in the climate and climate history category and to the Audit Engine, which verifies that all the catalog's mandatory rules have been met before approving the final formula generated for the case being analyzed. Relevant differences between catalog species The principle of this rule is identical for the catalog's 4 species; what changes is the specific threshold or tolerance for climate and climate history depending on the particular species being treated within the case being analyzed at that point in the complete process. How it is observed in practice on a case In practice, this is observed when the system reviews the climate and climate history data reported for the case and decides whether to proceed with full confidence, lower its confidence level, or halt the process until the missing data is obtained for the case being analyzed. What happens if this rule is ignored If this rule is ignored, the engine could proceed with a formula based on incomplete or missing climate and climate history data, increasing the risk of delivering a less accurate or outright wrong recommendation for the actual case being analyzed. How Yolia uses it within the process Yolia uses this as part of the validation chain it reviews before approving a formula, applying this critical-severity rule in both pilot and final mode, though with a different tolerance level depending on the case's active mode, part of the structured process the system follows. Common interpretation errors Thinking this rule is just an administrative formality — in reality it doesn't block based on an isolated maximum; it measures frequency and percentiles, which makes it an actual condition that directly affects the quality of the final formula delivered to the user within the case being analyzed. Evidence and limits of current knowledge Its specification acknowledges that the exact threshold that triggers this rule can vary depending on the reported context, without publishing the internal weights or the exact private thresholds, leaving room for this logic to continue being refined within Yolia's system. Related topics and rules Climate and climate history, related topic — Audit Engine, related engine — Pilot/final gate, related entry within Yolia's complete Final Decision catalog for the process, topics worth reviewing together within the catalog.