refactor: genericize enterprise content for public release

- Rename 07_SOLARWINDS_ORION.md → 07_MONITORING_API_INTEGRATION.md
- Rename 13_ENTERPRISE_SAMPLE_SCHEMAS.md → 13_SAMPLE_DATABASE_SCHEMAS.md
- Replace SolarWinds/Orion/DPA/MSSQL references with generic alternatives
- Remove personal references (Travis J Neuman)
- Update CLAUDE.md to remove personal learner context

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

Author: travisjneuman

00_COMPUTER_LITERACY_PRIMER.md

@@ -38,8 +38,8 @@ my_computer/
 ```
 
 The "path" is the address of a file or folder. It tells the computer exactly where to find something:
-- Windows: `C:\Users\Travis\Projects\learn_python\hello.py`
-- Mac/Linux: `/Users/Travis/Projects/learn_python/hello.py`
+- Windows: `C:\Users\YourName\Projects\learn_python\hello.py`
+- Mac/Linux: `/Users/YourName/Projects/learn_python/hello.py`
 
 ## What is a text editor?
 
@@ -57,7 +57,7 @@ The terminal (also called "command line" or "command prompt") is a text-based wa
 
 It looks like this:
 ```
-C:\Users\Travis> _
+C:\Users\YourName> _
 ```
 
 The blinking cursor means the terminal is waiting for you to type a command.

01_ROADMAP.md

@@ -1,30 +1,30 @@
-# 01 - Roadmap: Zero Experience -> Python SME (Enterprise Automation and Dashboards)
+# 01 - Roadmap: Zero Experience -> Python SME (Automation and Dashboards)
 Home: [README](./README.md)
 
 ## Who this is for
 - You have zero coding, scripting, or programming experience.
-- You need practical outcomes in an enterprise operations environment.
+- You need practical outcomes in a real operations environment.
 - You learn best by doing real work, not passive studying.
 
 ## What you will build
 - Reliable Python automations for files, Excel, SQL, and monitoring data.
-- Repeatable ETL workflows using MSSQL as a reporting backbone.
-- SolarWinds Orion and DPA data ingestion jobs.
+- Repeatable ETL workflows using SQL databases as a reporting backbone.
+- Monitoring API data ingestion jobs.
 - Browser-based dashboards for non-technical stakeholders.
 
 ## Prerequisites
-- One supported platform: Windows, macOS, Linux, Android, or iOS (desktop strongly recommended for full enterprise path).
+- One supported platform: Windows, macOS, Linux, Android, or iOS (desktop strongly recommended for full path).
 - Permission to install Python and VS Code.
-- Access path for MSSQL credentials (non-SSO SQL auth is supported in this plan).
-- Read-only API access to Orion and DPA to start.
+- Database credentials for your SQL database (SQLite for learning, PostgreSQL for production).
+- Read-only API access to your monitoring platform to start.
 
 ## Program overview (8-10 hrs/week default)
 - Phase 0 (Week 1): environment setup and first script.
 - Phase 1 (Weeks 2-6): Python foundations.
 - Phase 2 (Weeks 7-10): quality tooling and team-ready workflow.
 - Phase 3 (Weeks 11-16): file and Excel automation.
 - Phase 4 (Weeks 17-22): SQL-first ETL pipelines.
-- Phase 5 (Weeks 23-28): Orion and DPA integration.
+- Phase 5 (Weeks 23-28): monitoring API integration.
 - Phase 6 (Weeks 29-38): dashboard delivery for browser users.
 - Phase 7 (Weeks 39+): release process, governance, and handoff maturity.
 - Phase 8+ (Advanced): full-stack expert path and infinite mastery loop.
@@ -105,9 +105,9 @@ Done means done:
 Fail/recover guidance:
 - freeze schema changes until test dataset passes end-to-end.
 
-### Phase 5 - Orion and DPA integration (Weeks 23-28)
+### Phase 5 - Monitoring API integration (Weeks 23-28)
 Weekly outcomes:
-- read-only ingestion from Orion and DPA into cache tables.
+- read-only ingestion from monitoring APIs into cache tables.
 
 Minimum deliverables:
 - one daily ingestion job from each source.
@@ -148,7 +148,7 @@ Fail/recover guidance:
 - Gate A: setup + first script + first passing test.
 - Gate B: Capstone A supports safe reruns and rejects.
 - Gate C: SQL ETL is idempotent and logged.
-- Gate D: Orion/DPA ingestion proof into MSSQL cache.
+- Gate D: Monitoring API ingestion proof into database cache.
 - Gate E: browser dashboard available to stakeholders.
 
 ## Project ladder mapping (practice by skill level)
@@ -180,8 +180,8 @@ Fail/recover guidance:
 - Teach-back: explain one concept weekly to another person or a written journal.
 
 ## Expected output
-- A complete progression from beginner to enterprise-capable Python practitioner.
-- A portfolio of capstones tied to your real data systems.
+- A complete progression from beginner to production-capable Python practitioner.
+- A portfolio of capstones tied to real data systems.
 - A clear upgrade path to full-stack expert mastery:
   - [21_FULL_STACK_MASTERY_PATH.md](./curriculum/21_FULL_STACK_MASTERY_PATH.md)
   - [22_SPECIALIZATION_TRACKS.md](./curriculum/22_SPECIALIZATION_TRACKS.md)

02_GLOSSARY.md

@@ -1,4 +1,4 @@
-# 02 - Glossary (Plain English + Enterprise Context)
+# 02 - Glossary (Plain English + Practical Context)
 Home: [README](./README.md)
 
 Use this file anytime you see unknown terms.
@@ -13,8 +13,8 @@ Use this file anytime you see unknown terms.
 
 ### Script
 - Plain English: A small program designed to automate one task.
-- Why it matters: Most enterprise automation starts as scripts.
-- Example: Daily job that exports critical SolarWinds alerts.
+- Why it matters: Most automation starts as scripts.
+- Example: Daily job that exports critical monitoring alerts.
 - Common beginner mistake: Putting too many unrelated tasks into one script.
 
 ### Function
@@ -86,7 +86,7 @@ Use this file anytime you see unknown terms.
 ### ETL
 - Plain English: Extract, transform, load.
 - Why it matters: Core pattern for reporting pipelines.
-- Example: Excel -> clean rows -> MSSQL table.
+- Example: Excel -> clean rows -> SQL database table.
 - Common beginner mistake: Skipping schema validation before load.
 
 ### Staging table
@@ -102,35 +102,29 @@ Use this file anytime you see unknown terms.
 - Common beginner mistake: Mixing raw and curated records.
 
 ### SQL auth vs SSO
-- Plain English: SQL auth uses DB username/password; SSO uses Windows/M365 identity.
-- Why it matters: Your current MSSQL access may use SQL auth, not SSO.
+- Plain English: SQL auth uses DB username/password; SSO uses identity provider (OAuth, SAML).
+- Why it matters: Your database access may use SQL auth, not SSO.
 - Example: Service account credentials for ETL jobs.
 - Common beginner mistake: Hardcoding credentials in scripts.
 
-## SolarWinds and monitoring terms
+## Monitoring and API terms
 
-### SWIS
-- Plain English: Orion information service API layer.
-- Why it matters: Main way to query Orion entities.
-- Example: Query node or alert metadata.
-- Common beginner mistake: Treating SWIS like raw SQL access.
+### REST API
+- Plain English: Standard way for programs to exchange data over HTTP.
+- Why it matters: Main way to query monitoring platforms and external services.
+- Example: Query node or alert metadata from a monitoring API.
+- Common beginner mistake: Treating API responses like raw SQL access.
 
-### SWQL
-- Plain English: Query language used with SolarWinds Orion objects.
-- Why it matters: Required for many useful Orion queries.
-- Example: Query active alerts by severity.
-- Common beginner mistake: Expecting all T-SQL features in SWQL.
-
-### DPA API token
-- Plain English: Credential used to call DPA REST API endpoints.
-- Why it matters: Enables scripted data pulls from DPA.
+### API token
+- Plain English: Credential used to call REST API endpoints.
+- Why it matters: Enables scripted data pulls from monitoring platforms.
 - Example: Fetch instance health metrics daily.
 - Common beginner mistake: Storing token in source code.
 
 ### Caching layer
 - Plain English: Intermediate database layer to reduce repeated API calls.
 - Why it matters: Improves dashboard speed and source-system stability.
-- Example: Load Orion and DPA snapshots into MSSQL cache tables.
+- Example: Load API snapshots into database cache tables.
 - Common beginner mistake: Querying live APIs directly for every dashboard request.
 
 ### Service account
@@ -142,8 +136,8 @@ Use this file anytime you see unknown terms.
 ## Primary Sources
 - [Python glossary and tutorial](https://docs.python.org/3/tutorial/)
 - [PyPA guide](https://packaging.python.org/en/latest/tutorials/installing-packages/)
-- [SolarWinds OrionSDK](https://github.com/solarwinds/OrionSDK)
-- [SolarWinds DPA docs](https://documentation.solarwinds.com/en/success_center/dpa/content/dpa_documentation.htm)
+- [requests library](https://docs.python-requests.org/en/latest/)
+- [SQLAlchemy tutorial](https://docs.sqlalchemy.org/en/20/tutorial/index.html)
 
 ## Optional Resources
 - [Python Tutor](https://pythontutor.com/)

03_SETUP_ALL_PLATFORMS.md

@@ -16,7 +16,7 @@ Home: [README](./README.md)
 - One device with internet access.
 - Permission to install apps on your device.
 - 45 to 90 minutes for first-time setup.
-- For enterprise labs later in this plan: SQL-auth credentials to MSSQL (separate from Windows/M365 SSO is fine).
+- For database labs later in this plan: database credentials (SQLite works locally with no setup; PostgreSQL for production practice).
 
 ## Step-by-step lab pack
 
@@ -27,7 +27,7 @@ Use one of these paths:
 
 Important:
 - You can learn basics on mobile.
-- For advanced enterprise work (drivers, ETL jobs, dashboards, CI), desktop is required.
+- For advanced work (drivers, ETL jobs, dashboards, CI), desktop is required.
 
 ### Step 1 - Install Python
 

06_SQL.md

@@ -1,12 +1,12 @@
-# 06 - SQL Integration (MSSQL-First ETL for Reporting and Dashboards)
+# 06 - SQL Integration (SQL & ETL Pipelines for Reporting and Dashboards)
 Home: [README](./README.md)
 
 ## Who this is for
 - Learners moving from file automation to data pipelines.
-- Teams with MSSQL as a reporting backbone.
+- Teams with SQL databases as a reporting backbone.
 
 ## What you will build
-- A Python ETL pipeline that ingests validated records into MSSQL.
+- A Python ETL pipeline that ingests validated records into a SQL database.
 - Staging and reporting tables with idempotent loads.
 - A daily summary query output for dashboard use.
 
@@ -35,8 +35,8 @@ Minimum metadata fields:
 - `idempotency_key`
 
 ### Lab 3 - Python connection strategy
-Preferred start: `pyodbc`.
-Optional scaling path: SQLAlchemy.
+Preferred start: `sqlite3` (built-in, no driver needed).
+Optional scaling path: SQLAlchemy (supports SQLite, PostgreSQL, and more).
 
 Connection requirements:
 - no hardcoded secrets,
@@ -58,15 +58,15 @@ Generate query output by:
 Export summary to `output/daily_summary.csv` for dashboard consumption.
 
 ### Lab 6 - Custom reporting backend integration
-For your contractor-built MSSQL reporting DB:
+For an existing reporting database:
 - identify existing table contracts,
 - map your ETL output to existing schema,
 - avoid direct writes to unmanaged tables until schema ownership is clear.
 
-### Lab 7 - Optional Oracle extension
-If Oracle sources are added later:
+### Lab 7 - Optional PostgreSQL extension
+If you scale beyond SQLite:
 - ingest to staging only first,
-- normalize data types to MSSQL-compatible forms,
+- normalize data types to PostgreSQL-compatible forms,
 - preserve source system metadata.
 
 ## Expected output
@@ -90,7 +90,7 @@ If Oracle sources are added later:
   - add indexes on date, severity, idempotency key.
 
 ## Mastery check
-You are ready for SolarWinds ingestion when you can:
+You are ready for API integration when you can:
 - explain your table contract,
 - rerun ETL safely,
 - recover from transient DB failures,
@@ -103,18 +103,17 @@ You are ready for SolarWinds ingestion when you can:
 - Teach-back: present ETL data flow and failure strategy.
 
 ## Primary Sources
-- [SQL Server Python drivers overview](https://learn.microsoft.com/en-gb/sql/connect/python/python-driver-for-sql-server)
-- [MSSQL Python quickstart](https://learn.microsoft.com/en-us/sql/connect/python/mssql-python/python-sql-driver-mssql-python-quickstart?view=sql-server-ver17)
-- [ODBC connection strings](https://learn.microsoft.com/en-us/sql/connect/odbc/dsn-connection-string-attribute?view=sql-server-ver17)
+- [SQLite documentation](https://www.sqlite.org/docs.html)
+- [PostgreSQL documentation](https://www.postgresql.org/docs/)
 - [SQLAlchemy tutorial](https://docs.sqlalchemy.org/en/20/tutorial/index.html)
 
 ## Optional Resources
 - [pyodbc project](https://github.com/mkleehammer/pyodbc)
 - [python-oracledb docs](https://python-oracledb.readthedocs.io/en/latest/user_guide/connection_handling.html)
 
-## Enterprise sample schemas
+## Sample database schemas
 - Full schema pack for staging/reporting/cache/marts:
-  - [13_ENTERPRISE_SAMPLE_SCHEMAS.md](./13_ENTERPRISE_SAMPLE_SCHEMAS.md)
+  - [13_SAMPLE_DATABASE_SCHEMAS.md](./13_SAMPLE_DATABASE_SCHEMAS.md)
 
 ---
 

08_DASHBOARDS.md

@@ -6,11 +6,11 @@ Home: [README](./README.md)
 - Teams that need browser-only access to reporting and health data.
 
 ## What you will build
-- A browser-consumable dashboard backed by MSSQL cache tables.
+- A browser-consumable dashboard backed by database cache tables.
 - Filters, exports, and freshness indicators usable by operations teams.
 
 ## Prerequisites
-- Cache tables and summaries from [07_SOLARWINDS_ORION.md](./07_SOLARWINDS_ORION.md).
+- Cache tables and summaries from [07_MONITORING_API_INTEGRATION.md](./07_MONITORING_API_INTEGRATION.md).
 - Clean SQL summary outputs from [06_SQL.md](./06_SQL.md).
 
 ## Step-by-step lab pack
@@ -31,7 +31,7 @@ Examples:
   - export button.
 
 ### Step 3 - Add cache and data freshness
-- Query MSSQL cache first, not live APIs per request.
+- Query database cache first, not live APIs per request.
 - Display `last_refresh_utc` on every page.
 - Warn user when data is stale.
 
@@ -50,7 +50,7 @@ Reference: [FastAPI tutorial](https://fastapi.tiangolo.com/tutorial/).
 ### Step 6 - Deployment path options
 1. Local-only developer run.
 2. Internal server deployment for team use.
-3. Future option: host with existing MSSQL/ASP.NET server ecosystem if architecture and security review approves.
+3. Future option: host on cloud infrastructure if architecture and security review approves.
 
 ## Expected output
 - A dashboard accessible in browser with reliable and understandable data.

10_CAPSTONE_PROJECTS.md

@@ -46,7 +46,7 @@ Stretch goals:
 - config-driven schemas,
 - richer Excel formatting.
 
-### Capstone B - ETL to MSSQL
+### Capstone B - ETL to SQL Database
 Business goal:
 - Move validated report data into durable SQL pipelines.
 
@@ -77,12 +77,12 @@ Stretch goals:
 - SQLAlchemy migration path,
 - performance tuning and indexing.
 
-### Capstone C - Orion + DPA Daily Ops Pipeline
+### Capstone C - Monitoring API Daily Ops Pipeline
 Business goal:
 - Ingest monitoring health data into reporting cache.
 
 Inputs/outputs:
-- Orion and DPA API reads.
+- Monitoring API reads.
 - Outputs: cache tables + daily ops reports (xlsx/html).
 
 Implementation milestones:
@@ -113,7 +113,7 @@ Business goal:
 - Deliver usable operational visibility to non-technical users.
 
 Inputs/outputs:
-- MSSQL summary/cache data.
+- Database summary/cache data.
 - Output: browser UI with filters and exports.
 
 Implementation milestones:
@@ -172,8 +172,8 @@ You are SME-ready when you can:
 - [Streamlit docs](https://docs.streamlit.io/get-started)
 - [Dash docs](https://dash.plotly.com/tutorial)
 - [FastAPI tutorial](https://fastapi.tiangolo.com/tutorial/)
-- [OrionSDK](https://github.com/solarwinds/OrionSDK)
-- [DPA API docs](https://documentation.solarwinds.com/en/success_center/dpa/content/dpa-use-the-api.htm)
+- [requests library](https://docs.python-requests.org/en/latest/)
+- [SQLAlchemy tutorial](https://docs.sqlalchemy.org/en/20/tutorial/index.html)
 
 ## Optional Resources
 - [Real Python](https://realpython.com/tutorials/python/)

11_CHECKLISTS.md

@@ -54,7 +54,7 @@ Use before architecture reviews with experienced engineers:
 - [ ] Can explain your data flow in under 2 minutes.
 - [ ] Can justify staging vs reporting schema design.
 - [ ] Can explain idempotency strategy.
-- [ ] Can explain Orion/DPA cache strategy.
+- [ ] Can explain API data cache strategy.
 - [ ] Can explain security posture for credentials and access.
 - [ ] Can explain dashboard fallback behavior during outages.
 

12_SCREENSHOT_CHECKPOINTS.md

@@ -66,10 +66,10 @@ Reflection prompts:
 - How did you verify idempotency?
 - What index or query improvement did you add?
 
-### Phase 5 - Orion and DPA integration
+### Phase 5 - Monitoring API integration
 Capture screenshots of:
-1. Orion ingestion result snapshot.
-2. DPA ingestion result snapshot.
+1. Primary API ingestion result snapshot.
+2. Secondary API ingestion result snapshot.
 3. Cache table freshness timestamps.
 
 Reflection prompts:

14_NAVIGATION_AND_STUDY_WORKFLOW.md

@@ -11,12 +11,12 @@ Use this file to keep study flow clean and avoid navigation friction.
 5. [09_QUALITY_TOOLING.md](./09_QUALITY_TOOLING.md)
 6. [05_AUTOMATION_FILES_EXCEL.md](./05_AUTOMATION_FILES_EXCEL.md)
 7. [06_SQL.md](./06_SQL.md)
-8. [07_SOLARWINDS_ORION.md](./07_SOLARWINDS_ORION.md)
+8. [07_MONITORING_API_INTEGRATION.md](./07_MONITORING_API_INTEGRATION.md)
 9. [08_DASHBOARDS.md](./08_DASHBOARDS.md)
 10. [10_CAPSTONE_PROJECTS.md](./10_CAPSTONE_PROJECTS.md)
 11. [11_CHECKLISTS.md](./11_CHECKLISTS.md)
 12. [12_SCREENSHOT_CHECKPOINTS.md](./12_SCREENSHOT_CHECKPOINTS.md)
-13. [13_ENTERPRISE_SAMPLE_SCHEMAS.md](./13_ENTERPRISE_SAMPLE_SCHEMAS.md)
+13. [13_SAMPLE_DATABASE_SCHEMAS.md](./13_SAMPLE_DATABASE_SCHEMAS.md)
 14. [14_NAVIGATION_AND_STUDY_WORKFLOW.md](./14_NAVIGATION_AND_STUDY_WORKFLOW.md)
 
 ## Elite extension sequence (after baseline completion)