How long does the integration take?

Change one base URL in an OpenAI-compatible client, or install the Python or TypeScript SDK; the quickstart routes a first request in a few minutes.

Will this lock us into another vendor?

No. The router is Apache-2.0 open source, your provider keys stay yours, and the API is OpenAI-compatible, so leaving is a change of base URL.

What happens when a provider fails?

The router falls back to the next model your policy allows and records the fallback in the trace, so an outage costs a retry, not an incident.

hcip-infrastructure-setup - Prompt

Name: hcip-infrastructure-setup
Author: HeadySystems

Prompt file imported from HeadySystems/Heady-Testing (.windsurf/workflows/hcip-infrastructure-setup.md). Copyright stays with the author.

Heady Complete Infrastructure Pipeline (HCIP)

This workflow systematically sets up the entire Heady infrastructure:

Replaces internal.headyio.com with service domains
Configures clean-build CI/CD with error alerting
Provisions all devices with extensions
Sets up observability and alerting

Prerequisites

PowerShell 7+ (Windows) or PowerShell Core (macOS/Linux)
Admin/sudo access for hosts file modification
Node.js 20+ and Python 3.12+ for builds

Quick Start

# Run complete setup
.\scripts\hc-infrastructure-setup.ps1 -Mode full-setup

# Or step by step
.\scripts\hc-infrastructure-setup.ps1 -Mode inventory    # Find internal.headyio.com refs
.\scripts\hc-infrastructure-setup.ps1 -Mode migrate     # Replace with domains
.\scripts\hc-infrastructure-setup.ps1 -Mode provision # Install everything
.\scripts\hc-infrastructure-setup.ps1 -Mode clean-build # Build from scratch

Mode Details

1. Inventory Mode

Scans entire codebase for localhost/internal.headyio.com references and creates a migration plan.

.\scripts\hc-infrastructure-setup.ps1 -Mode inventory

Output:

CSV file with all internal.headyio.com references
Suggested domain replacements
Service-to-port mapping

2. Migrate Mode

Replaces localhost references with proper service domains and updates hosts file.

.\scripts\hc-infrastructure-setup.ps1 -Mode migrate
# Or skip confirmation
.\scripts\hc-infrastructure-setup.ps1 -Mode migrate -Force

Changes:

Replaces localhost:3300 → manager.heady.local
Replaces localhost:5000 → worker.heady.local
Replaces localhost:3000 → dashboard.heady.local
Updates /etc/hosts or C:\Windows\System32\drivers\etc\hosts
Backs up original hosts file

DNS Entries Created:

internal.headyio.com manager.heady.local
internal.headyio.com worker.heady.local
internal.headyio.com dashboard.heady.local
internal.headyio.com www.heady.local
internal.headyio.com api.heady.local
internal.headyio.com cache.heady.local
internal.headyio.com db.heady.local
internal.headyio.com metrics.heady.local
internal.headyio.com grafana.heady.local
internal.headyio.com imagination.heady.local
internal.headyio.com traces.heady.local
internal.headyio.com alerts.heady.local

3. Provision Mode

Installs all required applications, extensions, and configurations.

.\scripts\hc-infrastructure-setup.ps1 -Mode provision

Installs:

Browsers: Chrome, Firefox, Edge (with extensions)
Editors: VS Code, JetBrains toolbox (with extensions)
Languages: Node.js 20.18.1, Python 3.12.7
Tools: Docker, Git, Postman, 1Password, Slack, Discord
Heady-specific: Local extensions from distribution/

VS Code Extensions:

TypeScript, Python, ESLint, Prettier support
Docker, Kubernetes, YAML tools
GitLens, GitHub Copilot
Heady Dev Companion (local)

Browser Extensions:

React/Redux DevTools
Heady Companion (local build)
Wappalyzer (technology profiler)
uBlock Origin (ad/tracker blocker)

4. Clean-Build Mode

Performs a full clean build with error alerting (no auto-rebuild).

.\scripts\hc-infrastructure-setup.ps1 -Mode clean-build

Build Steps:

Clean environment (remove node_modules, dist, cache)
Install dependencies (npm ci)
Lint code
Run tests
Build application
Verify artifacts

Error Handling:

❌ NO AUTO-REBUILD - If build fails, alerts are sent
Errors are classified: network, permission, code, resource
Desktop notification + webhook alert (if configured)
Human must fix issue and manually retry

Configure Alerts:

$env:HEADY_ALERT_WEBHOOK = "https://hooks.slack.com/services/YOUR/WEBHOOK/URL"
.\scripts\hc-infrastructure-setup.ps1 -Mode clean-build

5. Full-Setup Mode

Runs all modes in sequence for complete setup.

.\scripts\hc-infrastructure-setup.ps1 -Mode full-setup

Timeline:

Inventory: ~30 seconds
Migrate: ~10 seconds
Provision: 5-15 minutes (downloads)
Clean-build: 3-10 minutes

Service Domain Reference

Service	Old URL	New Domain	Port
Heady Manager	internal.headyio.com:3300	manager.heady.local	3300
Python Worker	localhost:5000	worker.heady.local	5000
Web Dashboard	localhost:3000	dashboard.heady.local	3000
Public Site	localhost:8080	www.heady.local	8080
API Gateway	localhost:8081	api.heady.local	8081
Redis Cache	localhost:6379	cache.heady.local	6379
PostgreSQL	localhost:5432	db.heady.local	5432
Metrics	localhost:9090	metrics.heady.local	9090
Grafana	localhost:3001	grafana.heady.local	3001
Imagination	localhost:3400	imagination.heady.local	3400

CI/CD Integration

GitHub Actions Workflow

The .github/workflows/clean-build.yml runs on every push:

on:
  push:
    branches: [main, develop]
  pull_request:
    branches: [main]

Jobs:

Pre-flight: Checks for internal.headyio.com references
Build Manager: Clean Node.js build
Build Frontend: React app build
Build Worker: Python + Docker
Integration Tests: Full stack testing
Security Scan: Trivy vulnerability check
Deploy Staging: Auto-deploy on develop
Deploy Production: Manual approval on main

Key Features:

Full clean build every time (no incremental artifacts)
Pinned dependencies (lockfiles committed)
Deterministic builds
Error classification + retry for transient issues
Slack notifications for failures/deployments

Local Clean Build

For development, use the script:

# Before committing
.\scripts\hc-infrastructure-setup.ps1 -Mode clean-build

# This ensures what you push matches CI

Device Management

Cross-Platform Setup

Windows (Intune/Autopilot):

# Initial enrollment
& $env:SystemRoot\System32\WindowsPowerShell\v1.0\powershell.exe -Command "
    Install-Script -Name Get-WindowsAutoPilotInfo -Force
    Get-WindowsAutoPilotInfo -Online
"

macOS (MDM):

# Apple Business Manager enrollment
# Device appears in MDM console automatically
# Heady profile pushed over-the-air

Linux (Ansible):

# Run device provisioning playbook
ansible-playbook -i inventory/internal.headyio.com device-provision.yml

Required Applications (All Devices)

Security:

1Password (password manager)
VPN client (Tailscale/WireGuard)
2FA authenticator

Communication:

Signal (secure messaging)
Slack (team chat)
Discord (community)

Productivity:

Obsidian (knowledge base)
Figma (design)
Notion (docs)

Development Workstation (Additional)

Languages & Runtimes:

Node.js 20.18.1
Python 3.12.7
Docker Desktop
Git

Browsers (all with dev profile):

Chrome + React/Vue DevTools + Heady Companion
Firefox + Heady Assistant
Edge (backup)

Editors:

VS Code + 15+ extensions
JetBrains toolbox (IntelliJ, PyCharm, WebStorm)

Monitoring & Alerting

What Gets Monitored

Services:

Heady Manager (health, response time, error rate)
Python Worker (queue depth, processing time)
PostgreSQL (connections, slow queries)
Redis (memory, hit rate)

Infrastructure:

CPU/Memory/Disk on all nodes
Network connectivity
SSL certificate expiry

Security:

Failed login attempts
Unauthorized access
Vulnerability scan results

Alert Routing

Severity	Channel	Response Time
Critical	Signal + Slack @channel	Immediate
Warning	Slack #alerts	1 hour
Info	Slack #ops	Next business day

Dashboard URLs

Once deployed:

Main Dashboard: https://grafana.heady.local/d/heady-overview
Manager Metrics: https://grafana.heady.local/d/manager-details
Imagination Engine: https://grafana.heady.local/d/imagination

Troubleshooting

DNS Not Resolving

# Windows
ipconfig /flushdns

# macOS
sudo killall -HUP mDNSResponder

# Linux
sudo systemd-resolve --flush-caches

Build Fails

# Check for internal.headyio.com references still present
.\scripts\hc-infrastructure-setup.ps1 -Mode inventory

# Clean and retry
Remove-Item -Recurse -Force node_modules, dist
npm cache clean --force
.\scripts\hc-infrastructure-setup.ps1 -Mode clean-build

Extension Not Loading

# Chrome: Load unpacked extension
# 1. chrome://extensions
# 2. Enable "Developer mode"
# 3. "Load unpacked" → select distribution/browser/extensions/chrome/

# VS Code: Install from VSIX
# 1. Extensions view
# 2. "..." menu → "Install from VSIX"
# 3. Select distribution/ide/vscode/heady-*.vsix

Maintenance

Weekly Tasks

# 1. Run clean build to verify health
.\scripts\hc-infrastructure-setup.ps1 -Mode clean-build

# 2. Check for drift in internal.headyio.com references
.\scripts\hc-infrastructure-setup.ps1 -Mode inventory

# 3. Update dependencies
npm outdated
# Review and update as needed

Monthly Tasks

Review and rotate secrets
Update browser/IDE extensions
Check disk usage on all nodes
Verify backup integrity

Environment-Specific Notes

Local Development

All services run on internal.headyio.com (via hosts file mapping)
Use heady.local domains for consistency with production
Hot reload enabled for manager/frontend

Staging

Separate subdomain: *.staging.internal.heady.systems
Auto-deploy from develop branch
Reduced resource limits
Test data only

Production

Public domains: *.heady.systems
Manual approval required for deploys
Full monitoring and alerting
Multi-region if configured

Next Steps

After running full-setup:

Verify domains: curl http://manager.heady.local:3300/api/health
Start developing: npm run dev in manager and frontend
Run tests: npm test
Check dashboards: http://grafana.heady.local

Support

If issues occur:

Check logs: Get-Content /var/log/heady/manager.log -Tail 50
Review alerts in Slack
Check runbook: https://docs.heady.io/runbooks/
File issue: https://github.com/HeadySystems/Heady/issues

Part of the Heady Sacred Geometry Infrastructure Clean builds | Domain-driven | Alert-driven | Human-in-the-loop

Install hcip-infrastructure-setup and it becomes one more candidate the router can pick - when it fits.

A listing is a routing target with a manifest: what it does, which domains it covers, what it costs and who publishes it. Once installed it sits beside your own models and tools, is scored like any other candidate for each request, and shows up in the trace when it wins. Ratings come from workspaces that installed it, one per account.

# Heady Complete Infrastructure Pipeline (HCIP) This workflow systematically sets up the entire Heady infrastructure: 1. Replaces internal.headyio.com with service domains 2. Configures clean-build CI/CD with error alerting 3. Provisions all devices with extensions 4. Sets up observability and alerting ## Prerequisites - PowerShell 7+ (Windows) or PowerShell Core (macOS/Linux) - Admin/sudo access for hosts file modification - Node.js 20+ and Python 3.12+ for builds ## Quick Start ```powershell # Run complete setup .\scripts\hc-infrastructure-setup.ps1 -Mode full-setup # Or step by step .\scripts\hc-infrastructure-setup.ps1 -Mode inventory # Find internal.headyio.com refs .\scripts\hc-infrastructure-setup.ps1 -Mode migrate # Replace with domains .\scripts\hc-infrastructure-setup.ps1 -Mode provision # Install everything .\scripts\hc-infrastructure-setup.ps1 -Mode clean-build # Build from scratch ``` ## Mode Details ### 1. Inventory Mode Scans entire codebase for localhost/internal.headyio.com references and creates a migration plan. ```powershell .\scripts\hc-infrastructure-setup.ps1 -Mode inventory ``` **Output:** - CSV file with all internal.headyio.com references - Suggested domain replacements - Service-to-port mapping ### 2. Migrate Mode Replaces localhost references with proper service domains and updates hosts file. ```powershell .\scripts\hc-infrastructure-setup.ps1 -Mode migrate # Or skip confirmation .\scripts\hc-infrastructure-setup.ps1 -Mode migrate -Force ``` **Changes:** - Replaces `localhost:3300` → `manager.heady.local` - Replaces `localhost:5000` → `worker.heady.local` - Replaces `localhost:3000` → `dashboard.heady.local` - Updates `/etc/hosts` or `C:\Windows\System32\drivers\etc\hosts` - Backs up original hosts file **DNS Entries Created:** ``` internal.headyio.com manager.heady.local internal.headyio.com worker.heady.local internal.headyio.com dashboard.heady.local internal.headyio.com www.heady.local internal.headyio.com api.heady.local internal.headyio.com cache.heady.local internal.headyio.com db.heady.local internal.headyio.com metrics.heady.local internal.headyio.com grafana.heady.local internal.headyio.com imagination.heady.local internal.headyio.com traces.heady.local internal.headyio.com alerts.heady.local ``` ### 3. Provision Mode Installs all required applications, extensions, and configurations. ```powershell .\scripts\hc-infrastructure-setup.ps1 -Mode provision ``` **Installs:** - **Browsers:** Chrome, Firefox, Edge (with extensions) - **Editors:** VS Code, JetBrains toolbox (with extensions) - **Languages:** Node.js 20.18.1, Python 3.12.7 - **Tools:** Docker, Git, Postman, 1Password, Slack, Discord - **Heady-specific:** Local extensions from `distribution/` **VS Code Extensions:** - TypeScript, Python, ESLint, Prettier support - Docker, Kubernetes, YAML tools - GitLens, GitHub Copilot - Heady Dev Companion (local) **Browser Extensions:** - React/Redux DevTools - Heady Companion (local build) - Wappalyzer (technology profiler) - uBlock Origin (ad/tracker blocker) ### 4. Clean-Build Mode Performs a full clean build with error alerting (no auto-rebuild). ```powershell .\scripts\hc-infrastructure-setup.ps1 -Mode clean-build ``` **Build Steps:** 1. Clean environment (remove node_modules, dist, cache) 2. Install dependencies (`npm ci`) 3. Lint code 4. Run tests 5. Build application 6. Verify artifacts **Error Handling:** - ❌ **NO AUTO-REBUILD** - If build fails, alerts are sent - Errors are classified: network, permission, code, resource - Desktop notification + webhook alert (if configured) - Human must fix issue and manually retry **Configure Alerts:** ```powershell $env:HEADY_ALERT_WEBHOOK = "https://hooks.slack.com/services/YOUR/WEBHOOK/URL" .\scripts\hc-infrastructure-setup.ps1 -Mode clean-build ``` ### 5. Full-Setup Mode Runs all modes in sequence for complete setup. ```powershell .\scripts\hc-infrastructure-setup.ps1 -Mode full-setup ``` **Timeline:** - Inventory: ~30 seconds - Migrate: ~10 seconds - Provision: 5-15 minutes (downloads) - Clean-build: 3-10 minutes ## Service Domain Reference | Service | Old URL | New Domain | Port | |---------|---------|------------|------| | Heady Manager | internal.headyio.com:3300 | manager.heady.local | 3300 | | Python Worker | localhost:5000 | worker.heady.local | 5000 | | Web Dashboard | localhost:3000 | dashboard.heady.local | 3000 | | Public Site | localhost:8080 | www.heady.local | 8080 | | API Gateway | localhost:8081 | api.heady.local | 8081 | | Redis Cache | localhost:6379 | cache.heady.local | 6379 | | PostgreSQL | localhost:5432 | db.heady.local | 5432 | | Metrics | localhost:9090 | metrics.heady.local | 9090 | | Grafana | localhost:3001 | grafana.heady.local | 3001 | | Imagination | localhost:3400 | imagination.heady.local | 3400 | ## CI/CD Integration ### GitHub Actions Workflow The `.github/workflows/clean-build.yml` runs on every push: ```yaml on: push: branches: [main, develop] pull_request: branches: [main] ``` **Jobs:** 1. **Pre-flight:** Checks for internal.headyio.com references 2. **Build Manager:** Clean Node.js build 3. **Build Frontend:** React app build 4. **Build Worker:** Python + Docker 5. **Integration Tests:** Full stack testing 6. **Security Scan:** Trivy vulnerability check 7. **Deploy Staging:** Auto-deploy on develop 8. **Deploy Production:** Manual approval on main **Key Features:** - Full clean build every time (no incremental artifacts) - Pinned dependencies (lockfiles committed) - Deterministic builds - Error classification + retry for transient issues - Slack notifications for failures/deployments ### Local Clean Build For development, use the script: ```powershell # Before committing .\scripts\hc-infrastructure-setup.ps1 -Mode clean-build # This ensures what you push matches CI ``` ## Device Management ### Cross-Platform Setup **Windows (Intune/Autopilot):** ```powershell # Initial enrollment & $env:SystemRoot\System32\WindowsPowerShell\v1.0\powershell.exe -Command " Install-Script -Name Get-WindowsAutoPilotInfo -Force Get-WindowsAutoPilotInfo -Online " ``` **macOS (MDM):** ```bash # Apple Business Manager enrollment # Device appears in MDM console automatically # Heady profile pushed over-the-air ``` **Linux (Ansible):** ```bash # Run device provisioning playbook ansible-playbook -i inventory/internal.headyio.com device-provision.yml ``` ### Required Applications (All Devices) **Security:** - 1Password (password manager) - VPN client (Tailscale/WireGuard) - 2FA authenticator **Communication:** - Signal (secure messaging) - Slack (team chat) - Discord (community) **Productivity:** - Obsidian (knowledge base) - Figma (design) - Notion (docs) ### Development Workstation (Additional) **Languages & Runtimes:** - Node.js 20.18.1 - Python 3.12.7 - Docker Desktop - Git **Browsers (all with dev profile):** - Chrome + React/Vue DevTools + Heady Companion - Firefox + Heady Assistant - Edge (backup) **Editors:** - VS Code + 15+ extensions - JetBrains toolbox (IntelliJ, PyCharm, WebStorm) ## Monitoring & Alerting ### What Gets Monitored **Services:** - Heady Manager (health, response time, error rate) - Python Worker (queue depth, processing time) - PostgreSQL (connections, slow queries) - Redis (memory, hit rate) **Infrastructure:** - CPU/Memory/Disk on all nodes - Network connectivity - SSL certificate expiry **Security:** - Failed login attempts - Unauthorized access - Vulnerability scan results ### Alert Routing | Severity | Channel | Response Time | |----------|---------|---------------| | Critical | Signal + Slack @channel | Immediate | | Warning | Slack #alerts | 1 hour | | Info | Slack #ops | Next business day | ### Dashboard URLs Once deployed: - **Main Dashboard:** https://grafana.heady.local/d/heady-overview - **Manager Metrics:** https://grafana.heady.local/d/manager-details - **Imagination Engine:** https://grafana.heady.local/d/imagination ## Troubleshooting ### DNS Not Resolving ```powershell # Windows ipconfig /flushdns # macOS sudo killall -HUP mDNSResponder # Linux sudo systemd-resolve --flush-caches ``` ### Build Fails ```powershell # Check for internal.headyio.com references still present .\scripts\hc-infrastructure-setup.ps1 -Mode inventory # Clean and retry Remove-Item -Recurse -Force node_modules, dist npm cache clean --force .\scripts\hc-infrastructure-setup.ps1 -Mode clean-build ``` ### Extension Not Loading ```powershell # Chrome: Load unpacked extension # 1. chrome://extensions # 2. Enable "Developer mode" # 3. "Load unpacked" → select distribution/browser/extensions/chrome/ # VS Code: Install from VSIX # 1. Extensions view # 2. "..." menu → "Install from VSIX" # 3. Select distribution/ide/vscode/heady-*.vsix ``` ## Maintenance ### Weekly Tasks ```powershell # 1. Run clean build to verify health .\scripts\hc-infrastructure-setup.ps1 -Mode clean-build # 2. Check for drift in internal.headyio.com references .\scripts\hc-infrastructure-setup.ps1 -Mode inventory # 3. Update dependencies npm outdated # Review and update as needed ``` ### Monthly Tasks 1. Review and rotate secrets 2. Update browser/IDE extensions 3. Check disk usage on all nodes 4. Verify backup integrity ## Environment-Specific Notes ### Local Development - All services run on internal.headyio.com (via hosts file mapping) - Use `heady.local` domains for consistency with production - Hot reload enabled for manager/frontend ### Staging - Separate subdomain: `*.staging.internal.heady.systems` - Auto-deploy from develop branch - Reduced resource limits - Test data only ### Production - Public domains: `*.heady.systems` - Manual approval required for deploys - Full monitoring and alerting - Multi-region if configured ## Next Steps After running full-setup: 1. **Verify domains:** `curl http://manager.heady.local:3300/api/health` 2. **Start developing:** `npm run dev` in manager and frontend 3. **Run tests:** `npm test` 4. **Check dashboards:** http://grafana.heady.local ## Support If issues occur: 1. Check logs: `Get-Content /var/log/heady/manager.log -Tail 50` 2. Review alerts in Slack 3. Check runbook: https://docs.heady.io/runbooks/ 4. File issue: https://github.com/HeadySystems/Heady/issues --- *Part of the Heady Sacred Geometry Infrastructure* *Clean builds | Domain-driven | Alert-driven | Human-in-the-loop*

{ "prompt": "# Heady Complete Infrastructure Pipeline (HCIP)\n\nThis workflow systematically sets up the entire Heady infrastructure:\n1. Replaces internal.headyio.com with service domains\n2. Configures clean-build CI/CD with error alerting\n3. Provisions all devices with extensions\n4. Sets up observability and alerting\n\n## Prerequisites\n\n- PowerShell 7+ (Windows) or PowerShell Core (macOS/Linux)\n- Admin/sudo access for hosts file modification\n- Node.js 20+ and Python 3.12+ for builds\n\n## Quick Start\n\n```powershell\n# Run complete setup\n.\\scripts\\hc-infrastructure-setup.ps1 -Mode full-setup\n\n# Or step by step\n.\\scripts\\hc-infrastructure-setup.ps1 -Mode inventory # Find internal.headyio.com refs\n.\\scripts\\hc-infrastructure-setup.ps1 -Mode migrate # Replace with domains\n.\\scripts\\hc-infrastructure-setup.ps1 -Mode provision # Install everything\n.\\scripts\\hc-infrastructure-setup.ps1 -Mode clean-build # Build from scratch\n```\n\n## Mode Details\n\n### 1. Inventory Mode\n\nScans entire codebase for localhost/internal.headyio.com references and creates a migration plan.\n\n```powershell\n.\\scripts\\hc-infrastructure-setup.ps1 -Mode inventory\n```\n\n**Output:**\n- CSV file with all internal.headyio.com references\n- Suggested domain replacements\n- Service-to-port mapping\n\n### 2. Migrate Mode\n\nReplaces localhost references with proper service domains and updates hosts file.\n\n```powershell\n.\\scripts\\hc-infrastructure-setup.ps1 -Mode migrate\n# Or skip confirmation\n.\\scripts\\hc-infrastructure-setup.ps1 -Mode migrate -Force\n```\n\n**Changes:**\n- Replaces `localhost:3300` → `manager.heady.local`\n- Replaces `localhost:5000` → `worker.heady.local`\n- Replaces `localhost:3000` → `dashboard.heady.local`\n- Updates `/etc/hosts` or `C:\\Windows\\System32\\drivers\\etc\\hosts`\n- Backs up original hosts file\n\n**DNS Entries Created:**\n```\ninternal.headyio.com manager.heady.local\ninternal.headyio.com worker.heady.local\ninternal.headyio.com dashboard.heady.local\ninternal.headyio.com www.heady.local\ninternal.headyio.com api.heady.local\ninternal.headyio.com cache.heady.local\ninternal.headyio.com db.heady.local\ninternal.headyio.com metrics.heady.local\ninternal.headyio.com grafana.heady.local\ninternal.headyio.com imagination.heady.local\ninternal.headyio.com traces.heady.local\ninternal.headyio.com alerts.heady.local\n```\n\n### 3. Provision Mode\n\nInstalls all required applications, extensions, and configurations.\n\n```powershell\n.\\scripts\\hc-infrastructure-setup.ps1 -Mode provision\n```\n\n**Installs:**\n- **Browsers:** Chrome, Firefox, Edge (with extensions)\n- **Editors:** VS Code, JetBrains toolbox (with extensions)\n- **Languages:** Node.js 20.18.1, Python 3.12.7\n- **Tools:** Docker, Git, Postman, 1Password, Slack, Discord\n- **Heady-specific:** Local extensions from `distribution/`\n\n**VS Code Extensions:**\n- TypeScript, Python, ESLint, Prettier support\n- Docker, Kubernetes, YAML tools\n- GitLens, GitHub Copilot\n- Heady Dev Companion (local)\n\n**Browser Extensions:**\n- React/Redux DevTools\n- Heady Companion (local build)\n- Wappalyzer (technology profiler)\n- uBlock Origin (ad/tracker blocker)\n\n### 4. Clean-Build Mode\n\nPerforms a full clean build with error alerting (no auto-rebuild).\n\n```powershell\n.\\scripts\\hc-infrastructure-setup.ps1 -Mode clean-build\n```\n\n**Build Steps:**\n1. Clean environment (remove node_modules, dist, cache)\n2. Install dependencies (`npm ci`)\n3. Lint code\n4. Run tests\n5. Build application\n6. Verify artifacts\n\n**Error Handling:**\n- ❌ **NO AUTO-REBUILD** - If build fails, alerts are sent\n- Errors are classified: network, permission, code, resource\n- Desktop notification + webhook alert (if configured)\n- Human must fix issue and manually retry\n\n**Configure Alerts:**\n```powershell\n$env:HEADY_ALERT_WEBHOOK = \"https://hooks.slack.com/services/YOUR/WEBHOOK/URL\"\n.\\scripts\\hc-infrastructure-setup.ps1 -Mode clean-build\n```\n\n### 5. Full-Setup Mode\n\nRuns all modes in sequence for complete setup.\n\n```powershell\n.\\scripts\\hc-infrastructure-setup.ps1 -Mode full-setup\n```\n\n**Timeline:**\n- Inventory: ~30 seconds\n- Migrate: ~10 seconds\n- Provision: 5-15 minutes (downloads)\n- Clean-build: 3-10 minutes\n\n## Service Domain Reference\n\n| Service | Old URL | New Domain | Port |\n|---------|---------|------------|------|\n| Heady Manager | internal.headyio.com:3300 | manager.heady.local | 3300 |\n| Python Worker | localhost:5000 | worker.heady.local | 5000 |\n| Web Dashboard | localhost:3000 | dashboard.heady.local | 3000 |\n| Public Site | localhost:8080 | www.heady.local | 8080 |\n| API Gateway | localhost:8081 | api.heady.local | 8081 |\n| Redis Cache | localhost:6379 | cache.heady.local | 6379 |\n| PostgreSQL | localhost:5432 | db.heady.local | 5432 |\n| Metrics | localhost:9090 | metrics.heady.local | 9090 |\n| Grafana | localhost:3001 | grafana.heady.local | 3001 |\n| Imagination | localhost:3400 | imagination.heady.local | 3400 |\n\n## CI/CD Integration\n\n### GitHub Actions Workflow\n\nThe `.github/workflows/clean-build.yml` runs on every push:\n\n```yaml\non:\n push:\n branches: [main, develop]\n pull_request:\n branches: [main]\n```\n\n**Jobs:**\n1. **Pre-flight:** Checks for internal.headyio.com references\n2. **Build Manager:** Clean Node.js build\n3. **Build Frontend:** React app build\n4. **Build Worker:** Python + Docker\n5. **Integration Tests:** Full stack testing\n6. **Security Scan:** Trivy vulnerability check\n7. **Deploy Staging:** Auto-deploy on develop\n8. **Deploy Production:** Manual approval on main\n\n**Key Features:**\n- Full clean build every time (no incremental artifacts)\n- Pinned dependencies (lockfiles committed)\n- Deterministic builds\n- Error classification + retry for transient issues\n- Slack notifications for failures/deployments\n\n### Local Clean Build\n\nFor development, use the script:\n\n```powershell\n# Before committing\n.\\scripts\\hc-infrastructure-setup.ps1 -Mode clean-build\n\n# This ensures what you push matches CI\n```\n\n## Device Management\n\n### Cross-Platform Setup\n\n**Windows (Intune/Autopilot):**\n```powershell\n# Initial enrollment\n& $env:SystemRoot\\System32\\WindowsPowerShell\\v1.0\\powershell.exe -Command \"\n Install-Script -Name Get-WindowsAutoPilotInfo -Force\n Get-WindowsAutoPilotInfo -Online\n\"\n```\n\n**macOS (MDM):**\n```bash\n# Apple Business Manager enrollment\n# Device appears in MDM console automatically\n# Heady profile pushed over-the-air\n```\n\n**Linux (Ansible):**\n```bash\n# Run device provisioning playbook\nansible-playbook -i inventory/internal.headyio.com device-provision.yml\n```\n\n### Required Applications (All Devices)\n\n**Security:**\n- 1Password (password manager)\n- VPN client (Tailscale/WireGuard)\n- 2FA authenticator\n\n**Communication:**\n- Signal (secure messaging)\n- Slack (team chat)\n- Discord (community)\n\n**Productivity:**\n- Obsidian (knowledge base)\n- Figma (design)\n- Notion (docs)\n\n### Development Workstation (Additional)\n\n**Languages & Runtimes:**\n- Node.js 20.18.1\n- Python 3.12.7\n- Docker Desktop\n- Git\n\n**Browsers (all with dev profile):**\n- Chrome + React/Vue DevTools + Heady Companion\n- Firefox + Heady Assistant\n- Edge (backup)\n\n**Editors:**\n- VS Code + 15+ extensions\n- JetBrains toolbox (IntelliJ, PyCharm, WebStorm)\n\n## Monitoring & Alerting\n\n### What Gets Monitored\n\n**Services:**\n- Heady Manager (health, response time, error rate)\n- Python Worker (queue depth, processing time)\n- PostgreSQL (connections, slow queries)\n- Redis (memory, hit rate)\n\n**Infrastructure:**\n- CPU/Memory/Disk on all nodes\n- Network connectivity\n- SSL certificate expiry\n\n**Security:**\n- Failed login attempts\n- Unauthorized access\n- Vulnerability scan results\n\n### Alert Routing\n\n| Severity | Channel | Response Time |\n|----------|---------|---------------|\n| Critical | Signal + Slack @channel | Immediate |\n| Warning | Slack #alerts | 1 hour |\n| Info | Slack #ops | Next business day |\n\n### Dashboard URLs\n\nOnce deployed:\n- **Main Dashboard:** https://grafana.heady.local/d/heady-overview\n- **Manager Metrics:** https://grafana.heady.local/d/manager-details\n- **Imagination Engine:** https://grafana.heady.local/d/imagination\n\n## Troubleshooting\n\n### DNS Not Resolving\n\n```powershell\n# Windows\nipconfig /flushdns\n\n# macOS\nsudo killall -HUP mDNSResponder\n\n# Linux\nsudo systemd-resolve --flush-caches\n```\n\n### Build Fails\n\n```powershell\n# Check for internal.headyio.com references still present\n.\\scripts\\hc-infrastructure-setup.ps1 -Mode inventory\n\n# Clean and retry\nRemove-Item -Recurse -Force node_modules, dist\nnpm cache clean --force\n.\\scripts\\hc-infrastructure-setup.ps1 -Mode clean-build\n```\n\n### Extension Not Loading\n\n```powershell\n# Chrome: Load unpacked extension\n# 1. chrome://extensions\n# 2. Enable \"Developer mode\"\n# 3. \"Load unpacked\" → select distribution/browser/extensions/chrome/\n\n# VS Code: Install from VSIX\n# 1. Extensions view\n# 2. \"...\" menu → \"Install from VSIX\"\n# 3. Select distribution/ide/vscode/heady-*.vsix\n```\n\n## Maintenance\n\n### Weekly Tasks\n\n```powershell\n# 1. Run clean build to verify health\n.\\scripts\\hc-infrastructure-setup.ps1 -Mode clean-build\n\n# 2. Check for drift in internal.headyio.com references\n.\\scripts\\hc-infrastructure-setup.ps1 -Mode inventory\n\n# 3. Update dependencies\nnpm outdated\n# Review and update as needed\n```\n\n### Monthly Tasks\n\n1. Review and rotate secrets\n2. Update browser/IDE extensions\n3. Check disk usage on all nodes\n4. Verify backup integrity\n\n## Environment-Specific Notes\n\n### Local Development\n\n- All services run on internal.headyio.com (via hosts file mapping)\n- Use `heady.local` domains for consistency with production\n- Hot reload enabled for manager/frontend\n\n### Staging\n\n- Separate subdomain: `*.staging.internal.heady.systems`\n- Auto-deploy from develop branch\n- Reduced resource limits\n- Test data only\n\n### Production\n\n- Public domains: `*.heady.systems`\n- Manual approval required for deploys\n- Full monitoring and alerting\n- Multi-region if configured\n\n## Next Steps\n\nAfter running full-setup:\n\n1. **Verify domains:** `curl http://manager.heady.local:3300/api/health`\n2. **Start developing:** `npm run dev` in manager and frontend\n3. **Run tests:** `npm test`\n4. **Check dashboards:** http://grafana.heady.local\n\n## Support\n\nIf issues occur:\n1. Check logs: `Get-Content /var/log/heady/manager.log -Tail 50`\n2. Review alerts in Slack\n3. Check runbook: https://docs.heady.io/runbooks/\n4. File issue: https://github.com/HeadySystems/Heady/issues\n\n---\n\n*Part of the Heady Sacred Geometry Infrastructure*\n*Clean builds | Domain-driven | Alert-driven | Human-in-the-loop*", "variables": [], "notes": "HCFP Infrastructure Setup - Clean builds, domain migration, device provisioning", "metadata": { "source": { "provider": "github-windsurf-workflows", "repository": "https://github.com/HeadySystems/Heady-Testing", "path": ".windsurf/workflows/hcip-infrastructure-setup.md", "ref": "688dd9a613128f74bfb8687c36e5349ee1e2d942", "url": "https://github.com/HeadySystems/Heady-Testing/blob/688dd9a613128f74bfb8687c36e5349ee1e2d942/.windsurf/workflows/hcip-infrastructure-setup.md", "key": "HeadySystems/Heady-Testing/.windsurf/workflows/hcip-infrastructure-setup.md" } } }