CombinationsHard block: water-retaining mucilage + waterlogged substrateBloqueo duro: mucílago retenedor + sustrato encharcado.Origin: Yolia's safe educational catalogExact route: /biblioteca?ruta=combinaciones/mucilage_waterlogging FULL TOPICHard block: water-retaining mucilage + waterlogged substrate Name and classification of the combination Hard block: water-retaining mucilage + waterlogged substrate. Combinations Sheet explaining why water-retention modules are not used in an already saturated substrate, a topic in Yolia's Combinations catalog for growing, present within the system's module relationship logic. What this relationship is within the catalog It's the entry that explains that water-retention modules, chia or flaxseed mucilage, are designed for fast-draining substrate, and using them in a substrate that already retains too much water can cause real waterlogging, within the complete process of building a formula. What modules or contexts it involves It involves the Mucilage Biofilm Retention module against the context of waterlogging and low oxygen, blocking its use when the reported substrate type already retains excess water within the case being analyzed, information that later gets cross-checked with the catalog's other rules. Why it matters within the complete process It is key because in a clayey or poorly draining substrate, retaining more water is counterproductive, not beneficial, this rule being what prevents the engine from suggesting this module under conditions where it would worsen the real problem, being a necessary piece of the case's complete reasoning. Easy explanation Water-retention modules, chia or flax mucilage, are designed for fast-draining substrate — using them in a substrate that already retains too much water can cause real waterlogging and suffocate the root from lack of oxygen, designed for those seeking a general, accessible idea. Medium explanation It is the reason these modules ask about the substrate type before activating; in a clay or poorly draining substrate, retaining more water is counterproductive, not beneficial, for the plant grown in the analyzed case, with more technical detail than the earlier introductory level. Advanced explanation A hard-block functional relationship by context, conditioned on the reported substrate type; the engine specifically blocks this module when the substrate already shows signs of excessive water retention in the specific case, aimed at those seeking to understand the mechanism with precision. Mechanism behind this relationship The mechanism behind this rule is that adding more water retention to an already saturated substrate displaces the oxygen available in the root zone, causing anoxia and potential damage to the grown plant's root in the case, a link the engine considers before letting a result through. When and where this rule applies This rule is specifically triggered when the reported context includes waterlogging or low oxygen in the substrate, being a conditional gate that directly depends on the substrate type declared by the user, a condition openly stated to avoid mistaken decisions. Which engines it relates to It relates to Root Architecture, which details the root's general condition, and to the Risk Engine, which evaluates the severity of a reported waterlogging event within the case currently being analyzed, a relationship that helps understand the overall picture of the analysis. Relevant differences between catalog species The principle of blocking this module under waterlogging is identical for the catalog's 4 species; what changes is the relative tolerance to waterlogging according to the particular species cultivated within the analyzed case, a detail worth keeping in mind depending on the case being analyzed. How it is observed in practice on a case It's observed in practice when the system withholds or rejects the retaining-mucilage module specifically when the user reports a poorly draining substrate or visible signs of waterlogging in the case analyzed, something reflected in the final formula delivered to the user. What happens if this relationship is ignored If this rule is ignored, the substrate would retain even more water than it already has in excess, worsening the existing waterlogging and increasing the risk that the root suffers from lack of available oxygen in the root zone, a risk that grows if this relationship is not taken into account in time. How Yolia uses it within the process Yolia uses this as a conditional gate within the Compatibility Engine, always asking about the substrate type before considering this module, avoiding applying it when the reported context indicates a waterlogging risk, a concrete application within Yolia's complete reasoning process. Common interpretation errors Thinking that a water-retention module always helps against any stress signal in the plant — if the substrate already retains too much water, this same module worsens the problem instead of helping resolve the actual stress, a frequent confusion worth clarifying about this relationship. Evidence and limits of current knowledge Its specification recognizes that the exact retention threshold that triggers this block depends on the specific reported substrate type, with room for this precision to keep being refined within Yolia's complete system, although the exact design remains subject to ongoing improvement. Related topics and modules RH-01/TH-01 Water Retention, related module — Oxygen in the root zone, related topic — Root Architecture, related engine within Yolia's complete catalog of Engines, topics worth reviewing together within the catalog.