Final decisionData quality/traceabilityWithout quality data, pilot can warn; final must be strict.Origin: Yolia's safe educational catalogExact route: /biblioteca?ruta=decision/reglas/regional_data_quality FULL TOPICData quality/traceability Name and classification of the rule Data quality/traceability. Final Decision Sheet documenting this rule in the data quality and traceability category, with critical severity, part of the complete catalog of Final Decision rules Yolia reviews before approving any formula generated for a real case. What this rule is within the catalog It is the sheet that explains the "Data quality/traceability" rule: Without quality data, pilot mode can warn; final mode must be strict. This rule is part of the data quality and traceability category within the complete Final Decision catalog Yolia reviews in every case analyzed. What exactly this rule evaluates This rule specifically evaluates whether the data quality and traceability information 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 without quality data, pilot can warn; final must be strict. 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 Without quality data, the pilot may warn; the final one must be strict. Yolia checks this point before trusting a decision. If important information is missing, Yolia must lower confidence or stop rather than make things up, explained in simple language for those new to the topic. Medium explanation Without quality data, the pilot may warn; the final must be strict. 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 Without quality data, the pilot may warn; the final must be strict. The rule participates in a validation chain with identity, context, phenology, evidence, compatibility, biological capacity and safety limits. The cause of acceptance/blocking is explained without publishing weights. Mechanism behind this rule The mechanism behind this rule is that the decision engine compares the reported data-quality-and-traceability figure 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 data quality and traceability category of the Final Decision catalog, being mandatory compliance in every case, regardless of the species or the 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 data quality and traceability category and to the Audit Engine, which verifies that all mandatory catalog 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 data quality and traceability according to the particular species treated within the case being analyzed at that moment of the complete process. How it is observed in practice on a case It is observed in practice when the system reviews the reported data quality and traceability information for the case and decides whether to continue with full confidence, lower its confidence level, or halt the process until the missing data is obtained within 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 data quality and traceability information, increasing the risk of delivering a less precise or outright wrong recommendation for the real 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 that this rule is just an administrative formality — in reality without quality data, pilot mode can warn; final mode must be strict, which makes it a real 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 Data quality and traceability, related topic — Audit Engine, related engine — Pilot/final gate, related entry within Yolia's complete Final Decision catalog for the process, see also the directly related rules and engines.