Deterministic context compiler for small-window coding models
Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.
Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"ccw-mcp","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.
Everything here was measured by our prober or read from a registry. Nothing is self-reported.
Attributed to the source that supplied each field. Treated as claims, not facts.
# ccw **CCW is a deterministic context compiler for small-window coding models.** Most context pipelines give a model either everything (too noisy) or an embedding-retrieved guess (unverifiable). CCW does neither. It walks the repo, records explicit facts and run history, and assembles a bounded, grounded markdown artifact whose every file path, symbol, and constraint traces back to the real index. No vector store. No LLM in the critical path. Receipts included. The compiled artifact and a portable session bundle are the primary surfaces. An MCP server exposes the same pipeline as callable tools so your existing harness, editor, agent, or workflow runner can consume deterministic context without shelling out. CCW is not an agent framework, coding assistant, editor, orchestrator, or harness adapter. It does one job: compile grounded repository context that other tools can use. ## What CCW is for - Use CCW when you want a task-scoped repo briefing with explicit receipts. - Use it when hidden editor context, giant prompt dumps, or vector search feel too opaque for a coding task. - Bring your own harness. CCW provides CLI commands, MCP tools, and file-only session bundles; it does not manage model sessions or execute agent loops. ## Compared to adjacent tools - **Repomix** packs a repository for an LLM. CCW compiles a validated, task-specific artifact from an indexed repo, explicit memory, and a budget. - **aider repo map** gives aider's own agent a compact code map. CCW produces provider-neutral artifacts any compatible tool can consume. - **LangGraph** orchestrates stateful agents. CCW prepares the deterministic repo context such an agent may read before acting. - **Cursor, Claude Code, Codex, Copilot, and similar tools** include their own context systems. CCW makes context selection inspectable outside any one product. ## Why deterministic compilation matters A small-window model working on a real codebase needs: - **Relevance** — only files…
Mapped onto the structured taxonomy from declared text and observed tool names. Confidence shown for derived entries.
Every source is kept verbatim. Field changes are logged as events.