SandboxHow to create a temporary caseOrigin: Yolia's safe educational catalogExact route: /biblioteca?ruta=sandbox/guias/sandbox-custom FULL PROFILEThe 17 points of this moduleEach section opens separately — tap the title to expand it. 1. Name and what screen it explains How to Create a Temporary Case. Sandbox guide that explains that here the user provides the basic data without inventing what they don't know, a central topic in the complete catalog of Sandbox guides in Yolia's scientific Library, part of the set of engines that process each case. 2. What this guide is within the Sandbox It is the guide that explains that here you provide the basic data, and if you don't know something, you should leave it blank rather than invent it, since Yolia needs to distinguish what you know from what is still missing before correctly interpreting the complete case, within the complete process of analyzing a case. 3. What you should look at first on this screen Complete one screen at a time and read the available help, using the underlined words if you don't understand something; if you don't know the substrate's pH, for example, don't just put 7 to fill in the field without verifying it first, inputs the system treats with their declared origin. 4. Why it matters to understand this before moving on It is key because a made-up measurement can lead to a wrong conclusion, while a missing measurement simply reduces confidence without distorting the result, this distinction being central throughout the entire guide, a factor that shapes the quality of the final recommendation. 5. Easy explanation Here you provide the basic data. If you don't know something, leave it blank rather than inventing it. Yolia needs to distinguish what you know from what is still missing. Complete one screen at a time and read the hints before continuing to the next block, designed for someone looking for a general, accessible overview. 6. Medium explanation The form separates identity, stage, goals, environment, and measurements; each block reduces ambiguity before interpreting the case, presenting the mandatory data first and the optional available measurements afterward, for anyone who already knows the basics and wants to go deeper. 7. Advanced explanation The intake preserves provenance and distinguishes declared, measured, and missing data; specialized goals go through risk and compatibility filters, since input quality limits the inferential quality of subsequent analysis, as a technical closing of the three levels of explanation. 8. What Yolia observes at this step Yolia observes whether the user completes the mandatory data before optional measurements and whether they confirm the context at the end, evaluating validity, completeness, consistency, and applicability before treating a value as evidence, a risk the engine considers before letting a result through. 9. Related key concepts The key concepts of this guide are data quality, pH, electrical conductivity, phenology, and traceability — five ideas that explain why an electrical conductivity reading without a method, unit, or matrix is not the same as one correctly traced, an important nuance for correctly interpreting this engine. 10. What other guide or engine it connects to It connects with the How to Read the Record's Home guide, which summarizes the case once created, and with the Evidence Engine, which verifies the provenance of every data point entered before it is used in the case's analysis, a link showing how the different engines coordinate. 11. Relevant differences between catalog species The principle of not making up data is identical for the catalog's 4 species; what changes are the specific relevant fields depending on the particular species selected at the start of the temporary case creation form, a detail worth keeping in mind depending on the case analyzed. 12. How this is practiced within the Sandbox It's practiced by filling out the form step by step, with the option to go back and choose a prepared case from this same screen if the user prefers to explore an already-existing example instead of creating a completely new one, an element visible when reviewing how Yolia reached its conclusion. 13. What happens if this screen is ignored If this guide is ignored and measurements are invented, the system could treat an unverified value as if it were a real measured datum, generating an interpretation of the case that doesn't match the plant's real condition, a problem other engines couldn't correct on their own. 14. How Yolia uses it within the complete journey Yolia uses this to build a temporary case with the best possible data quality, always prioritizing honesty over artificial completeness, since a missing data point is preferable to a fabricated one within the complete system, a concrete application within Yolia's complete reasoning. 15. Common interpretation errors Thinking that leaving a field empty is worse than making up an approximate value — actually a made-up measurement can lead to a wrong conclusion, while an empty field simply lowers the system's confidence, a misinterpretation worth avoiding beforehand. 16. Evidence and limits of current knowledge Its specification acknowledges that data created in the Demo remains temporary and isn't saved as a real productive case, with room for this distinction to keep being communicated clearly within the Yolia system, with aspects that continue to be documented in more detail. 17. Related topics and guides How to Read the Record's Home, related guide — Evidence Engine, related engine — How to Choose a Laboratory, related guide within Yolia's complete Library catalog for cultivation, topics worth reviewing together within the catalog.