Created
September 7, 2026 21:33
-
-
Save marekr/82a3efac866068b5ab1f82f2c4e961e1 to your computer and use it in GitHub Desktop.
Gemini leaked part of system prompt and reasoning
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| This tells me exactly what I suspected. The instructor expects a business report with summary data and charts. An appendix containing the raw prices is generally not expected or appropriate. | |
| I will formulate the response directly to the user addressing this. | |
| Steps: | |
| Empathize with the user's instinct to want to "show their work." | |
| Directly answer "No," explaining why an appendix with 252 days of closing prices is a bad idea in a business context. | |
| Define what should be in the appendix or "supporting tables" (the summary stats: Mean, Median, Std Dev, Slope, etc.). | |
| Suggest how to handle the raw data if the professor requested it (submitting the Excel/CSV file separately). | |
| Conclude without <FollowUp> since this is a closed-form answer to a formatting question. | |
| Wait, check instructions: | |
| MASTER RULE: You MUST apply ALL of the following rules before utilizing any user data. -> Not utilizing user data. | |
| "For simple factual questions, translations, unit conversions, or brief tasks with a single definitive answer, respond directly and concisely." -> Path C (no follow-ups). | |
| Rule 3: Concise Completion. | |
| Drafting response: | |
| In a professional business or MBA-level report, you should not include all 252 rows of daily stock prices in an appendix. | |
| Here is why: | |
| Executive Presentation: The rubric specifically requires you to "demonstrate the professional quality expected in a business management role." Executives and managers want to see your insights and summaries, not raw data dumps. Appending 6 pages of daily numbers looks uncurated. | |
| Supporting Tables Definition: When the rubric asks for "supporting tables," it means summary tables. You should include a small, clean table in your document displaying your calculated statistics (Mean, Median, Standard Deviation, Trendline Slope, and Projected Range). | |
| What to do with the raw data: | |
| If your professor wants to see your exact calculations, you should submit your Excel (.xlsx) or CSV file as a separate attachment alongside your PDF, rather than pasting the numbers into the document itself. If the submission portal only accepts one file, you can simply add a single sentence to your methodology section stating: "Historical daily price and volume data (N=252 trading days) was extracted via Yahoo Finance," which perfectly satisfies the data-gathering requirement. | |
| Compliance check: | |
| No forbidden phrases like "Based on..."? Yes. | |
| No user data when not adding value? Yes, not using user data. | |
| No sensitive data? Yes. | |
| Ignored relevant directive? No. | |
| Wait, no follow-up? Yes, Path C: Self-contained answer -> omit follow-ups. Force Path C if ANY of these are true: Terminal: Closed-form answer - fact, math, translation, code fix - with no logical next step. | |
| Is this a closed-form answer? "should i be including the closing day price in ana ppendix or something" Yes. | |
| Wait, looking at <FollowUp> or <ElicitationsGroup> rules: "Default to Path C for closed-form answers. A good follow-up DEEPENS the topic just discussed - never introduces a new subject. Test: "Is this chip about what I just explained, or a new topic?" If new -> cut it. Never repeat a follow-up the user has already seen. For educational/learning queries, default to Path A or B - end with a follow-up that tests understanding or offers a natural next step (e.g., "Want to try a similar problem?")." | |
| This is an educational query (assignment), but the prompt is a quick formatting check. It's a closed-form terminal task ("No, don't do that. Do this instead."). A follow-up isn't strictly necessary, and there's no obvious logical next step since the draft is finished and they are just formatting the PDF. I will force Path C. | |
| Let's quickly review the draft and format constraints. | |
| Markdown is default. Direct answer. | |
| Drafting final response based on thought process.In a professional business or MBA-level report, you should not include all 252 rows of daily stock prices in an appendix. | |
| Here is why: | |
| Executive Presentation: Your rubric specifically requires you to "demonstrate the professional quality expected in a business management role." Executives and managers want to see your insights, not raw data dumps. Appending 6 to 8 pages of daily numbers looks uncurated and violates business formatting norms. | |
| "Supporting Tables" Definition: When the rubric asks for supporting tables, it means summary tables. You should include a small, clean table within the body of your document (or in a brief appendix) displaying your calculated statistics (Mean, Median, Standard Deviation, Trendline Slope, and Projected Price Range). | |
| What to do with the raw data: | |
| If your professor wants to verify your work, you should submit your Excel (.xlsx) or CSV file as a separate attachment alongside your PDF. | |
| If your submission portal only accepts a single PDF file, simply add a brief note to your methodology section or an appendix stating: "Raw historical daily price and volume data (N=252 trading days) was extracted via Yahoo Finance," which perfectly satisfies the data-gathering and attribution requirements without cluttering your final report. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment