Skip to content

fix: revert to knowledge layer positioning, add cold-start framing#22

Merged
rushikeshmore merged 1 commit intomainfrom
v0.5.0-knowledge-layer
Mar 8, 2026
Merged

fix: revert to knowledge layer positioning, add cold-start framing#22
rushikeshmore merged 1 commit intomainfrom
v0.5.0-knowledge-layer

Conversation

@rushikeshmore
Copy link
Owner

Summary

  • Reverts "navigation and risk layer" → "persistent codebase knowledge layer"
  • Adds cold-start framing: "eliminates the cold start", "not a middleware, not a proxy"
  • Keeps validated ~50% token savings (no change to data claims)

Why

"Navigation layer" undersells CodeCortex. It provides knowledge (architecture, coupling, risk, decisions, patterns) — not just pointers. The real issue was the old 85% claim and unclear messaging about whether it replaces code reading. Fix: keep "knowledge layer", drop bad claims, clarify it's cold-start knowledge not a middleware.

Files (4)

  • README.md — subtitle + solution section
  • CLAUDE.md — one-liner
  • package.json — description
  • src/mcp/server.ts — MCP server description

Also updated (site, not in git)

  • layout.tsx SEO titles/descriptions
  • Hero, Features, FAQ, llms.txt, changelog — all updated to knowledge layer + cold-start framing
  • GitHub repo description updated

Test plan

  • tsc --noEmit — clean
  • npm test — 276/276 pass

🤖 Generated with Claude Code

"Navigation layer" undersells what CodeCortex does. It IS a knowledge layer —
the issue was the old 85% claim and unclear relationship to code reading.

Changes:
- "navigation and risk layer" → "persistent codebase knowledge layer"
- Added cold-start framing: "eliminates the cold start", "not a middleware"
- Kept validated ~50% token savings data
- Updated: README, CLAUDE.md, package.json, server description

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
@rushikeshmore rushikeshmore merged commit ed92e17 into main Mar 8, 2026
1 of 3 checks passed
@rushikeshmore rushikeshmore deleted the v0.5.0-knowledge-layer branch March 8, 2026 19:30
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant