Final decisionPilot/final doorPilot tolerates warnings; Final formula blocks critical missing.Origin: Yolia's safe educational catalogExact route: /biblioteca?ruta=decision/reglas/pilot_final_gate FULL TOPICPilot/final door Name and classification of the rule Pilot/final gate. Final Decision sheet that documents this rule of the final audit category for the complete process, 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 This is the sheet that explains the "Pilot/final gate" rule: Pilot tolerates warnings; final formula blocks critical missing items. This rule is part of the final audit category of the complete process within the complete catalog of Final Decisions Yolia reviews in each case analyzed. What exactly this rule evaluates This rule specifically evaluates whether the final audit data of the complete process 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 pilot tolerates warnings; the final formula blocks critical missing items. 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 Pilot tolerates warnings; final formula blocks critical missing data. Yolia checks this point before trusting a decision. If important information is missing, Yolia must lower confidence or stop instead of inventing, as a first level of understanding within the Library. Medium explanation The pilot tolerates warnings; the final formula blocks critical gaps. 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 The pilot tolerates warnings; the final formula blocks critical gaps. 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 final-audit-of-the-complete-process datum 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 final-audit category of the Final Decision catalog's complete process, 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 final audit of the complete process 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 the final audit of the complete process 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 final audit data of the complete process 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 final audit data of the complete process, 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 pilot mode tolerates warnings; the final formula blocks critical missing items, 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 Final Audit of the Complete Process, related topic — Audit Engine, related engine — Pilot/Final Gate, related entry within Yolia's complete Final Decision catalog for the process, consult other Final Decision entries within the Library.