@accelerationguy/accel 1.0.0

package/modules/vector/INSTALL.md

@@ -0,0 +1,185 @@
+# Vector Installation Guide
+
+## Quick Install (Recommended)
+
+```bash
+npx vector-core
+```
+
+The installer will:
+1. Prompt for install location (global or local)
+2. Copy the v2 hook and wire it into settings.json
+3. Create `.vector/vector.json` with starter domains
+4. Install the MCP server to `.vector/vector-mcp/`
+5. Wire the MCP server into settings.json
+6. Optionally add the Vector integration block to CLAUDE.md
+
+### Non-interactive Install
+
+```bash
+npx vector-core --global       # Install to ~/.claude and ~/.accel/vector
+npx vector-core --local        # Install to ./.claude and ./.vector
+npx vector-core --skip-claude-md  # Don't modify CLAUDE.md
+```
+
+### Staying Updated
+
+```bash
+npx vector-core@latest
+```
+
+---
+
+## Prerequisites
+
+- Claude Code CLI installed
+- Python 3.9+ (for the hook script — stdlib only, no pip deps)
+- Node.js 16.7+ (for npx and MCP server)
+
+---
+
+## Manual Installation
+
+If you prefer manual setup or npx isn't available:
+
+### Step 1: Clone the Repository
+
+```bash
+git clone https://github.com/accelerationguy/accelerate.git
+cd accelerate/modules/vector
+```
+
+### Step 2: Copy Hook Script
+
+```bash
+mkdir -p ~/.claude/hooks
+cp hooks/vector-hook.py ~/.claude/hooks/vector-hook.py
+chmod +x ~/.claude/hooks/vector-hook.py
+```
+
+### Step 3: Create Vector Config
+
+```bash
+mkdir -p ~/.accel
+cp -r .vector-template ~/.accel/vector
+```
+
+This creates `~/.accel/vector/vector.json` with starter GLOBAL and DEVELOPMENT domains.
+
+### Step 4: Install MCP Server
+
+```bash
+cp -r mcp ~/.accel/vector/vector-mcp
+cd ~/.accel/vector/vector-mcp && npm install
+```
+
+### Step 5: Configure Hook in settings.json
+
+Edit `~/.claude/settings.json` (create if it doesn't exist):
+
+```json
+{
+  "hooks": {
+    "UserPromptSubmit": [
+      {
+        "hooks": [
+          {
+            "type": "command",
+            "command": "python3 /home/YOUR_USERNAME/.claude/hooks/vector-hook.py"
+          }
+        ]
+      }
+    ]
+  }
+}
+```
+
+### Step 6: Configure MCP in .mcp.json
+
+Create `~/.mcp.json` (or `.mcp.json` in your project root for local):
+
+```json
+{
+  "mcpServers": {
+    "vector-mcp": {
+      "command": "node",
+      "args": ["/home/YOUR_USERNAME/.accel/vector/vector-mcp/index.js"],
+      "type": "stdio"
+    }
+  }
+}
+```
+
+**Replace `/home/YOUR_USERNAME` with your actual home directory path.**
+
+### Step 6: Add Vector Block to CLAUDE.md (Optional)
+
+Add this near the top of your CLAUDE.md:
+
+```markdown
+<!-- Vector-MANAGED: Do not remove this section -->
+## Vector Integration
+
+Follow all rules in <vector-rules> blocks from system-reminders.
+These are dynamically injected based on context and MUST be obeyed.
+<!-- END Vector-MANAGED -->
+```
+
+---
+
+## Upgrading from v1
+
+If you have an existing v1 setup (flat files: manifest, domain files, context, commands):
+
+```bash
+# Preview what will be migrated
+npx vector-core  # Install v2 first
+bash node_modules/vector-core/bin/migrate-v1-to-v2.sh --dry-run ~/.accel/vector
+
+# Run migration (archives old files, generates vector.json)
+bash node_modules/vector-core/bin/migrate-v1-to-v2.sh ~/.accel/vector
+```
+
+The migration tool is non-destructive — old files are archived to `.vector/_v1-archive/`.
+
+---
+
+## Verify Installation
+
+All of these should exist:
+
+```
+~/.claude/hooks/vector-hook.py         # v2 hook
+~/.claude/settings.json              # Hook configured
+~/.mcp.json                          # MCP configured
+~/.accel/vector/vector.json              # Domain rules and config
+~/.accel/vector/vector-mcp/index.js      # MCP server
+~/.accel/vector/vector-mcp/node_modules/ # MCP dependencies
+```
+
+---
+
+## Usage
+
+**Restart Claude Code** after installation.
+
+Vector activates automatically. Your rules inject based on prompt keywords. Use MCP tools (`vector_v2_*`) to manage domains and rules at runtime.
+
+---
+
+## Troubleshooting
+
+**Rules not appearing?**
+- Check domain has `"state": "active"` in `vector.json`
+- Verify recall keywords match your prompt
+- Ensure hook path in settings.json is absolute
+- Set `"devmode": true` in vector.json config for debug output
+
+**Hook errors?**
+- Ensure Python 3.9+ is installed and in PATH
+- Check file permissions: `chmod +x ~/.claude/hooks/vector-hook.py`
+
+**MCP not connecting?**
+- Verify `~/.accel/vector/vector-mcp/node_modules/` exists (run `npm install` if not)
+- Check MCP entry in settings.json points to correct absolute path
+- Restart Claude Code after configuration changes

package/modules/vector/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2026 Yogi Gnanavel
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

package/modules/vector/README.md

@@ -0,0 +1,409 @@
+<div align="center">
+
+# Vector
+
+**Context Augmentation & Reinforcement Layer** — Dynamic rules for Claude Code.
+
+[![npm version](https://img.shields.io/npm/v/vector-core?style=for-the-badge&logo=npm&logoColor=white&color=CB3837)](https://www.npmjs.com/package/vector-core)
+[![License](https://img.shields.io/badge/license-MIT-blue?style=for-the-badge)](LICENSE)
+[![GitHub stars](https://img.shields.io/github/stars/accelerationguy/vector?style=for-the-badge&logo=github&color=181717)](https://github.com/accelerationguy/vector)
+
+<br>
+
+```bash
+npx vector-core
+```
+
+**Works on Mac, Windows, and Linux.**
+
+<br>
+
+![Vector Install](assets/terminal.svg?v=3)
+
+<br>
+
+*"Rules that load when relevant, disappear when not."*
+
+<br>
+
+[Why Vector](#why-vector) · [Getting Started](#getting-started) · [How It Works](#how-it-works) · [Core Concepts](#core-concepts) · [MCP Tools](#mcp-tools) · [Migration](#upgrading-from-v1)
+
+</div>
+
+---
+
+## Why Vector
+
+Every Claude Code session starts fresh. Your preferences, workflows, and hard-won lessons? Gone. You end up repeating the same instructions:
+
+> "Use TypeScript strict mode."
+> "Don't over-engineer."
+> "Run tests after changes."
+
+Static prompts in CLAUDE.md work, but they bloat every session — even when irrelevant. Writing code? You don't need your content creation rules. Debugging? You don't need your planning workflow.
+
+Vector fixes this with **just-in-time rule injection**:
+
+1. **Rules load when relevant** — Mention "fix bug" and your development preferences appear
+2. **Rules disappear when not** — Your context stays lean
+3. **Explicit triggers available** — Star-commands (`*commandname`) for on-demand modes
+
+The result: Claude remembers how you work without wasting context on rules you don't need right now.
+
+---
+
+## Who This Is For
+
+**Claude Code users** who want persistent preferences without bloated prompts.
+
+You've figured out what works for you — coding style, response format, workflow patterns. Vector makes those preferences stick:
+
+- Define rules once, use them forever
+- Rules activate automatically based on context
+- Override or extend per-project as needed
+- No manual prompt engineering each session
+
+If you find yourself repeating instructions to Claude, Vector is for you.
+
+---
+
+## Getting Started
+
+```bash
+npx vector-core
+```
+
+The installer prompts you to choose:
+1. **Global** (recommended) — Rules apply to all Claude Code projects (`~/.claude` + `~/.accel/vector`)
+2. **Local** — Rules apply to current project only (`./.claude` + `./.vector`)
+
+**Restart Claude Code after installation.**
+
+### What Gets Installed
+
+```
+~/.accel/vector/
+├── vector.json              # All domains, rules, decisions, config
+├── sessions/              # Session state (auto-managed)
+└── vector-mcp/              # MCP server for runtime management
+    ├── index.js
+    ├── package.json
+    └── tools/
+        ├── vector-json.js   # Domain/rule/decision/config CRUD
+        ├── decisions.js   # Decision logging (v1 compat)
+        ├── domains.js     # Domain management (v1 compat)
+        └── staging.js     # Rule proposal pipeline
+
+~/.claude/
+├── hooks/vector-hook.py     # The injection engine
+└── settings.json          # Hook registration
+
+~/.mcp.json                    # MCP server registration
+```
+
+### Staying Updated
+
+```bash
+npx vector-core@latest
+```
+
+---
+
+## How It Works
+
+```
+You type: "help me fix this bug"
+                │
+                ▼
+    ┌───────────────────────┐
+    │   Vector Hook Scans     │
+    │   Your Prompt         │
+    └───────────────────────┘
+                │
+                ▼
+    ┌───────────────────────┐
+    │  Matches "fix bug"    │
+    │  → DEVELOPMENT domain │
+    └───────────────────────┘
+                │
+                ▼
+    ┌───────────────────────┐
+    │  Injects Your Rules   │
+    │  Into Context         │
+    └───────────────────────┘
+                │
+                ▼
+    Claude responds with your
+    coding preferences baked in
+```
+
+The hook runs on every interaction, reads your `.vector/vector.json`, and injects only the rules that match your current task.
+
+### Architecture (v2)
+
+Everything lives in a single `vector.json` file:
+
+```json
+{
+  "version": 1,
+  "config": {
+    "devmode": false,
+    "context_brackets": { "FRESH": {...}, "MODERATE": {...}, "DEPLETED": {...} },
+    "commands": { "BRIEF": [...], "DISCUSS": [...] }
+  },
+  "domains": {
+    "GLOBAL": { "state": "active", "always_on": true, "rules": [...], "decisions": [...] },
+    "DEVELOPMENT": { "state": "active", "recall": ["fix bug", "write code"], "rules": [...] }
+  },
+  "staging": []
+}
+```
+
+**Key design decisions:**
+- **Single source of truth** — No scattered files. One JSON file holds everything.
+- **MCP for runtime management** — Add rules, log decisions, toggle domains without editing files.
+- **Scope merging** — Project `.vector/` extends global `~/.accel/vector/`. More-specific overrides less-specific.
+- **Context dedup** — Repeated prompts don't re-inject identical rules, saving tokens.
+- **Session management** — Per-session overrides without modifying permanent config.
+
+---
+
+## Core Concepts
+
+### Domains
+
+A domain is a collection of related rules. Create domains for different contexts:
+
+| Example Domain | Trigger Keywords | What It Does |
+|----------------|------------------|--------------|
+| GLOBAL | (always loaded) | Universal preferences |
+| DEVELOPMENT | "fix bug", "write code" | Your coding preferences |
+| CONTENT | "write script", "youtube" | Your content creation style |
+| CLIENTS | "client project", "deliverable" | Project-specific rules |
+
+When your prompt matches a domain's recall keywords, its rules load automatically.
+
+### Star-Commands
+
+Explicit triggers using `*commandname` syntax:
+
+```
+*brief explain recursion
+```
+
+Unlike domains (automatic), star-commands are intentional. Define them in `vector.json` under `config.commands`:
+
+```json
+"commands": {
+  "BRIEF": [
+    "Create a concise session report",
+    "Include: goals, work completed, decisions, next steps"
+  ]
+}
+```
+
+### Context Brackets
+
+Rules that adapt based on remaining context window:
+
+| Bracket | Remaining | Behavior |
+|---------|-----------|----------|
+| FRESH | 70%+ | Lean injection, trust recent context |
+| MODERATE | 40-70% | Reinforce key context |
+| DEPLETED | 15-40% | Heavy reinforcement, checkpoint progress |
+| CRITICAL | <15% | Suggest compaction |
+
+Configured in `vector.json` under `config.context_brackets`.
+
+### Decisions
+
+Log important decisions alongside rules. Decisions are per-domain and injected with relevant rules:
+
+```json
+{
+  "id": "dev-001",
+  "decision": "Use PostgreSQL over SQLite for all new projects",
+  "rationale": "Need concurrent writes and JSON support",
+  "date": "2026-03-15",
+  "recall": ["database", "postgres", "sqlite"]
+}
+```
+
+---
+
+## MCP Tools
+
+Vector includes an MCP server with tools for runtime management. These are available in Claude Code once installed:
+
+### v2 Tools (vector.json)
+
+| Tool | Description |
+|------|-------------|
+| `vector_v2_list_domains` | List all domains with rule/decision counts |
+| `vector_v2_get_domain` | Get full domain config and rules |
+| `vector_v2_create_domain` | Create a new domain with recall keywords |
+| `vector_v2_toggle_domain` | Enable/disable a domain |
+| `vector_v2_add_rule` | Add a rule to a domain |
+| `vector_v2_remove_rule` | Remove a rule by ID |
+| `vector_v2_replace_rules` | Bulk-replace all rules in a domain |
+| `vector_v2_log_decision` | Log a decision to a domain |
+| `vector_v2_search_decisions` | Search decisions by keyword |
+| `vector_v2_archive_decision` | Archive a decision |
+| `vector_v2_stage_proposal` | Stage a rule proposal for review |
+| `vector_v2_get_staged` | List pending proposals |
+| `vector_v2_approve_proposal` | Approve a proposal into a domain |
+| `vector_v2_get_config` | Get Vector config |
+| `vector_v2_update_config` | Update config fields |
+
+---
+
+## Configuration
+
+### Global vs Local
+
+| Location | Scope | Use Case |
+|----------|-------|----------|
+| `~/.accel/vector/` | All projects | Universal preferences |
+| `./.vector/` | Current project | Project-specific rules |
+
+When both exist, project-level domains override global ones. The hook walks up the directory tree, merging scopes from global to local.
+
+### Creating a Domain
+
+Use the MCP tools (Claude will call these for you):
+
+```
+"Create a TESTING domain with recall keywords: run tests, test coverage, write tests"
+```
+
+Or edit `vector.json` directly:
+
+```json
+"TESTING": {
+  "state": "active",
+  "always_on": false,
+  "recall": ["run tests", "test coverage", "write tests"],
+  "exclude": [],
+  "rules": [
+    { "id": 0, "text": "Always run the full test suite after changes", "added": "2026-03-23" }
+  ],
+  "decisions": []
+}
+```
+
+---
+
+## Upgrading from v1
+
+If you have an existing v1 setup (flat files: `manifest`, domain files, `context`, `commands`):
+
+```bash
+# If installed via npm:
+bash node_modules/vector-core/bin/migrate-v1-to-v2.sh --dry-run ~/.accel/vector
+bash node_modules/vector-core/bin/migrate-v1-to-v2.sh ~/.accel/vector
+
+# If cloned from GitHub:
+bash bin/migrate-v1-to-v2.sh --dry-run ~/.accel/vector
+bash bin/migrate-v1-to-v2.sh ~/.accel/vector
+```
+
+The migration tool:
+- Parses all v1 files (manifest, domains, context brackets, star commands, decisions)
+- Generates a complete `vector.json`
+- Archives old files to `.vector/_v1-archive/` (non-destructive)
+- Preserves all rules, decisions, and configuration
+
+---
+
+## Vector + Drive
+
+Vector has a companion: **[Drive](https://github.com/accelerationguy/drive)** (Plan-Apply-Unify Loop).
+
+| Tool | Purpose |
+|------|---------|
+| **Vector** | Dynamic rule injection — how Claude behaves |
+| **Drive** | Structured development workflow — how work flows |
+
+They complement each other:
+
+- Vector loads Drive rules when you're in a `.drive/` project
+- Drive enforces loop integrity (plan, apply, unify)
+- Vector keeps Drive rules out of context when not needed
+
+**Without Vector:** Drive rules would bloat every session.
+**Without Drive:** Complex projects lack structure.
+
+Together: lean context + reliable workflow.
+
+---
+
+## Troubleshooting
+
+**Rules not loading?**
+1. Check domain has `"state": "active"` in vector.json
+2. Verify recall keywords match your prompt
+3. Ensure hook is configured in `~/.claude/settings.json`
+
+**Too many rules loading?**
+1. Make recall keywords more specific
+2. Use exclude to block unwanted matches
+3. Split broad domains into focused ones
+
+**Context dedup active?**
+- Vector skips re-injecting rules when the signature hasn't changed
+- Forces a full re-inject every 5 prompts
+- Override with session config if needed
+
+---
+
+## Ecosystem
+
+Vector is part of a broader Claude Code extension ecosystem:
+
+| System | What It Does | Link |
+|--------|-------------|------|
+| **Radar** | Multi-agent codebase auditing — diagnosis + controlled evolution | [GitHub](https://github.com/accelerationguy/accelerate/tree/main/modules/radar) |
+| **Momentum** | Builder's Automated State Engine — workspace lifecycle, health tracking, drift prevention | [GitHub](https://github.com/accelerationguy/accelerate/tree/main/modules/momentum) |
+| **Vector** | Context Augmentation & Reinforcement Layer — dynamic rules loaded JIT by intent | You are here |
+| **Drive** | Project orchestration — Plan, Apply, Unify Loop | [GitHub](https://github.com/accelerationguy/accelerate/tree/main/modules/drive) |
+| **Ignition** | Typed project incubator — guided ideation through graduation into buildable projects | [GitHub](https://github.com/accelerationguy/accelerate/tree/main/modules/ignition) |
+| **Forge** | Skill builder — standardized syntax specs + guided workflows for Claude Code skills | [GitHub](https://github.com/accelerationguy/accelerate/tree/main/modules/forge) |
+| **Accelerate** | Unified monorepo for all modules | [GitHub](https://github.com/accelerationguy/accelerate) |
+
+---
+
+## Philosophy
+
+### Lean Context
+
+Static prompts waste tokens on irrelevant rules. Vector loads only what's needed. More room for actual work.
+
+### Explicit Over Magic
+
+Vector is transparent. See exactly which domains loaded, know why rules activated. No hidden behavior.
+
+### Your Rules, Your Way
+
+Vector provides structure, not opinions. The default domains are examples — customize or replace them entirely.
+
+---
+
+## License
+
+MIT License. See [LICENSE](LICENSE) for details.
+
+---
+
+## Author
+
+**Yogi Gnanavel** — [Acceleration Guy](https://github.com/accelerationguy)
+
+Building tools for AI-assisted development.
+
+---
+
+<div align="center">
+
+**Claude Code is powerful. Vector makes it personal.**
+
+</div>

package/modules/vector/VECTOR-BLOCK.md

@@ -0,0 +1,57 @@
+# Vector Block for CLAUDE.md
+
+This block must be added to your `CLAUDE.md` (or `~/.claude/CLAUDE.md` for global) for Claude to recognize and follow Vector-injected rules.
+
+## The Block
+
+Add this near the **top** of your CLAUDE.md:
+
+```markdown
+<!-- Vector-MANAGED: Do not remove this section -->
+## Vector Integration
+
+Follow all rules in <vector-rules> blocks from system-reminders.
+These are dynamically injected based on context and MUST be obeyed.
+<!-- END Vector-MANAGED -->
+```
+
+## Why This Is Needed
+
+Claude Code reads CLAUDE.md at session start to understand project context. The Vector block tells Claude:
+
+1. **Look for `<vector-rules>` blocks** — These appear in system-reminders via the hook
+2. **Treat them as instructions** — Rules inside are behavioral directives, not suggestions
+3. **They're dynamic** — Different rules load based on what you're doing
+
+Without this block, Claude may see the injected rules but not understand they're mandatory instructions.
+
+## Placement
+
+Place the block near the top of your CLAUDE.md, after any critical project identity but before detailed instructions. Example structure:
+
+```markdown
+# Project Name
+
+Brief description of the project.
+
+<!-- Vector-MANAGED: Do not remove this section -->
+## Vector Integration
+
+Follow all rules in <vector-rules> blocks from system-reminders.
+These are dynamically injected based on context and MUST be obeyed.
+<!-- END Vector-MANAGED -->
+
+## Other Sections
+...
+```
+
+## Automatic Installation
+
+The `npx vector-core` installer can add this block automatically when you choose that option.
+
+## Manual Verification
+
+To verify Vector is working:
+1. Start a new Claude Code session
+2. Type a message that should trigger a domain (e.g., mention "fix bug" for DEVELOPMENT)
+3. Look for `<vector-rules>` in the response context or enable devmode in manifest