Spaces:
Runtime error
Runtime error
V9.1.0: Prevent Client Crashes - AI Diet (40-char limit)
Browse files- prompts.py +6 -2
prompts.py
CHANGED
|
@@ -605,11 +605,15 @@ def get_master_prompt_v860(category: str = "", problem_text: str = ""):
|
|
| 605 |
* Good: "ืืื ืืืฆืื ื ืงืืืช ืงืืฆืื ื ืืืืจ ืืช ืืคืื ืงืฆืื. ืืืืืื ืฉืื ืื ื, ื ืฉืชืืฉ ืืืื ืืื ื ืืืืืจ ืฉ... ื ืืืืจ ืืช ืืืื ื ืื ืคืจื ืืืช ืืืื ื ืื ืคืจื:"
|
| 606 |
3. **COMPLETE THE MISSION (ANTI-TRUNCATION):** Never abandon the task. You MUST reach the final numeric/algebraic answer. If asked for extrema, you must find x, y, and classify (max/min).
|
| 607 |
4. **ANTI-ASCII-ART RULE (V8.8.8):** NEVER attempt to draw or sketch a graph using text characters, keyboard symbols, slashes, or ASCII art (e.g., do not use |, /, \\, -, _ to make a picture). If asked to sketch a graph, ONLY describe its mathematical properties in text (e.g., intersections, asymptotes).
|
| 608 |
-
5. **CONTENT TYPE SEPARATION (IRON LAW - V9.
|
| 609 |
- All LaTeX math and steps must go inside the `block_math` list for clear UI display.
|
| 610 |
- `block_math` MUST contain ONLY PURE MATH. Absolutely NO HEBREW LETTERS, no words, no explanations.
|
| 611 |
- Do NOT put coordinate lists or points like `A(0,1), B(2,3)` in `block_math`. Points and their names MUST stay in `content_mixed`.
|
| 612 |
-
-
|
|
|
|
|
|
|
|
|
|
|
|
|
| 613 |
- Descriptions and casual variables must stay in `content_mixed`.
|
| 614 |
- NEVER write Hebrew inside `block_math` or `final_answer`. (CRITICAL: violates the algebraic validator contract).
|
| 615 |
6. **ANTI-TABLE RULE & EXTREMA ANALYSIS:**
|
|
|
|
| 605 |
* Good: "ืืื ืืืฆืื ื ืงืืืช ืงืืฆืื ื ืืืืจ ืืช ืืคืื ืงืฆืื. ืืืืืื ืฉืื ืื ื, ื ืฉืชืืฉ ืืืื ืืื ื ืืืืืจ ืฉ... ื ืืืืจ ืืช ืืืื ื ืื ืคืจื ืืืช ืืืื ื ืื ืคืจื:"
|
| 606 |
3. **COMPLETE THE MISSION (ANTI-TRUNCATION):** Never abandon the task. You MUST reach the final numeric/algebraic answer. If asked for extrema, you must find x, y, and classify (max/min).
|
| 607 |
4. **ANTI-ASCII-ART RULE (V8.8.8):** NEVER attempt to draw or sketch a graph using text characters, keyboard symbols, slashes, or ASCII art (e.g., do not use |, /, \\, -, _ to make a picture). If asked to sketch a graph, ONLY describe its mathematical properties in text (e.g., intersections, asymptotes).
|
| 608 |
+
5. **CONTENT TYPE SEPARATION (IRON LAW - V9.1.0):**
|
| 609 |
- All LaTeX math and steps must go inside the `block_math` list for clear UI display.
|
| 610 |
- `block_math` MUST contain ONLY PURE MATH. Absolutely NO HEBREW LETTERS, no words, no explanations.
|
| 611 |
- Do NOT put coordinate lists or points like `A(0,1), B(2,3)` in `block_math`. Points and their names MUST stay in `content_mixed`.
|
| 612 |
+
- EXTREME SIMPLICITY MANDATE FOR MATH BLOCKS:
|
| 613 |
+
* `block_math` MUST contain exactly ONE mathematical operation per step.
|
| 614 |
+
* NEVER use commas (,) to separate multiple equations.
|
| 615 |
+
* NEVER chain equations (e.g., NO `x = 2 + 2 = 4`). Break EVERY '=' into a new JSON step.
|
| 616 |
+
* MAXIMUM LENGTH: A single `block_math` string MUST NEVER exceed 40 characters. If a calculation is longer (like a complex fraction), you MUST break it down into intermediate variables across multiple steps.
|
| 617 |
- Descriptions and casual variables must stay in `content_mixed`.
|
| 618 |
- NEVER write Hebrew inside `block_math` or `final_answer`. (CRITICAL: violates the algebraic validator contract).
|
| 619 |
6. **ANTI-TABLE RULE & EXTREMA ANALYSIS:**
|