adaptive-memory-multi-model-router 2.14.46 → 2.14.47

package/HEALTH_REPORT.md

@@ -1,118 +0,0 @@
-# A3M Router — Health Report
-
-**Generated:** 2026-05-28  
-**Branch:** `main`  
-**npm version:** 2.13.22  
-**Latest release:** v2.13.20 "SEO fixes, homepage URL, 15 awesome PRs"
-
----
-
-## 1. Awesome-List Submissions (15 issues)
-
-| # | Repo | Issue | State | Comments | Notes |
-|---|------|-------|-------|----------|-------|
-| 1 | 12britz/awesome-ai-gateways | #6 | OPEN | 0 | |
-| 2 | wauputr4/awesome-llm-gateways | #1 | OPEN | 1 | Author responded to review |
-| 3 | pyxis3-ai/awesome-model-agnostic-llm | #2 | OPEN | 0 | |
-| 4 | mahseema/awesome-ai-tools | #1404 | OPEN | 0 | |
-| 5 | ai-for-developers/awesome-ai-coding-tools | #358 | OPEN | 0 | |
-| 6 | WangRongsheng/awesome-LLM-resources | #125 | OPEN | 0 | |
-| 7 | tensorchord/Awesome-LLMOps | #523 | OPEN | 0 | |
-| 8 | Hannibal046/Awesome-LLM | #611 | OPEN | 0 | |
-| 9 | RunaCapital/awesome-oss-alternatives | #352 | OPEN | 0 | Label: enhancement |
-| 10 | AiHubCN/Awesome-Chinese-LLM | #101 | OPEN | 0 | |
-| 11 | jamesmurdza/awesome-ai-devtools | #584 | **CLOSED** | 1 | Rejected — missing PR template checklist items (auto-closed by bot) |
-| 12 | EthicalML/awesome-production-machine-learning | #778 | OPEN | 0 | |
-| 13 | reorx/awesome-chatgpt-api | #158 | OPEN | 0 | |
-| 14 | Not-Diamond/awesome-ai-model-routing | #15 | OPEN | 0 | |
-| 15 | filipecalegario/awesome-generative-ai | #536 | OPEN | 0 | |
-
-**Summary:** 14/15 OPEN, 1 CLOSED (template violation). Only 1 has any reviewer comments (wauputr4). No repo maintainer has merged any entry yet. The closed one (awesome-ai-devtools) can be reopened if the PR description is fixed to match their template.
-
----
-
-## 2. CI / GitHub Actions
-
-| Workflow | Status | Latest Run |
-|----------|--------|------------|
-| CI | success | 2026-05-28T04:25:34Z |
-| Deploy Pages | success | 2026-05-28T04:25:34Z |
-| CodeQL | success | 2026-05-28T04:25:34Z |
-| pages-build-deployment | success | 2026-05-28T04:25:32Z |
-| stale.yml | **failure** | 2026-05-28T04:25:33Z |
-
-**Stale.yml failure:** The `actions/stale` workflow fails consistently. Root cause: `exempt-issue-labels` and `exempt-pr-labels` are defined **twice** in the config (duplicate keys). GitHub Actions treats duplicate YAML keys as an error. Fix: deduplicate the labels into one `exempt-issue-labels` and one `exempt-pr-labels` entry.
-
----
-
-## 3. npm Package Metadata
-
-| Field | Value |
-|-------|-------|
-| **Package** | `adaptive-memory-multi-model-router` |
-| **Version** | `2.13.22` |
-| **Homepage** | `https://das-rebel.github.io/a3m-router/` |
-| **Repository** | `git+https://github.com/Das-rebel/a3m-router.git` |
-| **License** | MIT |
-| **Engine** | Node >= 18.0.0 |
-| **Keywords** | 54 keywords (ai-gateway, llm-router, parallel-llm, ensemble-voting, etc.) |
-| **Binaries** | a3m-router, a3m, a3m-tui, adaptive-memory-multi-model-router |
-| **Types** | Not set (missing from package.json) |
-| **Weekly Downloads** | **5,369** (last week) — Top 0.2% of npm |
-| **Total Downloads** | ~10,024 in 14 days |
-
-- `types` field is missing from package.json — consumers using TypeScript won't get automatic type resolution.
-- Package name may be too long for convenience; the shorter CLI aliases (`a3m`, `a3m-router`) help.
-
----
-
-## 4. GitHub Pages
-
-| Check | Status |
-|-------|--------|
-| HTTPS | OK (200) |
-| Content-Type | text/html |
-| Size | 19,847 bytes |
-| Last-Modified | 2026-05-28 (today) |
-| Deploy Workflow | Success on latest run |
-
-**Page is healthy and serving content.**
-
----
-
-## 5. GitHub Releases
-
-| Tag | Date | Notes |
-|-----|------|-------|
-| v2.13.20 | 2026-05-28 | **Latest** — SEO fixes, homepage URL, 15 awesome PRs |
-| v2.13.18 | 2026-05-27 | 54 npm keywords + HF Space ready |
-| v2.14.0 | 2026-05-27 | 10K downloads in 14 days |
-| v2.13.3 | 2026-05-26 | Parallel Multi-LLM Execution with Intelligent Merge |
-
----
-
-## 6. Action Items
-
-### Critical
-1. **Fix stale.yml** — Duplicate `exempt-issue-labels`/`exempt-pr-labels` keys cause workflow failure. Merge into single definitions.
-2. **Add `types` to package.json** — Currently missing, breaking automatic TypeScript type resolution for consumers.
-
-### Medium
-3. **Reopen awesome-ai-devtools PR (#584)** — Edit description to match PR template and re-open. This repo has 2.9K+ visibility.
-4. **Check on wauputr4 review** — The only repo with active reviewer feedback. Respond to their comments if any remain.
-
-### Low
-5. **Track remaining 14 open submissions** — None have been merged yet. May need follow-up nudges or format adjustments per each repo's rules.
-
----
-
-## 7. Overall Health Score
-
-| Category | Score | Notes |
-|----------|-------|-------|
-| CI/CD | 80% | stale.yml broken, others green |
-| npm Package | 85% | Missing `types` field |
-| GitHub Pages | 100% | Healthy |
-| Submissions | 93% | 14/15 open, none merged yet |
-| Releases | 100% | Regular cadence |
-| **Overall** | **88%** | Good — 2 quick fixes needed |

package/IMPROVEMENT_PLAN.md

@@ -1,107 +0,0 @@
-# A3M Router Improvement Plan: Target 80% Accuracy
-
-## Current State (Local Benchmark v2.14.26)
-- **Overall Accuracy**: 67% (134/200)
-- **Target**: 80% (160/200)
-- **Gap**: +26 correct answers needed
-
-## Problem Areas
-
-### 1. MID Tier: 36% → Need 70%
-- **Current**: 18/50 correct
-- **Problem**: 22 queries under-routed to CHEAP, 9 over-routed to PREMIUM
-- **Impact**: +17 potential correct
-
-### 2. PREMIUM Tier: 58% → Need 75%  
-- **Current**: 23/40 correct
-- **Problem**: 11 queries under-routed to MID, 4 to CHEAP, 2 to FREE
-- **Impact**: +9 potential correct
-
-### 3. CHEAP Tier: 75% → Keep at 80%+
-- **Current**: 45/60 correct (13 under-routed to FREE)
-
-## Root Cause Analysis
-
-The router uses a single "complexity" score (0-1) to route queries. The problem:
-
-1. **MID queries scored too low** → routed to CHEAP (44% error rate)
-2. **PREMIUM queries scored too low** → routed to MID/CHEAP (30% error rate)
-
-### Current Complexity Signal Weights
-- Word count: up to 0.35
-- Jargon: up to 0.35
-- Formality: up to 0.19
-- Depth indicators: up to 0.17
-- Stakes indicators: up to 0.12
-- Multi-step: up to 0.11
-- Domain detection: up to 0.35
-- Code detection: +0.15
-- Reasoning detection: +0.20
-- Multilingual: +0.10
-
-**Problem**: These signals don't differentiate enough between CHEAP and MID/PREMIUM tiers.
-
-## Proposed Signal Improvements
-
-### A. MID Tier Detection Signals (Priority 1)
-
-**Add these to complexity score:**
-1. **Technical depth markers** (+0.15): "implement", "architecture", "system design", "optimize", "performance"
-2. **Analysis requirements** (+0.12): "compare and contrast", "evaluate", "assess", "analyze the tradeoffs"
-3. **Multi-conceptual** (+0.10): Queries mentioning 3+ concepts that need to be connected
-4. **Specific domain expertise** (+0.08): Medical, legal, financial, security terminology
-
-### B. PREMIUM Tier Detection Signals (Priority 2)
-
-**Add these to complexity score:**
-1. **Advanced reasoning** (+0.20): "prove that", "derive", "synthesize", "create a new approach"
-2. **Multi-modal requirements** (+0.15): Code + data + explanation needs
-3. **Novel generation** (+0.15): "write a story", "generate code", "create a solution"
-4. **High-stakes context** (+0.12): Decisions with significant consequences
-
-### C. Calibration Fixes
-
-1. **Don't route to FREE** if:
-   - Query has any technical terms
-   - Query length > 75 words
-   - Query asks for explanation/analysis
-
-2. **Don't route to CHEAP** if:
-   - Query has 2+ mid-tier indicators
-   - Domain is medical/legal/financial/security
-
-3. **Route to PREMIUM** if:
-   - Query explicitly asks for reasoning chain
-   - Query is about system architecture
-   - Query requires code generation AND explanation
-
-## Implementation Order
-
-### Phase 1: Fix MID→CHEAP under-routing
-- Add mid-tier specific signals
-- Recalibrate complexity thresholds
-- Target: MID tier 36% → 60%
-
-### Phase 2: Fix PREMIUM under-routing  
-- Add premium-tier specific signals
-- Target: PREMIUM tier 58% → 75%
-
-### Phase 3: Protect CHEAP tier
-- Ensure CHEAP queries don't leak to FREE
-- Target: Keep CHEAP at 75%+
-
-## Expected Results
-
-| Tier | Current | Phase 1 | Phase 2 | Final |
-|------|---------|---------|---------|-------|
-| FREE | 96% | 96% | 96% | 96% |
-| CHEAP | 75% | 70% | 70% | 80% |
-| MID | 36% | 60% | 65% | 70% |
-| PREMIUM | 58% | 58% | 75% | 75% |
-| **Overall** | **67%** | **70%** | **76%** | **80%** |
-
-## Testing Strategy
-
-1. Run local benchmark after each change
-2. Only submit to RouterArena when local benchmark shows 80%+
-3. Use RouterArena validation as final check, not development tool

package/LANDING.md

@@ -1,43 +0,0 @@
-# A3M Router — Parallel Multi-LLM Execution with Intelligent Merge
-
-*One prompt. All providers. The best answer.*
-
----
-
-## What It Is
-
-A routing layer between your app and every LLM provider. Routes every query to the cheapest capable model, runs multiple providers in parallel when quality matters, and scores results to return the best answer.
-
-## What It Does
-
-- **Parallel ensemble** — Runs NVIDIA + Groq + OpenAI simultaneously, scores results, picks best
-- **Smart routing** — 12 heuristic signals classify query complexity, routes to cheapest capable model
-- **Cost control** — Hard per-user/team budgets with real-time tracking and alerts
-- **Fault tolerance** — Circuit breaker, automatic failover, exponential backoff with jitter
-- **Memory persistence** — Cross-session episodic memory with keyword indexing
-
-## By the Numbers
-
-| Metric | Result |
-|--------|--------|
-| Routing Accuracy | **70.32**  |
-| Cost Savings | **62%** vs all-premium |
-| Providers | **47+** |
-| Cache Hit Rate | **30%+** |
-| Size | **19.5 KB** |
-| Startup | **<100ms** |
-
-## Start in 30 Seconds
-
-```bash
-npm install adaptive-memory-multi-model-router
-npx a3m-router serve                    # OpenAI proxy at localhost:8787
-npx a3m-router route "What is 2+2?"    # Routing decision
-npx a3m-router compare "Explain AI"    # All providers side-by-side
-```
-
-Point any OpenAI-compatible client to `http://localhost:8787` with `model: "auto"`.
-
----
-
-*A3M Router. Parallel multi-LLM execution with result merging.*

package/LAUNCH-PAIN-DRIVEN.md

@@ -1,339 +0,0 @@
-# 🚀 PAIN-DRIVEN LAUNCH MANIFEST
-
-## The Strategy: Pain → Agitate → Solution → Transformation
-
-**OLD APPROACH**: "Here's a cool feature we built"
-**NEW APPROACH**: "Your OpenAI bill is 3x higher than it should be (here's the fix)"
-
----
-
-## 📰 CONTENT READY TO POST
-
-### 1. DEV.TO (Highest Priority)
-**File**: `articles/PAIN-DRIVEN-devto.md`
-
-**URL**: https://dev.to/new
-
-**Title**: 
-```
-Your OpenAI Bill is 3x Higher Than It Should Be (Here's the Fix)
-```
-
-**Hook**: "Last month, our startup's OpenAI bill hit $2,400."
-
-**Pain**: Using GPT-4 for everything = paying premium for basic tasks
-
-**Agitation**: CFO ultimatum, 40% of infrastructure budget
-
-**Solution**: A3M Router with intelligent query analysis
-
-**Transformation**: $2,400 → $720/month (70% savings)
-
-**Copy & paste the entire file content**
-
----
-
-### 2. HACKER NEWS (Highest Priority)
-**File**: `articles/PAIN-DRIVEN-hackernews.md`
-
-**URL**: https://news.ycombinator.com/submit
-
-**Title**: 
-```
-Show HN: I cut our OpenAI bill by 70% with intelligent LLM routing
-```
-
-**Hook**: "$2,400 OpenAI bill, 5-person team, 1,000 queries/day"
-
-**Key Stats Table**: Before/After comparison
-
-**Copy & paste the entire file content**
-
-**Best Time**: Tuesday-Thursday, 9-11am PST
-
----
-
-### 3. TWITTER THREAD (Highest Priority)
-**File**: `articles/PAIN-DRIVEN-twitter.md`
-
-**URL**: https://twitter.com/compose/tweet
-
-**Hook (Tweet 1)**: 
-```
-Our OpenAI bill hit $2,400 last month.
-
-We're 5 people. 1,000 queries/day. Customer support, code gen, summarization.
-
-Nothing that should cost $2,400.
-
-Here's why we were overpaying by 70% 🧵
-```
-
-**Copy all 10 tweets and post as thread**
-
-**Pin to profile for 1 week**
-
----
-
-### 4. REDDIT r/MachineLearning (High Priority)
-**File**: `articles/PAIN-DRIVEN-reddit.md`
-
-**URL**: https://www.reddit.com/r/MachineLearning/submit
-
-**Title**: 
-```
-[P] We cut our LLM API costs by 70% with learned routing - here's how
-```
-
-**Focus**: Research approach, methodology, results
-
-**Copy & paste the entire file content**
-
-**Flair**: `Project`
-
----
-
-### 5. REDDIT r/javascript (High Priority)
-**URL**: https://www.reddit.com/r/javascript/submit
-
-**Title**: 
-```
-I was paying $2,400/month for OpenAI API calls. Built a router that cut it to $720.
-```
-
-**Content**:
-```
-Hey r/javascript,
-
-Last month our startup's OpenAI bill hit $2,400. We're 5 people processing ~1,000 LLM queries per day.
-
-I looked at our logs:
-• 34% simple Q&A (any model works)
-• 28% code generation (speed > perfection)
-• 22% summarization (doesn't need GPT-4)
-• 16% actually needs high-quality reasoning
-
-We were paying GPT-4 prices for 84% of queries that didn't need it.
-
-So I built A3M Router - it analyzes each query and routes to the cheapest capable provider:
-
-```javascript
-const { routeQuery } = require('adaptive-memory-multi-model-router');
-
-// Simple query → FREE provider
-routeQuery("What is 2+2?"); // → commandcode/taste-1 ($0.00)
-
-// Code query → FAST provider  
-routeQuery("Write Python to reverse a string"); 
-// → groq/llama-3.3-70b ($0.0004, 5x faster)
-```
-
-Results after 30 days:
-• Before: $2,400/month
-• After: $720/month
-• Savings: 70%
-• Speed: 2x faster
-• Quality: 94% (vs 100% GPT-4)
-
-Trade-off: 6% quality for 70% savings. Worth it.
-
-If your OpenAI bill is >$500/month, you're probably overpaying.
-
-Try it:
-```bash
-npm install adaptive-memory-multi-model-router
-npx a3m-router route "Your query"
-```
-
-GitHub: https://github.com/Das-rebel/a3m-router
-
-What's your current LLM spend?
-```
-
----
-
-## 🎯 POSTING SEQUENCE
-
-### TODAY (Do in this order)
-
-**Hour 1: Twitter**
-- Post thread from `PAIN-DRIVEN-twitter.md`
-- Pin to profile
-- Reply to any responses immediately
-
-**Hour 2: Hacker News**
-- Post from `PAIN-DRIVEN-hackernews.md`
-- Monitor comments for 2 hours
-- Respond to technical questions
-
-**Hour 3: Dev.to**
-- Post from `PAIN-DRIVEN-devto.md`
-- Share link on Twitter
-- Submit to JavaScript Weekly newsletter
-
-**Hour 4: Reddit**
-- Post to r/MachineLearning
-- Post to r/javascript
-- Monitor and respond
-
-### THIS WEEK
-
-**Day 2-3**: 
-- Hashnode article (adapt from Dev.to)
-- Medium article (adapt from Dev.to)
-- IndieHackers post
-
-**Day 4-5**:
-- Product Hunt prep (schedule for next Tuesday)
-- YouTube script recording
-- Demo GIF creation
-
-**Day 6-7**:
-- Monitor all posts
-- Respond to comments
-- Track metrics
-- Iterate based on feedback
-
----
-
-## 📊 EXPECTED RESULTS (Pain-Driven Approach)
-
-### Why Pain-Driven Works Better
-
-| Approach | Engagement | Conversion | Shares |
-|----------|-----------|------------|--------|
-| Feature-focused | Low | 0.5% | Rare |
-| **Pain-driven** | **High** | **3-5%** | **Common** |
-
-### Projected Impact
-
-**Week 1**:
-- HN: 100-300 upvotes (pain resonates)
-- Twitter: 20-50k impressions (relatable problem)
-- Reddit: 50-200 upvotes per post
-- Dev.to: 1,000-5,000 views
-- **Result**: 1,000-2,000 GitHub stars
-
-**Month 1**:
-- 5,000-10,000 daily NPM downloads
-- 3,000-5,000 GitHub stars
-- GitHub Trending feature
-- Newsletter mentions
-
----
-
-## 💬 RESPONSE TEMPLATES
-
-### When Someone Says "This is exactly what I needed"
-
-> "Thanks! What was your biggest pain point - cost, speed, or something else?"
-
-### When Someone Asks About Quality
-
-> "We tracked 1,000 test queries. Overall quality: 94% vs 100% GPT-4. Trade-off: 6% quality for 70% savings. For our use case (customer support, code gen), totally worth it."
-
-### When Someone Asks About Setup
-
-> "Literally 10 minutes:
-> ```bash
-> npm install adaptive-memory-multi-model-router
-> ```
-> Then replace your OpenAI calls with `router.route()`. That's it."
-
-### When Someone Shares Their Bill
-
-> "Ouch! Based on your volume, you could probably save $X/month. Want me to run the numbers?"
-
-### When Someone Criticizes Quality Trade-off
-
-> "Fair point! For medical/legal use cases, you might want 100% quality. But for customer support, internal tools, code generation - 94% at 30% cost is a no-brainer."
-
----
-
-## 📈 TRACKING
-
-### Metrics to Watch
-
-**Engagement**:
-- HN upvotes/comments
-- Twitter impressions/engagement
-- Reddit upvotes/comments
-- Dev.to views/reactions
-
-**Conversion**:
-- GitHub stars (target: 1,000 week 1)
-- NPM downloads (target: 2,000/day week 1)
-- Playground usage
-- Issue/PR creation
-
-**Sentiment**:
-- Positive vs negative comments
-- Feature requests
-- Bug reports
-
-### Tools
-
-- HN: https://hn.algolia.com/?q=a3m+router
-- Twitter: https://analytics.twitter.com/
-- Reddit: Post notifications
-- NPM: https://npm-stat.com/
-- GitHub: https://github.com/Das-rebel/a3m-router/graphs/traffic
-
----
-
-## 🚀 LAUNCH MESSAGE (Use Everywhere)
-
-```
-🚀 A3M Router is LIVE!
-
-Your OpenAI bill is probably 3x higher than it should be.
-
-We were paying $2,400/month. Cut it to $720 with intelligent routing.
-
-✨ Automatic query analysis
-💰 50-80% cost reduction  
-⚡ 2x faster responses
-🔄 Smart fallback
-📊 Real-time cost tracking
-
-npm install adaptive-memory-multi-model-router
-
-GitHub: github.com/Das-rebel/a3m-router
-
-Try the playground: [link]
-
-What's your current LLM spend? 👇
-```
-
----
-
-## ✅ FINAL CHECKLIST
-
-**Content Ready**:
-- [x] Dev.to (pain-driven)
-- [x] Hacker News (pain-driven)
-- [x] Twitter thread (pain-driven)
-- [x] Reddit ML (pain-driven)
-- [x] Reddit JS (pain-driven)
-
-**Assets Ready**:
-- [x] GitHub optimized
-- [x] README with pain points
-- [x] Playgrounds live
-- [x] Demo script ready
-
-**Posting Plan**:
-- [ ] Hour 1: Twitter
-- [ ] Hour 2: Hacker News
-- [ ] Hour 3: Dev.to
-- [ ] Hour 4: Reddit
-- [ ] Day 2-3: Hashnode, Medium, IndieHackers
-- [ ] Day 4-5: Product Hunt prep
-
-**READY TO LAUNCH! 🚀**
-
----
-
-**All pain-driven content is in `articles/PAIN-DRIVEN-*.md` files.**
-
-**Copy, paste, post. Watch the engagement roll in.**