<<<<<<< HEAD
=======
a3d7d06c432bf92df85e53f8d0cf1e6c8622ccea
Sacred Geometry :: Organic Systems :: Breathing Interfaces
<<<<<<< HEAD
HeadyCloud is live and operational with complete auto-deployment capabilities. All services are running at optimal performance with 100% HeadyBrain dominance and persistent memory integration.
- HeadyCloud API: https://headysystems.com/api
- HeadyManager: https://headysystems.com/manager
- Registry Service: https://headysystems.com/registry
- Brain Service: https://brain.headysystems.com
- Auto-Deploy Pipeline: Active and operational
# Clone and auto-deploy
git clone https://github.com/HeadySystems/Heady.git
cd Heady
./scripts/run-auto-deploy.ps1 -ForceProductionAll services automatically deploy to HeadyCloud - no local setup required.
- 100% HeadyBrain Dominance: All operations routed through HeadyBrain
- Persistent Memory System: Deep data scanning with pre-execution optimization
- Adaptive Complexity: Intelligent orchestration based on task requirements
- Monte Carlo Optimization: Real-time performance optimization
- Pattern Recognition: Self-learning system with continuous improvement
Get started with Heady applications:
- HeadyBuddy - Android companion
- HeadyIDE - Desktop AI assistant
- HeadyBrowser - Web extension
- HeadyServices - Backend system
- Heady API - Service interaction
- HeadyMCP - Manager Control Plane
Deeper integration and API documentation:
- Service Integration - How Heady services connect
- HeadyManager API - Service endpoints reference
=======
npm install
cp .env.example .env
npm run deva3d7d06c432bf92df85e53f8d0cf1e6c8622ccea
heady-manager.js # Node.js MCP Server & API Gateway (port 3300)
├── src/ # Core pipeline engine & agents
├── backend/ # Python worker & MCP servers
├── frontend/ # React UI (Vite + TailwindCSS)
<<<<<<< HEAD
├── HeadyAcademy/ # AI Nodes & Tools (JULES, OBSERVER, BUILDER, ATLAS, PYTHIA)
├── configs/ # YAML configuration (pipeline, resources, governance)
├── scripts/ # Automation (Sync, Build, Deploy, Checkpoint)
├── notebooks/ # Colab notebooks (quick-start, tutorials, examples)
├── docs/ # Documentation & Notion templates
└── heady-registry.json # HeadyRegistry — central catalog of the ecosystem
=======
├── HeadyAcademy/ # AI Nodes & Tools
├── configs/ # YAML configuration
├── scripts/ # Automation (Sync, Build, Deploy)
└── workers/ # Edge workers
>>>>>>> a3d7d06c432bf92df85e53f8d0cf1e6c8622ccea
| Endpoint | Description |
|---|---|
GET /api/health |
Health check |
GET /api/pulse |
System pulse with layer info |
GET /api/system/status |
Full system status |
POST /api/pipeline/run |
Trigger pipeline run |
GET /api/pipeline/state |
Current pipeline state |
GET /api/nodes |
List all AI nodes |
| <<<<<<< HEAD | |
GET /api/registry |
Full HeadyRegistry catalog |
GET /api/registry/component/:id |
Lookup a specific component |
GET /api/registry/environments |
List all environments |
GET /api/registry/docs |
List registered documents |
GET /api/registry/notebooks |
List registered notebooks |
GET /api/registry/patterns |
List architecture patterns |
GET /api/registry/workflows |
List workflows |
GET /api/registry/ai-nodes |
List AI nodes from registry |
The Heady CLI provides command-line access to Heady services:
# Set API key (or add to .env)
export HEADY_API_KEY="your_api_key"
# Run CLI
npm run cli
# or directly:
python scripts/heady_cli.pySee scripts/heady_cli.md for full documentation.
All files are kept in sync at every checkpoint (commit, merge, pipeline completion, release). See docs/CHECKPOINT_PROTOCOL.md for the full protocol.
.\scripts\checkpoint-sync.ps1 # Full sync
.\scripts\checkpoint-sync.ps1 -Mode check # Read-only drift detection
.\scripts\checkpoint-sync.ps1 -Mode fix # Auto-fix issuesheady-registry.json is the central catalog of the entire ecosystem:
- Components — services, modules, apps
- AI Nodes — JULES, OBSERVER, BUILDER, ATLAS, PYTHIA
- Workflows — HCFullPipeline, HeadySync, Checkpoint Sync
- Environments — local, cloud-me, cloud-sys, cloud-conn, hybrid
- Patterns — Sacred Geometry, Checkpoint Protocol, Direct Routing
- Docs & Notebooks — tracked with version and review status
Colab notebooks are stored under notebooks/ and validated in CI:
| Notebook | Purpose |
|---|---|
notebooks/quick-start/heady-quick-start.ipynb |
Fast system orientation |
notebooks/tutorials/hcfullpipeline-walkthrough.ipynb |
Pipeline deep-dive |
notebooks/examples/registry-api-demo.ipynb |
Registry API examples |
| Path | Purpose |
|---|---|
docs/CHECKPOINT_PROTOCOL.md |
Master protocol for keeping all files in sync |
docs/DOC_OWNERS.yaml |
Document ownership & review tracker |
docs/notion-quick-start.md |
Notion Quick Start template |
docs/notion-project-notebook.md |
Notion Project Notebook template |
docs/heady-services-manual.md |
Comprehensive services manual |
CLAUDE.md |
Claude Code integration protocol |
This project supports Python development with PyCharm and Google Colab integration.
data/ # Data directories
├── raw/ # Raw data files (git-ignored)
├── processed/ # Processed data
└── external/ # External data (git-ignored)
notebooks/ # Jupyter notebooks
├── exploratory/ # Scratch, EDA, experiments
├── reports/ # Clean, final notebooks
├── archive/ # Retired notebooks
└── figures/ # Exported plots/images
src/ # Reusable Python code
tests/ # Unit tests
# Install Python dependencies
pip install -r requirements.txt
# For PyCharm: Open as Python project
# For Colab: See COLAB_WORKFLOW.mdrequirements.txt- Python dependenciesNOTEBOOK_TEMPLATE.md- Template for new notebooksCOLAB_WORKFLOW.md- Google Colab workflow guide.env.example- Environment variables template ======= |POST /api/system/production| Activate production mode |
a3d7d06c432bf92df85e53f8d0cf1e6c8622ccea
Deployed via Render.com using render.yaml.
Proprietary - Heady Systems <<<<<<< HEAD
=======
a3d7d06c432bf92df85e53f8d0cf1e6c8622ccea