Merge pull request #1167 from buster-so/forecast-updates

python-limitation-removed
This commit is contained in:
Blake Rouse 2025-09-26 08:17:00 -06:00 committed by GitHub
commit 152f95c768
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
4 changed files with 11 additions and 10 deletions

View File

@ -485,7 +485,7 @@ You operate in a loop to complete tasks:
<system_limitations>
- The system is read-only and you cannot write to databases.
- Only the following chart types are supported: table, line, bar, combo, pie/donut, number cards, and scatter plot. Other chart types are not supported.
- You cannot write Python code or perform advanced analyses such as forecasting or modeling.
- You cannot write Python.
- You cannot highlight or flag specific elements (e.g., lines, bars, cells) within visualizations; it can only control the general color theme.
- You cannot attach specific colors to specific elements within visualizations. Only general color themes are supported.
- Individual metrics cannot include additional descriptions, assumptions, or commentary.

View File

@ -799,7 +799,7 @@ If all true → proceed to submit prep for Asset Creation with `submitThoughts`.
<system_limitations>
- The system is read-only and cannot write to databases.
- Only the following chart types are supported: table, line, bar, combo, pie/donut, number cards, and scatter plot. Other chart types are not supported.
- The system cannot write Python code or perform advanced analyses such as forecasting or modeling.
- The system cannot write Python.
- You cannot highlight or flag specific elements (e.g., lines, bars, cells) within visualizations;
- You cannot attach specific colors to specific elements within visualizations. Only general color themes are supported.
- Individual metrics cannot include additional descriptions, assumptions, or commentary.

View File

@ -652,7 +652,7 @@ When in doubt, be more thorough rather than less. Reports are the default becaus
<system_limitations>
- The system is read-only and cannot write to databases.
- Only the following chart types are supported: table, line, bar, combo, pie/donut, number cards, and scatter plot. Other chart types are not supported.
- The system cannot write Python code or perform advanced analyses such as forecasting or modeling.
- The system cannot write Python.
- You cannot highlight or flag specific elements (e.g., lines, bars, cells) within visualizations;
- You cannot attach specific colors to specific elements within visualizations. Only general color themes are supported.
- Individual metrics cannot include additional descriptions, assumptions, or commentary.

View File

@ -122,11 +122,12 @@ The TODO list should break down each aspect of the user request into tasks, base
```
### User Request: "what will sales be in Q4. oh and can you give me a separate line chart that shows me monthly sales over the last 6 months?"
```
[ ] Address inability to do forecasts
[ ] Determine how "sales" is identified
[ ] Determine how to group sales by month
[ ] Determine the visualization type and axes for each chart
[ ] Determine if the user is asking for a single metric, a report, or a dashboard.
[ ] Determine how "sales" is identified
[ ] Determine how to forecast sales for Q4
[ ] Determine how to group sales by month
[ ] Determine the time frame for the last 6 months
[ ] Determine the visualization type and axes for the line chart
[ ] Determine if the user is asking for a single metric, a report, or a dashboard.
```
### User Request: "What's the influence of unicorn sightings on our sales?"
```
@ -150,8 +151,8 @@ The TODO list should break down each aspect of the user request into tasks, base
```
---
### System Limitations
- The system cannot do unsupported operations like writing python code, building forecasts, or running "what-if" hypothetical analysis.
- If the user asks for these, include a TODO item like `Address inability to do forecasts`.
- The system cannot do unsupported operations like writing python code.
- If the user asks you to use python, include a TODO item like `Address inability to use python`.
- For non-analytics requests (e.g., greetings, exploratory questions, meta-questions), you should **not** default to "inability" responses. Instead, produce TODO items that reflect the conversational nature of the request.
- Reports from previous messages should never be edited, instead new reports should be made with any changes. Even if a user says 'add X to a report' or 'make Y change to a report', a new report should be made with the changes rather than editing the original report
- If the users requests that a change should be made to a report include this as an item in the TODO list.