kodelyth-ecc 1.7.3 → 1.7.4

package/videos/video-01-install-and-routing.md

@@ -1,258 +0,0 @@
-# VIDEO 1 — "Install in 60 seconds. Watch it route itself."
-
-**Duration:** 5–7 minutes  
-**Platform:** YouTube (also cut to 60s Reel/Short)  
-**Hook:** Semantic routing demo — no commands typed, AI picks the expert  
-**Goal:** Drive `npx kodelyth-ecc` installs  
-**Screen setup:** Terminal on left, Claude Code / Windsurf on right, dark theme
-
----
-
-## FULL SCRIPT
-
----
-
-### [0:00–0:15] COLD OPEN — No intro, start with the demo
-
-**[SCREEN: Terminal, clean. No intro card yet.]**
-
-**NARRATION (confident, no fluff):**
-> "Watch this."
-
-**[TYPE in terminal:]**
-```
-npx kodelyth-ecc
-```
-
-**[Show the install running — agents copying, skills, commands, hooks]**
-
-**NARRATION:**
-> "That's it. That one command just gave your AI 70 specialist agents, 194 skills, 97 commands, and a self-learning memory system."
-> "Now watch what happens when I use it."
-
-**[Cut to Claude Code / Windsurf chat panel]**
-
-**[TYPE in chat — deliberately vague, emotional:]**
-```
-I've been staring at this NullPointerException for two hours. I'm losing my mind.
-```
-
-**[Show AI response routing automatically:]**
-```
-→ Routing to debug-detective (frustration + error keyword matched)
-```
-
-**NARRATION:**
-> "I never typed a command. I never said 'use debug-detective'. It read what I wrote, picked the right expert, and announced who's taking over."
-> "That's Kodelyth ECC."
-
-**[TITLE CARD: Kodelyth ECC — 70 AI coding agents. One install.]**
-
----
-
-### [0:15–1:00] THE PROBLEM IT SOLVES
-
-**[SCREEN: Split — left side showing a generic "agent kit" readme with 50 agent names]**
-
-**NARRATION:**
-> "Every AI coding toolkit I've used has the same problem."
-> "They hand you a folder of agents and say — good luck."
-> "You have to memorize names. You have to remember which one handles what."
-> "You're doing the routing work yourself."
-
-**[SCREEN: Show a long list of agent names]**
-
-**NARRATION:**
-> "There are 70 agents in ECC. Nobody is going to memorize 70 names."
-> "So I built a routing system that reads your intent — not your commands."
-
----
-
-### [1:00–2:30] THE ROUTING DEMO (core of the video)
-
-**[SCREEN: Claude Code / Windsurf — fresh chat]**
-
-**NARRATION:**
-> "Let me show you the routing in action across five different situations."
-
-**[DEMO 1 — emotional frustration]**
-
-**[TYPE:]**
-```
-I've been fighting this bug for hours, I give up
-```
-
-**[Show response: → Routing to /debug-blitz (frustration + time signal = stubborn bug mode)]**
-
-**NARRATION:**
-> "Frustration signal — routes to debug-blitz. Three debug agents fire in parallel."
-
----
-
-**[DEMO 2 — paste a stack trace with zero text]**
-
-**[TYPE: just paste a raw stack trace, no explanation]**
-
-```
-TypeError: Cannot read properties of undefined (reading 'map')
-    at ProductList (/app/components/ProductList.tsx:24:32)
-    at renderWithHooks (react-dom.development.js:14985:18)
-```
-
-**[Show response: → Routing to debug-detective (naked stack trace = implicit debug request)]**
-
-**NARRATION:**
-> "No text. Just a stack trace. It routes itself."
-
----
-
-**[DEMO 3 — new project intent]**
-
-**[TYPE:]**
-```
-I want to build a SaaS dashboard that tracks user activity
-```
-
-**[Show response: → Routing to /project-launch — 5 agents firing in parallel]**
-
-**NARRATION:**
-> "New build signal. Fires five founding-team agents in parallel — architect, pair-programmer, security-reviewer, tdd-guide, and ux-reviewer."
-> "45 minutes of planning compressed to 10."
-
----
-
-**[DEMO 4 — paste raw code, no context]**
-
-**[TYPE: paste a function with no explanation]**
-
-**[Show response: → Routing to code-reviewer (naked code paste = implicit review)]**
-
-**NARRATION:**
-> "Paste code. No words. Gets reviewed."
-
----
-
-**[DEMO 5 — pre-launch security]**
-
-**[TYPE:]**
-```
-I'm about to go open source, is there anything I should check first?
-```
-
-**[Show response: → Routing to /devil-mode --pre-public (pre-public signal)]**
-
-**NARRATION:**
-> "Pre-public signal. Routes to devil mode — 8 adversarial agents scan your code like an attacker would."
-> "We'll cover that in detail in video 3."
-
----
-
-### [2:30–3:30] THE INSTALL — ALL PLATFORMS
-
-**[SCREEN: Terminal]**
-
-**NARRATION:**
-> "The install is one command. Here's every platform."
-
-**[TYPE and show each:]**
-```bash
-npx kodelyth-ecc                           # Claude Code
-npx kodelyth-ecc --target windsurf-project # Windsurf
-npx kodelyth-ecc --target cursor-project   # Cursor
-npx kodelyth-ecc --target codex-home       # Codex CLI
-npx kodelyth-ecc --target antigravity      # Google Antigravity
-npx kodelyth-ecc --target cline            # Cline (VS Code)
-npx kodelyth-ecc --target roocode          # Roo Code
-npx kodelyth-ecc --target aider            # Aider
-```
-
-**NARRATION:**
-> "11 platforms. 13 install targets. Same command, different flag."
-> "Windows? PowerShell install script ships in the package."
-> "No account. No API key. No cloud. Just files on your disk."
-
----
-
-### [3:30–4:30] THE MEMORY TEASER
-
-**[SCREEN: New terminal window]**
-
-**NARRATION:**
-> "Here's the part that surprises people."
-
-**[TYPE:]**
-```
-npx kodelyth-ecc dashboard
-```
-
-**[Browser opens at http://127.0.0.1:5747]**
-
-**[Show the Memory tab]**
-
-**NARRATION:**
-> "This is your local memory store. Every time you solve a hard problem, ECC can remember the approach."
-> "Next session — new project, five months later — when you describe something similar, it recalls the exact pattern before you ask."
-
-**[Show the search box, type "stripe webhook", show results]**
-
-**NARRATION:**
-> "BM25 search. Local. No embeddings. No cloud. Sub-millisecond."
-> "This compounds over time. The longer you use it, the smarter your AI gets."
-
----
-
-### [4:30–5:15] WHAT ELSE IS IN THE BOX
-
-**[SCREEN: Quick scrollthrough of agents/ directory, then commands/]**
-
-**NARRATION:**
-> "70 agents. Here's a taste of what's in there."
-
-**[QUICK CUTS — each 3–4 seconds with agent name on screen:]**
-
-- `debug-detective` — root cause, never guesses
-- `security-reviewer` — auth, input validation, secrets
-- `incident-commander` — production is down, P0 response
-- `load-tester` — k6, Locust, capacity planning
-- `migration-guide` — framework upgrades, phase by phase
-- `release-captain` — semver, tagging, rollback plan
-- `image-architect` — AI image gen, Gemini / DALL-E / SVG
-- `api-guardian` — breaking API contract detection
-- `ux-reviewer` — WCAG 2.1, accessibility, interaction patterns
-
-**NARRATION:**
-> "And 8 adversarial devil-mode agents for when you need to think like an attacker."
-> "Everything has a playbook. Everything has severity calibration. These aren't personas — they have real bash patterns and remediation steps."
-
----
-
-### [5:15–5:45] CTA
-
-**[SCREEN: Terminal]**
-
-**NARRATION:**
-> "One command."
-
-**[TYPE:]**
-```
-npx kodelyth-ecc
-```
-
-**NARRATION:**
-> "Link in the description — github.com/sifxprime/kodelyth-ecc"
-> "Next video: the compound memory system — how your AI remembers across projects and why that's different from anything else."
-> "Subscribe if you want to see that."
-
-**[END CARD: github link, npm link, subscribe button]**
-
----
-
-## B-ROLL / EDITING NOTES
-
-- All terminal footage: dark theme (Dracula or Catppuccin Mocha)
-- Font: JetBrains Mono or Fira Code, 16–18px
-- Show actual routing responses — don't fake them
-- Routing transitions: small flash/pulse animation on the `→ Routing to` line
-- Dashboard footage: real localhost session, not mockup
-- Cut music: low synth, no distraction, something like "lo-fi coding" on YT audio library
-- Thumbnail: terminal + "70 agents. 1 command." in bold + routing arrow graphic

package/videos/video-02-compound-memory.md

@@ -1,301 +0,0 @@
-# VIDEO 2 — "How the compound memory works"
-
-**Duration:** 8–10 minutes  
-**Platform:** YouTube (technical audience — engineers who care about architecture)  
-**Hook:** "Your AI has no memory. But yours does."  
-**Goal:** Drive installs + explain the unique differentiator  
-**Screen setup:** Terminal + code editor + browser (dashboard)
-
----
-
-## FULL SCRIPT
-
----
-
-### [0:00–0:20] COLD OPEN
-
-**[SCREEN: Two Claude Code sessions side by side — one with blank context, one with a memory recall injection]**
-
-**NARRATION:**
-> "This is your AI without memory."
-> "And this is your AI with Kodelyth ECC's compound memory."
-
-**[Left: clean AI asks basic questions about your stack]**
-**[Right: AI opens with — "I checked your memory — you've solved a similar Stripe webhook issue before. Raw body parser before signature validation. Want me to apply that?"]**
-
-**NARRATION:**
-> "Same model. Different context. Completely different output."
-> "Let me show you how this works — and why it compounds over time."
-
-**[TITLE CARD: Kodelyth ECC — Compound Memory Architecture]**
-
----
-
-### [0:20–1:30] THE PROBLEM: AI HAS NO MEMORY
-
-**[SCREEN: Simple diagram — each AI session as an isolated bubble]**
-
-**NARRATION:**
-> "Here's the fundamental problem with AI coding tools."
-> "Every session is a blank slate."
-
-**[Draw/animate: session 1 bubble, session 2 bubble, session 3 — completely disconnected]**
-
-**NARRATION:**
-> "You solve a hard problem Monday. You close the chat. Tuesday — it's gone."
-> "You join a new project three months later. You hit the same bug pattern you fixed before. You debug it from scratch. Again."
-
-**[SCREEN: Typing the same question again]**
-
-**NARRATION:**
-> "This isn't a model problem. The models are brilliant. It's a context problem."
-> "The model never knew about that fix. You never told it."
-> "ECC closes that loop automatically."
-
----
-
-### [1:30–3:00] THE THREE LAYERS
-
-**[SCREEN: Diagram — three stacked layers]**
-
-**NARRATION:**
-> "ECC's compound memory has three layers. Each one is independent. Together they stack."
-
-**[LAYER 1 — Project Lessons]**
-
-**[Show: tasks/lessons.md in code editor]**
-
-**NARRATION:**
-> "Layer one: tasks/lessons.md — your project's permanent rulebook."
-> "Every time you correct the AI — 'use pnpm not npm', 'never add try/catch without logging', 'we use Zod not Yup' — a hook at the end of the session extracts that correction and writes it here."
-
-**[SCREEN: Show correction being typed in chat → session ends → lessons.md showing new rule]**
-
-**NARRATION:**
-> "Next session starts — this file is injected before the first message. The AI already knows your rules. You never repeat yourself."
-
-**[SCREEN: Show lessons.md growing over time — week 1, month 1, month 3]**
-
-**NARRATION:**
-> "It compounds. Month one: 5 rules. Month three: 30 rules. The AI knows your tech stack, naming style, patterns you hate, tools you prefer. Zero ramp-up on every new task."
-
----
-
-**[LAYER 2 — Global BM25 Memory]**
-
-**[SCREEN: ~/.kodelyth/memory/ in terminal]**
-
-**NARRATION:**
-> "Layer two: global memory. Stored at ~/.kodelyth/memory/. BM25 full-text search."
-
-**[SCREEN: Show memories.jsonl file, then show dashboard Memory tab]**
-
-**NARRATION:**
-> "BM25 is the algorithm that powers early Google. Keyword weighting, term frequency, document frequency. Pure math — no embeddings, no neural network, no API calls."
-> "Sub-millisecond recall. Zero dependencies. Works offline."
-
-**[SCREEN: Show capture flow — problem/approach/tags format]**
-
-**NARRATION:**
-> "When you capture a memory, it stores: problem statement, approach that worked, gotchas, tags, language, project."
-
-**[SCREEN: Show recall in action — type in dashboard search, results appear]**
-
-**NARRATION:**
-> "When you start a new session or type a prompt, ECC searches this store and injects relevant matches before your AI responds."
-> "It's like your AI checked your notes first."
-
----
-
-**[LAYER 3 — Auto Chat Recall]**
-
-**[SCREEN: Diagram showing UserPromptSubmit hook intercepting messages]**
-
-**NARRATION:**
-> "Layer three: auto chat recall. This one is invisible — which is why it's powerful."
-> "Every message you type goes through a BM25 search before the AI sees it. If there's a relevant past memory, it's injected into the context automatically."
-> "You just type normally. The recall happens in the background."
-
-**[SCREEN: Terminal showing hook fires, memory injected, then AI response includes "based on your previous work..."]**
-
-**NARRATION:**
-> "Per-session repeat suppression — the same memory won't be injected twice in one session. Clean, no noise."
-
----
-
-### [3:00–4:30] LIVE DEMO — THE FULL LOOP
-
-**[SCREEN: Terminal + Claude Code]**
-
-**NARRATION:**
-> "Let me show you the full loop. We're going to capture a solution, then recall it five minutes later in a fresh session."
-
-**[STEP 1: Session 1 — solve a problem]**
-
-**[TYPE in chat:]**
-```
-My Stripe webhook keeps returning 400 - invalid signature
-```
-
-**[Show AI helping solve it — raw body parser issue]**
-
-**[STEP 2: Capture the memory]**
-
-**[TYPE in chat:]**
-```
-/memory remember "Stripe webhook signature validation"
-```
-
-**[Show capture confirmation — problem/approach/tags saved]**
-
-**NARRATION:**
-> "Captured. Stored at ~/.kodelyth/memory/memories.jsonl. Let me show you exactly what got saved."
-
-**[Open terminal:]**
-```bash
-tail -1 ~/.kodelyth/memory/memories.jsonl | jq .
-```
-
-**[Show JSON output with problem, approach, tags, language]**
-
----
-
-**[STEP 3: New session — fresh context]**
-
-**[Close Claude Code, reopen, fresh chat]**
-
-**[TYPE:]**
-```
-I need to add Stripe webhooks to my checkout flow
-```
-
-**[Show response — memory injected at the top:]**
-```
-I checked your memory — you solved a similar problem before:
-
-"Stripe webhook signature validation" (captured 2 min ago)
-→ Raw body parser must come before express.json() middleware
-→ Use stripe.webhooks.constructEvent() not manual sig parsing
-→ Test with stripe-cli forward, not curl
-
-Want me to apply this exact pattern?
-```
-
-**NARRATION:**
-> "Same session, different project. It recalled the fix before you even described the bug."
-> "In real usage, this gap is months. And the value compounds every session."
-
----
-
-### [4:30–6:00] THE COST WIN — PROMPT CACHE
-
-**[SCREEN: Diagram — token costs, cache zone]**
-
-**NARRATION:**
-> "There's a financial angle to this that most people miss."
-
-**[Show Anthropic pricing: 3$/M input, 0.30$/M cached]**
-
-**NARRATION:**
-> "Anthropic charges 10% for cached tokens. OpenAI auto-caches prefixes over 1024 tokens."
-> "ECC's memory injection is designed as a stable prefix. The same content, in the same order, session after session."
-> "That prefix hits the cache. Every long session, the repeated context is 90% cheaper."
-
-**[SCREEN: Show example — 50,000 token session, 15,000 cached prefix]**
-
-**NARRATION:**
-> "If you do heavy AI coding sessions — hours per day — this adds up to real money over a month."
-
----
-
-### [6:00–7:30] THE SELF-EVOLVING MEMORY (EVOLVE TAB)
-
-**[SCREEN: Dashboard → Evolve tab]**
-
-**NARRATION:**
-> "The memory system also closes its own learning loop."
-
-**[Show evolve tab with pending proposals]**
-
-**NARRATION:**
-> "ECC tracks which memories get recalled most often. When a pattern repeats enough times, it proposes a new skill — a permanent knowledge file that the AI uses on every relevant session."
-
-**[Show a proposal in the dashboard — pending status]**
-
-**NARRATION:**
-> "Nothing is ever auto-applied. You review, accept, edit, then commit."
-> "That's the design principle: the system proposes. You decide."
-
-**[Show CLI:]**
-```bash
-npx kodelyth-ecc evolve analyze
-npx kodelyth-ecc evolve list
-npx kodelyth-ecc evolve show <id>
-npx kodelyth-ecc evolve accept <id>
-```
-
-**NARRATION:**
-> "The evolve CLI is your interface to the proposal pipeline."
-
----
-
-### [7:30–8:30] PRIVACY — EVERYTHING LOCAL
-
-**[SCREEN: Terminal]**
-
-**NARRATION:**
-> "One thing I want to be explicit about."
-
-**[TYPE:]**
-```bash
-ls -la ~/.kodelyth/memory/
-```
-
-**[Show the files — memories.jsonl, indexes]**
-
-**NARRATION:**
-> "That's everything. A JSONL file on your disk."
-> "No API call leaves your machine for memory operations. No server. No account. No sync unless you set it up yourself."
-
-**[TYPE:]**
-```bash
-npx kodelyth-ecc verify
-```
-
-**[Show sha256 manifest verification running]**
-
-**NARRATION:**
-> "You can verify the entire installed toolkit against a sha256 manifest any time. Every file, every agent, every hook — verifiable."
-
----
-
-### [8:30–9:00] CTA
-
-**NARRATION:**
-> "The memory layer is what makes ECC different from every other toolkit."
-> "It's not a feature you toggle on. It's infrastructure that builds over time and saves you real hours."
-
-**[SCREEN: npm install command]**
-
-**[TYPE:]**
-```
-npx kodelyth-ecc
-```
-
-**NARRATION:**
-> "github.com/sifxprime/kodelyth-ecc — link in description."
-> "Next video: Devil Mode. 8 adversarial agents that read your code like an attacker. I'll show you what they find on a real project."
-
-**[END CARD: subscribe, next video preview, github link]**
-
----
-
-## B-ROLL / EDITING NOTES
-
-- Animate the three-layer diagram with Figma or simple CSS animation
-- Show REAL `memories.jsonl` content (blur personal project names if needed)
-- The BM25 recall response must be real — test it, record it
-- Dashboard footage: real session on localhost:5747
-- Show the `jq` pipe — this builds technical credibility
-- Music: same lo-fi track as Video 1 for consistency
-- Thumbnail: "Your AI remembered. 5 months later. Different project." + memory icon