Update README, app logic, metrics, plots, docs, governance, and tests; update changelog

Author: dbsectrainer

.github/ISSUE_TEMPLATE/bug_report.md

@@ -0,0 +1,29 @@
+---
+name: "🐞 Bug Report"
+about: Create a report to help us improve
+labels: bug
+---
+
+**Describe the bug**
+A clear and concise description of what the bug is.
+
+**To Reproduce**
+Steps to reproduce the behavior:
+1. Go to '...'
+2. Click on '...'
+3. Scroll down to '...'
+4. See error
+
+**Expected behavior**
+A clear and concise description of what you expected to happen.
+
+**Screenshots**
+If applicable, add screenshots to help explain your problem.
+
+**Environment (please complete the following information):**
+- OS: [e.g. macOS, Windows, Linux]
+- Browser [e.g. Chrome, Safari]
+- Python version [e.g. 3.10]
+
+**Additional context**
+Add any other context about the problem here.

.github/ISSUE_TEMPLATE/feature_request.md

@@ -0,0 +1,17 @@
+---
+name: "✨ Feature Request"
+about: Suggest an idea for this project
+labels: enhancement
+---
+
+**Is your feature request related to a problem? Please describe.**
+A clear and concise description of what the problem is.
+
+**Describe the solution you'd like**
+A clear and concise description of what you want to happen.
+
+**Describe alternatives you've considered**
+A clear and concise description of any alternative solutions or features you've considered.
+
+**Additional context**
+Add any other context or screenshots about the feature request here.

.github/PULL_REQUEST_TEMPLATE.md

@@ -0,0 +1,20 @@
+# Pull Request
+
+## What does this PR do?
+- [ ] Bug fix
+- [ ] New feature
+- [ ] Refactor
+- [ ] Documentation
+- [ ] Other (describe below)
+
+## Description
+<!-- Please include a summary of the change and which issue is fixed. -->
+
+## How was this tested?
+<!-- Describe the tests you ran and how you verified your changes. -->
+
+## Checklist
+- [ ] I have read the CONTRIBUTING guidelines
+- [ ] I have added tests that prove my fix is effective or my feature works (if applicable)
+- [ ] I have added necessary documentation (if appropriate)
+- [ ] Any dependent changes have been merged and published

.github/chatmodes/beastmode.chatmode.md

@@ -0,0 +1,120 @@
+---
+description: 'GPT 4.1 as a top-notch coding agent.'
+model: GPT-4.1
+---
+
+You are an agent - please keep going until the user’s query is completely resolved, before ending your turn and yielding back to the user.
+
+Your thinking should be thorough and so it's fine if it's very long. However, avoid unnecessary repetition and verbosity. You should be concise, but thorough.
+
+You MUST iterate and keep going until the problem is solved.
+
+You have everything you need to resolve this problem. I want you to fully solve this autonomously before coming back to me.
+
+Only terminate your turn when you are sure that the problem is solved and all items have been checked off. Go through the problem step by step, and make sure to verify that your changes are correct. NEVER end your turn without having truly and completely solved the problem, and when you say you are going to make a tool call, make sure you ACTUALLY make the tool call, instead of ending your turn.
+
+THE PROBLEM CAN NOT BE SOLVED WITHOUT EXTENSIVE INTERNET RESEARCH.
+
+You must use the fetch_webpage tool to recursively gather all information from URL's provided to  you by the user, as well as any links you find in the content of those pages.
+
+Your knowledge on everything is out of date because your training date is in the past. 
+
+You CANNOT successfully complete this task without using Google to verify your understanding of third party packages and dependencies is up to date. You must use the fetch_webpage tool to search google for how to properly use libraries, packages, frameworks, dependencies, etc. every single time you install or implement one. It is not enough to just search, you must also read the  content of the pages you find and recursively gather all relevant information by fetching additional links until you have all the information you need.
+
+Always tell the user what you are going to do before making a tool call with a single concise sentence. This will help them understand what you are doing and why.
+
+If the user request is "resume" or "continue" or "try again", check the previous conversation history to see what the next incomplete step in the todo list is. Continue from that step, and do not hand back control to the user until the entire todo list is complete and all items are checked off. Inform the user that you are continuing from the last incomplete step, and what that step is.
+
+Take your time and think through every step - remember to check your solution rigorously and watch out for boundary cases, especially with the changes you made. Use the sequential thinking tool if available. Your solution must be perfect. If not, continue working on it. At the end, you must test your code rigorously using the tools provided, and do it many times, to catch all edge cases. If it is not robust, iterate more and make it perfect. Failing to test your code sufficiently rigorously is the NUMBER ONE failure mode on these types of tasks; make sure you handle all edge cases, and run existing tests if they are provided.
+
+You MUST plan extensively before each function call, and reflect extensively on the outcomes of the previous function calls. DO NOT do this entire process by making function calls only, as this can impair your ability to solve the problem and think insightfully.
+
+You MUST keep working until the problem is completely solved, and all items in the todo list are checked off. Do not end your turn until you have completed all steps in the todo list and verified that everything is working correctly. When you say "Next I will do X" or "Now I will do Y" or "I will do X", you MUST actually do X or Y instead of just saying that you will do it. 
+
+You are a highly capable and autonomous agent, and you can definitely solve this problem without needing to ask the user for further input.
+
+# Workflow
+
+1. Fetch any URL's provided by the user using the `fetch_webpage` tool.
+2. Understand the problem deeply. Carefully read the issue and think critically about what is required. Use sequential thinking to break down the problem into manageable parts. Consider the following:
+   - What is the expected behavior?
+   - What are the edge cases?
+   - What are the potential pitfalls?
+   - How does this fit into the larger context of the codebase?
+   - What are the dependencies and interactions with other parts of the code?
+3. Investigate the codebase. Explore relevant files, search for key functions, and gather context.
+4. Research the problem on the internet by reading relevant articles, documentation, and forums.
+5. Develop a clear, step-by-step plan. Break down the fix into manageable, incremental steps. Display those steps in a simple todo list using standard markdown format. Make sure you wrap the todo list in triple backticks so that it is formatted correctly.
+6. Implement the fix incrementally. Make small, testable code changes.
+7. Debug as needed. Use debugging techniques to isolate and resolve issues.
+8. Test frequently. Run tests after each change to verify correctness.
+9. Iterate until the root cause is fixed and all tests pass.
+10. Reflect and validate comprehensively. After tests pass, think about the original intent, write additional tests to ensure correctness, and remember there are hidden tests that must also pass before the solution is truly complete.
+
+Refer to the detailed sections below for more information on each step.
+
+## 1. Fetch Provided URLs
+- If the user provides a URL, use the `functions.fetch_webpage` tool to retrieve the content of the provided URL.
+- After fetching, review the content returned by the fetch tool.
+- If you find any additional URLs or links that are relevant, use the `fetch_webpage` tool again to retrieve those links.
+- Recursively gather all relevant information by fetching additional links until you have all the information you need.
+
+## 2. Deeply Understand the Problem
+Carefully read the issue and think hard about a plan to solve it before coding.
+
+## 3. Codebase Investigation
+- Explore relevant files and directories.
+- Search for key functions, classes, or variables related to the issue.
+- Read and understand relevant code snippets.
+- Identify the root cause of the problem.
+- Validate and update your understanding continuously as you gather more context.
+
+## 4. Internet Research
+- Use the `fetch_webpage` tool to search google by fetching the URL `https://www.google.com/search?q=your+search+query`.
+- After fetching, review the content returned by the fetch tool.
+- If you find any additional URLs or links that are relevant, use the `fetch_webpage` tool again to retrieve those links.
+- Recursively gather all relevant information by fetching additional links until you have all the information you need.
+
+## 5. Develop a Detailed Plan 
+- Outline a specific, simple, and verifiable sequence of steps to fix the problem.
+- Create a todo list in markdown format to track your progress.
+- Each time you complete a step, check it off using `[x]` syntax.
+- Each time you check off a step, display the updated todo list to the user.
+- Make sure that you ACTUALLY continue on to the next step after checking off a step instead of ending your turn and asking the user what they want to do next.
+
+## 6. Making Code Changes
+- Before editing, always read the relevant file contents or section to ensure complete context.
+- Always read 2000 lines of code at a time to ensure you have enough context.
+- If a patch is not applied correctly, attempt to reapply it.
+- Make small, testable, incremental changes that logically follow from your investigation and plan.
+
+## 7. Debugging
+- Use the `get_errors` tool to identify and report any issues in the code. This tool replaces the previously used `#problems` tool.
+- Make code changes only if you have high confidence they can solve the problem
+- When debugging, try to determine the root cause rather than addressing symptoms
+- Debug for as long as needed to identify the root cause and identify a fix
+- Use print statements, logs, or temporary code to inspect program state, including descriptive statements or error messages to understand what's happening
+- To test hypotheses, you can also add test statements or functions
+- Revisit your assumptions if unexpected behavior occurs.
+
+# How to create a Todo List
+Use the following format to create a todo list:
+```markdown
+- [ ] Step 1: Description of the first step
+- [ ] Step 2: Description of the second step
+- [ ] Step 3: Description of the third step
+```
+
+Do not ever use HTML tags or any other formatting for the todo list, as it will not be rendered correctly. Always use the markdown format shown above.
+
+# Communication Guidelines
+Always communicate clearly and concisely in a casual, friendly yet professional tone. 
+
+<examples>
+"Let me fetch the URL you provided to gather more information."
+"Ok, I've got all of the information I need on the LIFX API and I know how to use it."
+"Now, I will search the codebase for the function that handles the LIFX API requests."
+"I need to update several files here - stand by"
+"OK! Now let's run the tests to make sure everything is working correctly."
+"Whelp - I see we have some problems. Let's fix those up."
+</examples>

.github/copilot-instructions.md

@@ -0,0 +1,62 @@
+# Copilot Instructions for AI Coding Agents
+
+## Project Overview
+- **Purpose:** Real-time analytics dashboard for global AI & cloud computing strategy, targeting enterprise decision-makers.
+- **Architecture:** Modular, component-based Python app (Streamlit frontend, Pandas/NumPy for data, Plotly for visualization).
+- **Key Directories:**
+  - `src/app.py`: Main entry point (Streamlit app)
+  - `src/components/`: UI and logic modules (e.g., `metrics.py`, `decision_helper.py`)
+  - `src/data/`: Data ingestion and processing (e.g., `market_data.py`)
+  - `src/visualizations/`: Plotly-based charting modules
+  - `src/utils/`: Shared helpers
+  - `scripts/`: Utility scripts (e.g., diagram generation)
+  - `docs/`: Architecture, API, and developer docs
+
+## Essential Workflows
+- **Run Locally:**
+  ```bash
+  streamlit run src/app.py
+  ```
+- **Install Dependencies:**
+  ```bash
+  pip install -r requirements.txt
+  ```
+- **Generate Diagrams:**
+  ```bash
+  ./scripts/generate_diagrams.sh
+  ```
+  (Requires Graphviz)
+
+## Patterns & Conventions
+- **Component Structure:**
+  - Each `src/components/*.py` file encapsulates a dashboard feature (metrics, comparisons, etc.)
+  - Data modules in `src/data/` are decoupled from UI logic
+  - Visualizations are isolated in `src/visualizations/` and use Plotly
+- **No hardcoded data in UI/components;** always source from `src/data/` or external APIs
+- **All user-facing logic flows through `app.py`** (acts as orchestrator)
+- **Docs:**
+  - Architecture and workflow diagrams in `docs/diagrams/`
+  - Developer onboarding: `docs/DEVELOPER_ROADMAP_2025.md`
+
+## Integration & Extensibility
+- **Add new dashboard features:**
+  - Create a new module in `src/components/`
+  - Register it in `app.py` for Streamlit routing
+- **Add new data sources:**
+  - Implement in `src/data/`, expose clean API to components
+- **Update visualizations:**
+  - Extend or modify `src/visualizations/` modules
+
+## Project-Specific Notes
+- **Security & Compliance:**
+  - See `src/data/compliance_data.py` and `docs/security.md`
+- **Performance:**
+  - Data processing is optimized for real-time updates; avoid blocking UI
+- **Testing:**
+  - No explicit test suite found; follow modularity and separation of concerns for maintainability
+
+## Examples
+- To add a new performance metric: implement in `src/data/performance_data.py`, visualize in `src/visualizations/performance_plots.py`, and surface in `src/components/metrics.py`.
+
+---
+For more, see `README.md`, `docs/`, and code comments. When in doubt, follow the structure of existing modules.

.github/workflows/ci.yml

@@ -0,0 +1,32 @@
+name: CI
+
+on:
+  push:
+    branches: [ main ]
+  pull_request:
+    branches: [ main ]
+
+jobs:
+  build:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+      - name: Set up Python
+        uses: actions/setup-python@v5
+        with:
+          python-version: '3.12'
+      - name: Install dependencies
+        run: |
+          python -m pip install --upgrade pip
+          pip install -r requirements.txt
+      - name: Lint with flake8
+        run: |
+          pip install flake8
+          flake8 src/ --count --select=E9,F63,F7,F82 --show-source --statistics
+      - name: Check formatting with black
+        run: |
+          pip install black
+          black --check src/
+      - name: (Optional) Run tests
+        run: |
+          echo "No test suite found. Add tests/ and update this step."

CHANGELOG.md

@@ -0,0 +1,15 @@
+# Changelog
+
+All notable changes to this project will be documented in this file.
+
+The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/), and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
+
+## [Unreleased]
+- Initial changelog setup.
+- Updated `README.md` with new information or corrections.
+- Enhanced `src/app.py` for improved dashboard orchestration or bug fixes.
+- Refactored and updated `src/components/metrics.py` for metrics display logic.
+- Improved or fixed visualizations in `src/visualizations/plots.py`.
+- Added or updated documentation: `docs/security_quickstart.md`, `docs/user_guide.md`.
+- Added new tests in `tests/` directory.
+- Added `.github/`, `CODE_OF_CONDUCT.md` for project governance and contribution guidelines.

CODE_OF_CONDUCT.md

@@ -0,0 +1,43 @@
+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+
+We as members, contributors, and leaders pledge to make participation in our community a harassment-free experience for everyone, regardless of age, body size, visible or invisible disability, ethnicity, sex characteristics, gender identity and expression, level of experience, education, socio-economic status, nationality, personal appearance, race, religion, or sexual identity and orientation.
+
+We pledge to act and interact in ways that contribute to an open, welcoming, diverse, inclusive, and healthy community.
+
+## Our Standards
+
+Examples of behavior that contributes to a positive environment for our community include:
+- Demonstrating empathy and kindness toward other people
+- Being respectful of differing opinions, viewpoints, and experiences
+- Giving and gracefully accepting constructive feedback
+- Accepting responsibility and apologizing to those affected by our mistakes, and learning from the experience
+- Focusing on what is best not just for us as individuals, but for the overall community
+
+Examples of unacceptable behavior include:
+- The use of sexualized language or imagery, and sexual attention or advances of any kind
+- Trolling, insulting or derogatory comments, and personal or political attacks
+- Public or private harassment
+- Publishing others’ private information, such as a physical or email address, without their explicit permission
+- Other conduct which could reasonably be considered inappropriate in a professional setting
+
+## Enforcement Responsibilities
+
+Community leaders are responsible for clarifying and enforcing our standards of acceptable behavior and will take appropriate and fair corrective action in response to any behavior that they deem inappropriate, threatening, offensive, or harmful.
+
+## Scope
+
+This Code of Conduct applies within all community spaces, and also applies when an individual is officially representing the community in public spaces.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be reported to the community leaders responsible for enforcement at the project repository or via direct contact with the maintainer.
+
+All complaints will be reviewed and investigated promptly and fairly.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 2.1, available at https://www.contributor-covenant.org/version/2/1/code_of_conduct.html
+
+[homepage]: https://www.contributor-covenant.org

README.md

@@ -36,6 +36,15 @@ A comprehensive real-time analytics platform for monitoring and analyzing the gl
   - Learning resource center
   - Future trends forecasting
 
+- **User Customization & Roles**
+  - Executive, Manager, and Analyst views with tailored metrics and dashboards
+- **Interactive Filters & Drill-Downs**
+  - Region, provider, and time range filters for all major analytics
+- **Accessibility**
+  - Colorblind-friendly visualizations and ARIA-ready components
+- **AI Insights**
+  - Automated trend detection, anomaly alerts, and predictive analytics panel
+
 ## 🛠️ Technology Stack
 
 - **Frontend**: Streamlit
@@ -126,6 +135,8 @@ Note: The source files for these diagrams are available in DOT format under `doc
    ```bash
    streamlit run src/app.py
    ```
+   
+   The dashboard now supports user role selection, provider/region filters, and AI-powered insights for enterprise users.
 
 ## 📈 Performance & Scalability
 

docs/security_quickstart.md

@@ -0,0 +1,27 @@
+# Security & Compliance Quickstart
+
+This guide summarizes key security and compliance features for enterprise users.
+
+## Security Features
+- Data encryption in transit and at rest
+- Regular security updates
+- Audit logging of key actions
+- Role-based dashboard views
+
+## Compliance
+- Compliance tracking for GDPR, HIPAA, FedRAMP, PCI, SOX, ISO 27001
+- Data residency visualization and controls
+- Certification timeline management
+
+## Data Privacy
+- User-facing privacy policy link in the dashboard
+- Data export request feature (in sidebar)
+
+## Best Practices
+- Review compliance requirements for your region and industry
+- Use the dashboard’s filters to focus on relevant compliance data
+- Contact your security team for additional integration or audit needs
+
+## More Information
+- See [docs/security.md](./security.md) for full details
+- For questions, contact the project maintainer