fix: revert to knowledge layer positioning, add cold-start framing#22
Merged
rushikeshmore merged 1 commit intomainfrom Mar 8, 2026
Merged
fix: revert to knowledge layer positioning, add cold-start framing#22rushikeshmore merged 1 commit intomainfrom
rushikeshmore merged 1 commit intomainfrom
Conversation
"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>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
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 sectionCLAUDE.md— one-linerpackage.json— descriptionsrc/mcp/server.ts— MCP server descriptionAlso updated (site, not in git)
Test plan
tsc --noEmit— cleannpm test— 276/276 pass🤖 Generated with Claude Code