Soften OSS→hosted references in CLAUDE.md

kiyeonjeon21 · claude · kiyeonjeon21 · commit db8524623cca · 2026-04-19T17:24:12.000+09:00
Rewrite the "Relationship to contextix-platform" section into
"Relationship to contextix.io". Drop the implementation detail list
(pg_trgm dedup, launchd batch, specific Supabase shape) in favor of
a boundary rule contributors actually need — "don't import
hosting-layer code here" — without cataloging the hosted side's
moat. The companion private repo's existence is still acknowledged
via the boundary rule itself.

Co-Authored-By: Claude Opus 4.7 (1M context) &lt;noreply@anthropic.com&gt;
diff --git a/CLAUDE.md b/CLAUDE.md
@@ -93,11 +93,11 @@ node dist/index.js serve              # MCP test (pipe JSON-RPC)
 
 Publish: `npm version patch && npm publish` (after local smoke test).
 
-## Relationship to contextix-platform
+## Relationship to contextix.io
 
-- `contextix-platform` runs a **production pipeline** on curated crypto + AI sources → feeds contextix.io (hosted graph showcase).
-- It uses this OSS repo as the engine but adds: Supabase schema, RLS, entity dedup via pg_trgm + Haiku, scheduled batch (launchd), Next.js frontend.
-- **Do not** import platform-specific code (Supabase, Next.js, scheduled agents) into this repo.
+The hosted graph you see at [contextix.io](https://contextix.io) is a dogfood showcase — we run this OSS on curated crypto + AI sources and display the result. The scheduler, hosting, UI, and source curation all live in a separate private repo; none of that infrastructure belongs in this OSS package.
+
+- **Do not** import hosting-layer code (Next.js frontend, scheduled batch, Supabase-specific dedup logic) into this repo.
 - **Do** keep the core engine self-contained so any dev can run the same pipeline on their own sources.
 
 ## What NOT to add here
