Full System Rundown

🚀 1. Daily Awareness Sync (GitHub Actions + Scripts)

Trigger: Automatically runs daily or manually.

Process: GitHub Actions executes Node.js scripts like scanSiteStructure.js and componentScan.js. These scripts generate JSON outputs in /data/, such as:

• code-footprint.json, js-function-map.json, ai-prompts.json, etc.
• nova-session-boot.txt (Nova's boot memory seed)
• Data is committed and deployed via Azure Static Web Apps

🌐 2. Site Deploy & Boot Memory Load

The homepage loads nova-session-boot.html which gives Nova her context, memory state, and intro message.

📊 3. Nova Awareness Dashboard (/nova/index.html)

The dashboard displays Nova’s state and logs using modules styled in a 12-column grid. Key files:

• nova.css: dashboard-specific visual style
• nova-dashboard.js: fetches + renders JSON data
• Chart.js powers visualizations

Modules include: Memory Snapshot, Awareness Logs, Prompt History, API Monitor, Unused CSS Report, Code Footprint, Image Grid, Function Map.

🧠 4. Nova's Awareness in Practice

Nova references this data in real-time and displays it dynamically. Visitors and Nova alike stay in sync with the state of the site.

🧪 5. Code Awareness Sensor (NEW)

Feature: Nova now parses the full codebase—JS, CSS, and HTML—to detect key logic patterns, file size trends, and new or removed functions.

• Data file: code-map.json
• Script: generateNovaBoot.js now includes this logic
• Example insight: "fadeIn() function added to nav.js"

This is visualized in the dashboard and may influence Nova’s logs or mood.

♻️ Summary: End-to-End Flow

1. GitHub Actions → Runs daily
2. Node Scripts → Generate awareness data as JSON
3. Git Commit + Push → Triggers Azure deploy
4. Site Loads → Nova reads nova-session-boot.txt
5. Dashboard Renders → JSON modules populate view
6. Nova Speaks → Uses this context across the site