-
Notifications
You must be signed in to change notification settings - Fork 0
Aurora refactoring #6
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Changes from all commits
Commits
Show all changes
9 commits
Select commit
Hold shift + click to select a range
4cd7222
Delete QUICK_ACTION_PLAN.md
Tushar-R-Tyagi 37088fd
Refactor README.md section headers and features list
Tushar-R-Tyagi f546932
Delete CODE_REVIEW.md
Tushar-R-Tyagi e1fae84
Update README with Siemens accelerator note
Tushar-R-Tyagi e76463b
Delete AI_EXPERIMENT.md
Tushar-R-Tyagi 519b63c
Merge conflict resolved
8ddd109
Rename project from AURA to Automated Resource Analytics
Tushar-R-Tyagi 6435ab3
Update roadmap direction for enterprise level focus
Tushar-R-Tyagi 785d035
Merge branch 'main' into aurora-refactoring
Tushar-R-Tyagi File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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 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
| Original file line number | Diff line number | Diff line change | ||
|---|---|---|---|---|
| @@ -1,81 +1,73 @@ | ||||
| # 🏢 AURA (Automated Resource Analysis) - AI-Powered Resource Planning & Workforce Management | ||||
| # AURA: Automated Resource Analytics | ||||
|
|
||||
| **AURA** is an intelligent workforce resource planning platform powered by **AURORA**, an advanced AI scenario analysis engine. | ||||
| AURA is a workforce planning and decision-support platform. | ||||
|
|
||||
| ## What is AURA? | ||||
| It combines team data, allocation data, budget constraints, and AI-assisted scenario analysis to answer practical planning questions such as: | ||||
|
|
||||
| **AURA** (Executive Dashboard) provides comprehensive resource planning across: | ||||
| - Team management & organizational structure | ||||
| - Project allocation & capacity tracking | ||||
| - Budget forecasting & financial planning | ||||
| - **AURORA** AI-driven scenario analysis | ||||
| - Where do we have staffing risk right now? | ||||
| - What is the impact of delaying a hire? | ||||
| - Which hiring sequence reduces risk most under budget limits? | ||||
| - How likely is a knowledge transfer to succeed before planned exits? | ||||
|
|
||||
| ## What is AURORA? | ||||
| ## Product Positioning | ||||
|
|
||||
| **AURORA** is the AI-powered decision engine within AURA that answers critical "what-if" workforce questions in seconds: | ||||
| This project is intentionally positioned as a decision layer, not only as a dashboard. | ||||
|
|
||||
| - What if we delay hiring for this component? | ||||
| - What if we add a new team member? | ||||
| - Where should we prioritize new hires? | ||||
| - What's our knowledge transfer risk? | ||||
| - How will decisions affect budget & timeline? | ||||
| - AURA is the platform (data + workflows + reporting) | ||||
| - AURORA is the AI reasoning engine inside AURA | ||||
|
|
||||
| **AURORA** combines: | ||||
| - Real-time LLM reasoning (Groq's Llama 3.3 70B) | ||||
| - Company-specific workforce data analysis | ||||
| - Multi-dimensional impact assessment (Timeline + Budget + Risk) | ||||
| - Transparent confidence scoring | ||||
| Target direction: evolve from internal workforce planning to ATS-adjacent hiring intelligence. | ||||
|
|
||||
| ## Quick Start | ||||
| ## Why This Matters | ||||
|
|
||||
| ### Prerequisites | ||||
| - Python 3.12+ | ||||
| - Groq API key (free at https://console.groq.com) | ||||
| Most organizations make hiring and staffing decisions across separate systems (recruiting, delivery, finance). | ||||
| That creates blind spots. | ||||
|
|
||||
| ### Setup | ||||
| AURA focuses on connecting those signals so decisions are: | ||||
|
|
||||
| ```bash | ||||
| python -m venv .venv | ||||
| source .venv/bin/activate # On Windows: .venv\Scripts\activate | ||||
| pip install -r requirements.txt | ||||
| - faster | ||||
| - explainable | ||||
| - measurable | ||||
| - constrained by real budget and capacity limits | ||||
|
|
||||
| # Create .env file | ||||
| echo "GROQ_API_KEY=gsk_YOUR_KEY_HERE" > .env | ||||
| ## Current Scope | ||||
|
|
||||
| # Run AURA | ||||
| streamlit run app.py | ||||
| ``` | ||||
| ### Functional Areas | ||||
|
|
||||
| AURA will open at `http://localhost:8501` | ||||
| 1. Executive Dashboard | ||||
| 2. Master Data Management | ||||
| 3. Project Allocation Management | ||||
| 4. Financial Management | ||||
| 5. AI Scenario Analysis | ||||
|
|
||||
| ## Documentation | ||||
| ### AI Scenario Types | ||||
|
|
||||
| - **[AURA_PROJECT_ANALYSIS.md](AURA_PROJECT_ANALYSIS.md)** - Complete technical analysis | ||||
| - **[AURA_ARCHITECTURE_DIAGRAMS.md](AURA_ARCHITECTURE_DIAGRAMS.md)** - System architecture & diagrams | ||||
| 1. Hiring delay impact | ||||
| 2. Employee addition impact | ||||
| 3. Component risk analysis | ||||
| 4. Hiring priority recommendation | ||||
| 5. Knowledge transfer success prediction | ||||
| 6. Custom free-form strategic questions | ||||
|
|
||||
| ## Architecture | ||||
| ## Architecture Overview | ||||
|
|
||||
| ### AURA Platform (5 Pages) | ||||
| The codebase follows a layered structure: | ||||
|
|
||||
| 1. **🏠 Executive Dashboard** - Strategic overview & KPIs | ||||
| 2. **🛠️ Stammdaten Management** - Team, components, budgets | ||||
| 3. **📅 Projekt Allocation** - Capacity & project assignments | ||||
| 4. **💰 Finanzielle Verwaltung** - Budget forecasting | ||||
| 5. **🤖 AURORA Scenarios** - AI-powered what-if analysis | ||||
| - Presentation Layer: Streamlit pages and dashboard UX | ||||
| - Logic Layer: business services and scenario reasoning | ||||
| - Data Access Layer: repository-style persistence APIs | ||||
| - Persistence Layer: SQLite schema and state tables | ||||
|
|
||||
| ### AURORA Engine (AI Core) | ||||
| Core directories: | ||||
|
|
||||
| ``` | ||||
| User Scenario → Context Building → Prompt Construction → | ||||
| Groq LLM (5-30s) → Response Parsing → Results & Visualizations | ||||
| ``` | ||||
| - app.py | ||||
| - pages/ | ||||
| - logic/ | ||||
| - database/ | ||||
| - ui/ | ||||
| - tests/ | ||||
|
|
||||
| **Scenario Types:** | ||||
| - Hiring Delay Impact | ||||
| - Employee Addition Analysis | ||||
| - Component Risk Assessment | ||||
| - Hiring Priority Optimization | ||||
| - Knowledge Transfer Prediction | ||||
| ## Engineering Status (April 2026) | ||||
|
|
||||
| ## Key Features | ||||
|
|
||||
|
|
@@ -89,21 +81,21 @@ Groq LLM (5-30s) → Response Parsing → Results & Visualizations | |||
|
|
||||
| ## Business Value | ||||
|
|
||||
| - **Speed:** 5-30 seconds vs 2-week manual analysis | ||||
| - **Accuracy:** AI considers 20+ variables simultaneously | ||||
| - **ROI:** Saves ~€30K/month in decision-making time | ||||
| - **Confidence:** Transparent scoring builds trust | ||||
| - AI output robustness and strict schema enforcement | ||||
| - Broader test coverage (integration + scenario-level tests) | ||||
| - API-first integration layer for external systems | ||||
| - Stronger observability and auditability | ||||
| - Multi-user and role-based access patterns | ||||
|
|
||||
| ## Tech Stack | ||||
| ## ATS-Aligned Roadmap Direction | ||||
|
|
||||
| | Layer | Technology | | ||||
| |-------|-----------| | ||||
| | **Frontend** | Streamlit 1.28.1, Plotly 5.17.0 | | ||||
| | **Backend** | Python 3.12, SQLite | | ||||
| | **AI Engine** | Groq API, Llama 3.3 70B (AURORA) | | ||||
| | **Deployment** | Local/Cloud | | ||||
| To take the project to enterprise level, the next milestones are: | ||||
|
|
||||
| ## Project Structure | ||||
| 1. Documentation and narrative consistency (single source of truth) | ||||
| 2. ATS-native domain model extensions (jobs, candidates, stages, interviews, offers) | ||||
| 3. AI hardening (validation, fallbacks, evaluation harness) | ||||
| 4. API contracts for integration-ready decision services | ||||
| 5. Decision quality metrics (time-to-fill, risk reduction, load balancing) | ||||
|
|
||||
| ``` | ||||
| ressourcenplanner/ | ||||
|
|
@@ -133,39 +125,43 @@ ressourcenplanner/ | |||
| └── requirements.txt # Python dependencies | ||||
| ``` | ||||
|
|
||||
| ## Security | ||||
| ### Prerequisites | ||||
|
|
||||
|
||||
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The PR title (“Aurora refactoring”) doesn’t match the actual change set here (documentation rewrite + removal of old docs). Consider updating the PR title/description to reflect the doc-only scope, or add the intended refactoring changes if they’re missing.