Skip to content

Latest commit

 

History

History
712 lines (544 loc) · 32.6 KB

File metadata and controls

712 lines (544 loc) · 32.6 KB

Clean-CTX — Token Waste Reducer & Structured Transport Protocol

🚀 Version 0.2.1-rc1 — Zero-touch workflow (provide_code_context), SQLite persistence layer, Angular/Spring Boot/.NET meta-layers, IR-level delta compression, text-level delta transport, cross-file dependency graph, modern Angular 17–21 syntax support, CBM filter-first architecture (symbol importance filtering before compression), Rust and Java language support, multi-platform proxy (Anthropic/OpenAI/Generic), 26 built-in tool output filters, secret scrubbing, streaming workspace walk (walkdir), Rayon-parallelized workspace compression, deterministic alias assignment, workspace compression result caching, R-43a Execution Semantics (DataFlow/ControlFlow/SideEffect/ExecutionContext across Rust/C#/TypeScript), R-43b Program Graph + Inference Layer + Pass Pipeline + Validator + Query Engine + Semantic Delta, and all 1,745 tests passing with zero clippy warnings.

A local-first, air-gapped code context optimizer that reduces LLM token waste through four independent mechanisms: CBM symbol filtering (drops low-importance symbols before compression), compression (75–97% token savings), tool output filtering (70–90% savings), and intelligent prompt caching (~90% API cost savings).

How It Works

Clean-CTX uses four independent mechanisms to reduce token waste:

  1. CBM symbol filtering — integrates with codebase-memory-mcp (CBM) to query symbol importance scores before compression runs. Low-importance symbols (score < 0.4) are dropped entirely, reducing token output by 30–50% for noisy files. This is the only mechanism that reduces tokens before compression.

  2. Compression — tree-sitter AST extraction + opcode encoding at 3 fidelity levels (Low/Medium/High) delivers 75–97% token savings vs raw source. This is what reduces LLM prompt tokens.

  3. Tool filtering — 26 built-in TOML filters compress verbose tool output (build logs, lint results, test output, etc.) by 70–90% before it reaches the LLM. Filters auto-detect the command from tool input and apply program-specific compression (e.g., collapsing a successful cargo build to "cargo: ok").

  4. Intelligent prompt caching — the optional multi-platform proxy injects cache_control breakpoints into API requests, achieving ~90% API cost savings on cached turns by leveraging provider-side prompt caching (Anthropic, OpenAI, etc.).

Delta transport is a CPU-savings layer that avoids full re-compilation on subsequent calls, saving CPU cycles and latency (up to 53% faster). It does NOT reduce LLM tokens — the LLM receives the same full compressed output either way.

┌─────────────────────────────────────────────────────────────┐
│  What delta saves              │  What delta does NOT save  │
│  ───────────────────────────── │  ───────────────────────── │
│  ✅ CPU cycles — avoids        |  ❌ LLM prompt tokens —   │
│     re-parsing and full        │     the LLM receives the   │
│     re-compression             │     same compressed output │
│  ✅ Latency — up to 53%        │  ❌ API costs — delta     │
│     faster at High fidelity    │     payload has the same   │
│  ✅ Session throughput — more  │     token count            │
│     edits per minute           │                            │
└─────────────────────────────────────────────────────────────┘

LLM token savings come from CBM filtering, compression, and tool filtering. Delta transport is a CPU-savings layer on top of compression — it makes the compiler itself faster, not the output smaller. Prompt caching reduces API costs on repeated turns without changing token counts.


Quick Start

Prerequisites

  • Rust 1.85+ (edition 2024)

Install

# Clone and build (release binary)
git clone https://github.com/codeliftsleep2/Clean-CTX.git
cd Clean-CTX
cargo build --release

# The binary is at: target/release/clean-ctx.exe (Windows) or target/release/clean-ctx (Linux/Mac)

Language & Feature Selection

Clean-CTX uses Cargo feature flags to control which languages and meta-layers are compiled into the binary. This lets you build a minimal binary with only the languages you need, reducing compile time and binary size.

Category Feature Implies Includes Build With Default
Language typescript Base TypeScript/JavaScript grammar --features typescript
Language csharp Base C# grammar --features csharp
Language rust Base Rust grammar --features rust
Language java Base Java grammar --features java
Meta-Layer angular typescript Components, Services, DI, Pipes, Directives, Modules, Input/Output, Template/Shape extraction, Style extraction, NgRx, RxJS, Signals, PrimeNG, Bundle graph --features angular
Meta-Layer spring_boot java RestController, Controller, Service, Repository, Configuration, RequestMapping, Autowired, Value, Bean, ConfigurationProperties, Cross-file graph --features spring_boot
Meta-Layer dotnet csharp ASP.NET Core (Controllers, Actions, Routes, Auth), EF Core (DbContext, DbSet, Entities), SignalR (Hubs, Clients, Streaming), AutoMapper (Profiles, Mappings), JSON Serialization, DI, Validation, Identity, Caching, Logging, Cross-file graph --features dotnet

Build with only specific languages:

# Default (TypeScript + C# + Angular only)
cargo build --release

# TypeScript + Angular only (no C#)
cargo build --release --no-default-features --features typescript,angular

# .NET/C# only (no TypeScript, Angular)
cargo build --release --no-default-features --features csharp,dotnet

# Rust only (no TypeScript, C#, Java, meta-layers)
cargo build --release --no-default-features --features rust

# All languages + all meta-layers
cargo build --release --features rust,java,spring_boot,dotnet

Default features give you TypeScript with Angular meta-layer, C#, and .NET enrichment — the most common full-stack combination. Everything else is opt-in:

# Add Rust, Java, and Spring Boot
cargo build --release --features rust,java,spring_boot

# Add just Rust
cargo build --release --features rust

Configure VS Code

Add to your MCP settings (see IDE Configuration below for all options):

{
  "mcpServers": {
    "clean-ctx": {
      "command": "C:\\path\\to\\clean-ctx.exe",
      "args": []
    }
  }
}

Restart your editor. The tools provide_code_context, compress_code_context, decompress_code_context, compress_workspace, diff_code_context, delta_code_context, delta_text_context, apply_delta, context_stats, context_history, save_context, list_sessions, replay_history, purge_old_deltas, and restore_context will be available.


Key Features

Zero-Touch Workflow

The recommended entry point is provide_code_context — a single tool that automatically handles compression, delta transport, Angular detection, fidelity selection, and CBM symbol filtering:

Tool Purpose
provide_code_context Single entry point — auto-detects file type, selects optimal fidelity, uses delta transport on subsequent calls, filters low-importance symbols via CBM
restore_context Force full re-compression, clearing all baselines and DB entries
context_history View compression history and delta savings for tracked files
context_stats Dashboard: token savings, compression stats, session metrics

The workflow automatically:

  • Runs a heuristics engine to select the best fidelity and strategy based on file characteristics
  • Detects Angular/Spring Boot files and enables the Meta-Layer with framework-specific markers
  • Uses delta transport on subsequent calls to avoid re-compiling the full IR from scratch (reduces CPU/latency by up to 53%, while the LLM receives the same full compressed output)
  • Records session stats for monitoring compression efficiency
  • Persists contexts to SQLite for crash recovery and cross-session continuity

How the Transport Protocol Works

                   ┌──────────────────┐
                   │  Source Code     │
                   │  (file on disk)  │
                   └────────┬─────────┘
                            │
                            ▼
                   ┌──────────────────┐
                   │  IRCompiler      │  Translates source → Vec<CoreOp>
                   │  (4 layers)      │  Language + Meta + Pattern layers
                   └────────┬─────────┘
                            │
                            ▼
               ┌────────────────────────┐
               │  CompiledIR { v: N }   │  Canonical instruction stream
               └────────┬───────────────┘
                        │
           ┌────────────┴────────────┐
           │                         │
           ▼                         ▼
┌──────────────────┐    ┌──────────────────┐
│  1st call:       │    │  N+1th call:     │
│  send full IR    │    │  compute delta   │
│  store in state  │    │  send only diffs │
│  machine         │    │  apply to state  │
└──────────────────┘    └──────────────────┘

At the protocol level:

  1. First compressioncompile_file_ir() runs the 4-layer pipeline (Core IR → Language → Meta → Patterns), producing a CompiledIR with version 1. The full IR is persisted in the in-session ContextState state machine.

  2. Subsequent editsdelta_code_context re-compiles the file, computes instruction-level diffs between the baseline and current IR via DeltaComputer, and returns only the +/~/- operations. The client's ContextState applies these via apply() — deletions first, then modifications, then additions.

  3. Field-patch encoding — when a method is renamed, only the changed field index and new value are transmitted, not the full instruction tuple. This is the most compact form (~5-8 tokens per edit).

  4. Fallback — if the state machine detects a version mismatch, it returns a full re-compression to re-sync.

CBM (Codebase Memory) Integration

Clean-CTX integrates with codebase-memory-mcp (CBM) using a filter-first architecture: CBM symbol importance scores determine which symbols are excluded from compression entirely, reducing token output instead of adding post-compression metadata.

Feature Description
Symbol Importance Filtering Symbols with importance score < 0.4 are dropped before compression runs, reducing token output by 30-50% for noisy files
Blast Radius Dependency graph tracing — knows which files are affected by a change
Dead Code Detection Identifies orphaned classes, methods, and fields
Architecture Awareness Understands layering, module boundaries, and dependency direction

How it works:

  1. provide_code_context queries CBM for symbol importance scores via get_symbol_importance(project)
  2. build_cbm_skip_set() identifies symbols with score < 0.4 for the current file
  3. The compression pipeline checks should_skip_capture() for each class/method/field — low-importance symbols are dropped entirely
  4. The IR compiler applies the same skip check before emitting DefClass/DefMethod/DefField
  5. Session stats record tokens removed under the cbm_filter domain

Result: CBM reduces token output instead of increasing it. The post-compression enrichment step is removed.

Component Description
client.rs JSON-RPC 2.0 subprocess client with retry + exponential backoff
bridge.rs DashMap-based TTL caching with detect_changes() cache invalidation
proxy.rs Pipe-level response interception and JSON-aware compression (~5,000 → ~1,100 tokens, ~78% savings)
json_compress.rs JSON-aware compressor: key shortening, envelope stripping, null field removal

Spring Boot Meta-Layer

For Spring Boot Java projects, Clean-CTX automatically detects framework annotations and enriches compressed output with structured Φ markers:

Marker Meaning
Φrest: / Φctrl: @RestController / @Controller with request mappings
Φsvc: @Service component
Φrepo: @Repository component
Φconf: @Configuration component
Φmap: @RequestMapping method mappings
Φaut: @Autowired field injection
Φval: @Value property injection
Φbean: @Bean method-level injection
Φprop: @ConfigurationProperties class
Φpropf: Properties file structural shape
Φgraph: Cross-file dependency graph (workspace mode)

Three-Fidelity Compression

Fidelity Description Savings Best For
Low Maximum compression with symbol opcodes ~81-96% Reading large codebases
Medium Preserves async, exports, behavior markers ~61-84% Understanding code behavior
High Preserves full keywords + indentation ~61-83% Code review / documentation

Core Tools

Tool Purpose
compress_code_context Source file → compressed skeleton (text or IR with encoding selection)
decompress_code_context Compressed skeleton → human-readable format
compress_workspace Entire directory → single compressed manifest
diff_code_context Source file → AST-level change-set (+ / - / ~ / =)
delta_code_context IR-level delta compression — instruction-level deltas between compiled IR states
delta_text_context Text-level delta compression — line-level deltas between compressed body snapshots
apply_delta Client-side state update — applies IR delta to in-session state machine

Persistence Layer (Built-in)

Compression contexts persist automatically across sessions using SQLite (enabled by default, stored in .clean-ctx/persistence.db):

Tool Purpose
save_context Manual checkpoint to DB
list_sessions Show tracked files/sessions
replay_history Replay deltas from DB (crash recovery)
purge_old_deltas Trim old delta history

Persistence uses a three-tier reliability stack:

  1. Batched writes — operations queue in memory and flush as single transactions
  2. Retry with exponential backoff — transient DB failures retry up to 3 times
  3. JSON file fallback — if all retries fail, data writes to .clean-ctx/fallback/ and re-imports on next successful flush

Disable in .clean-ctx.json with: "persistence": { "enabled": false }

Smart Caching

  • Content-hash cache — identical files compress instantly on repeat calls
  • Baseline snapshotsdiff_code_context remembers the previous state, producing small deltas instead of full re-compressions
  • Raw-token count cache — skip the BPE encode on cache hits (sub-millisecond responses)
  • Workspace result cachecompress_workspace caches the complete manifest keyed by file paths + mtimes + fidelity. Subsequent calls with no file changes return instantly (saves 5-15s per redundant call)

Path Aliases

Path aliases (α1, α2, …) are session-global — compress_workspace populates aliases that are immediately visible to subsequent provide_code_context calls, keeping the §PATHMAP footer stable across multiple tools. Aliases are pre-assigned deterministically before parallel compression to ensure αN numbering is stable across runs.

Multi-Platform Proxy

Clean-CTX ships with an optional local HTTP proxy that sits between your LLM client and any AI API (Anthropic, OpenAI, DeepSeek, etc.), automatically injecting cache_control breakpoints to achieve ~90% API cost savings on cached turns:

AUTO_CACHE=1 TOOL_FILTERS=1 SCRUB_SECRETS=1 cargo run -p clean-ctx-proxy

Works with Cline, Cursor, Aider, Continue.dev, and GitHub Copilot (BYOK). See docs/PROXY.md for full documentation.

Tool Output Filtering

The proxy includes 26 built-in TOML filters that compress verbose tool output by 70–90%:

Category Filters
Build cargo, make, mvn, node-build, dotnet-build, go
Lint eslint, ruff, biome, mypy, pyright, golangci-lint, shellcheck, hadolint, yamllint
Test pytest, dotnet-test, ng
Package Mgr npm, pip, apt, brew
DevOps docker, docker-logs, kubectl
Git gh, git-diff, pre-commit
System curl, ssh, systemctl, tsc

Enable with TOOL_FILTERS=1. Filters auto-detect the command from tool input and apply program-specific compression (e.g., collapsing a successful cargo build to "cargo: ok"). Custom filters can be added as TOML files in .clean-ctx/filters/.

Secret Scrubbing

The proxy detects and redacts secrets (AWS keys, GitHub tokens, JWTs, PEM keys, etc.) in tool results before they reach the LLM. Enable with SCRUB_SECRETS=1.

Security

  • Zero network transport — stdio-only via MCP, no HTTP/WS/RPC servers
  • No external runtimes — single statically linked binary
  • No AI models — fully deterministic, rule-based AST processing
  • Minimal unsafe code — only in test utilities for environment variable manipulation (required by Rust's stdlib)

Usage Examples

Quick context (recommended)

{
  "name": "provide_code_context",
  "arguments": {
    "filePath": "/path/to/MyService.ts"
  }
}

First call performs full compression; subsequent calls automatically use delta transport.

Compress a file (Low fidelity)

{
  "name": "compress_code_context",
  "arguments": {
    "filePath": "/path/to/MyService.ts",
    "fidelity": "low"
  }
}

Output (Phase 6 IR-first):

// SCHEMA v2  @=meta X=extends I=implements F=field M=method $=import →=scope fl:=flags cl:=class-flags P=pattern T=type-alias
// ── SampleService ──
M doWork(payload:$s[]):$b

Decompress back to readable format

{
  "name": "decompress_code_context",
  "arguments": {
    "compressedText": "$c SampleService;$ctor();processComplexData(payload: $s[]): $b;healthCheck(): $s"
  }
}

Output:

class SampleService;constructor();processComplexData(payload: string[]): boolean;healthCheck(): string

Compress entire workspace

{
  "name": "compress_workspace",
  "arguments": {
    "directoryPath": "C:\\path\\to\\project",
    "fidelity": "medium"
  }
}

AST-level diff (track changes over time)

{
  "name": "diff_code_context",
  "arguments": {
    "filePath": "/path/to/MyService.ts"
  }
}

First call stores the current state as baseline. Subsequent calls return only the changes:

// --- AST Diff: C:\path\to\MyService.ts ---
// +1 ~1 =1 (classes/methods/fields/imports)

~ class MyService
  + method archive():void
  ~ method process(id:string):boolean
        was: process(id:number):boolean
  = method healthCheck():string (unchanged)

IR-level delta (edit sessions)

{
  "name": "delta_code_context",
  "arguments": {
    "filePath": "/path/to/MyService.ts"
  }
}

First call stores baseline IR; subsequent calls return only the structural delta:

IR delta: v1 → v2

View compression dashboard

{
  "name": "context_stats",
  "arguments": {}
}

📊 Performance Benchmarks

Token Compression

Clean-CTX delivers 75–97% token waste reduction on real-world files. See docs/PERFORMANCE.md for the full per-file breakdown across all three fidelity levels (Low/Medium/High) and aggregated savings across all test files.

Key highlights:

  • Low fidelity: Up to 97.5% savings on large files (438 lines)
  • Medium fidelity: Up to 86.3% savings — balanced detail with behavior markers
  • High fidelity: Up to 77.2% savings with full type annotations preserved
  • Aggregate (3 test files): 96.1% worst-case reduction at Low fidelity

Delta Transport (50-Edit Session, CPU Savings Only)

Delta transport does NOT reduce LLM token counts — it reduces local CPU/latency by avoiding full re-parsing on subsequent calls. Simulated 50 sequential edits on a ~440-line file:

Fidelity Full ReComp (cumulative) Delta (cumulative) Delta vs ReComp
Low 7,823 tokens 8,490 tokens +8.5% overhead*
Medium 37,338 tokens 18,287 tokens −51% cheaper
High 48,556 tokens 22,955 tokens −53% cheaper

*At Low fidelity the compressed output is already tiny (~156 avg tokens), so delta's fixed envelope cost adds overhead. Delta is always within 0.3 percentage points of recompression at Low.

  • Delta transport breaks even from Edit #1 at Medium/High fidelity

See docs/PERFORMANCE.md for per-edit breakdowns, caching analysis, microbenchmarks, and optimization checklist.


Opcode Reference

Built-in Primitives (34 opcodes, always available)

Opcode Token Opcode Token Opcode Token
$c class $s string $b boolean
$n number $v void $a async
$e export $r return $t throw
$T true $F false $P Promise
$ctor constructor $fn function $E Error
$nw new $i if $fr for
$w while $h this $k const
$l let $pu public $pv private
$st static $x extends $m implements
$if interface $ty type $nl null
$ud undefined $fm from $im import

Behavior Markers

Marker Meaning
⊕guard Conditional branch (if statement)
⊕loop Iteration (for/while loop)
⊕⇒ Return value follows
⊕! Throws error
⊕export Module export

Angular Meta-Layer Markers (Φ)

Marker Meaning
Φcmp: @Component — class name + selector, template URL, style URLs
Φsvc: @Injectable — class name + providedIn scope
Φmod: @NgModule — class name + declarations, imports, exports
Φdir: @Directive — class name + selector
Φpipe: @Pipe — class name + pipe name
Φin: @Input — field name + optional alias
Φout: @Output — field name + optional alias
Φmodel: model() signal — field name + optional alias (Angular 17.1+)
Φinjects: Constructor/DI injection — resolved types with file aliases
Φtpl: Template shape — tags, bindings, control flow blocks
Φsty: Style shape — class selectors, SCSS/CSS variables
ΦBUNDLE File-triplet bundle group (workspace manifest)
ΦMAP Workspace bundle alias map footer
Φgraph: Cross-file dependency graph edge
§ΦGRAPH Workspace dependency graph footer section

Spring Boot Meta-Layer Markers (Φ)

Marker Meaning
Φrest: @RestController with request mappings
Φctrl: @Controller with request mappings
Φsvc: @Service component
Φrepo: @Repository component
Φconf: @Configuration component
Φmap: @RequestMapping / @GetMapping / etc. method mappings
Φaut: @Autowired field injection
Φval: @Value property injection
Φbean: @Bean method definition
Φprop: @ConfigurationProperties class
Φpropf: Properties file structural shape

IDE Configuration

Cline / Roo Code

File: ~/.vscode/extensions/saoudrizwan.claude-dev/settings/cline_mcp_settings.json

{
  "mcpServers": {
    "clean-ctx": {
      "command": "C:\\path\\to\\clean-ctx.exe",
      "args": []
    }
  }
}

Cursor

File: .cursor/mcp.json (project root)

{
  "mcpServers": {
    "clean-ctx": {
      "command": "C:\\path\\to\\clean-ctx.exe",
      "args": []
    }
  }
}

Claude Code (Anthropic)

File: ~/.claude/settings.json or VS Code settings.json

{
  "mcpServers": {
    "clean-ctx": {
      "command": "C:\\path\\to\\clean-ctx.exe",
      "args": []
    }
  }
}

Continue.dev

File: .continue/config.json

{
  "mcpServers": [
    {
      "name": "clean-ctx",
      "command": "C:\\path\\to\\clean-ctx.exe",
      "args": []
    }
  ]
}

Zed

File: settings.json (Zed settings)

{
  "context_servers": {
    "clean-ctx": {
      "command": "C:\\path\\to\\clean-ctx.exe",
      "args": []
    }
  }
}

MCP Prompts

The cleanctx-notation prompt provides system-level instructions to the AI explaining how to read and write Clean-CTX compressed notation. When loaded, the AI learns:

  • How to interpret all opcodes ($c, $ctor, $s, etc.)
  • How to interpret behavior markers (⊕guard, ⊕loop, ⊕!throw, ⊕⇒)
  • How to interpret Angular and Spring Boot Meta-Layer markers
  • To respond in compressed form when appropriate
  • To never output raw opcode tables or metadata sections

Configuration

Create a .clean-ctx.json file in your project root:

{
    "exclude_patterns": ["dist", "node_modules", "*.spec.ts"],
    "fidelity_overrides": {
        ".cs": "medium",
        ".test.ts": "high"
    },
    "default_fidelity": "medium",
    "type_aliases": {
        "UserId": "string",
        "JsonObject": "Record<string, unknown>"
    }
}

See docs/DEVELOPER_DOCUMENTATION.md for the full configuration reference.


Supported Languages

Language Extension Status
TypeScript .ts, .js ✅ Full support (Angular meta-layer)
C# .cs ✅ Full support
Rust .rs ✅ Full support (structs, enums, traits, impls, generics, derives, cfg, unsafe)
Java .java ✅ Full support (classes, interfaces, records, enums, Spring Boot meta-layer)

Angular framework detection is automatic for TypeScript files containing @Component, @Injectable, @NgModule, @Directive, or @Pipe decorators. Spring Boot detection is automatic for Java files containing @RestController, @Service, @Repository, @Configuration, or @RequestMapping annotations.


Building from Source

# Debug build
cargo build

# Release build (stripped, LTO-optimized)
cargo build --release

The binary is output as clean-ctx.exe (Windows) or clean-ctx (Linux/Mac).


Project Status

Metric Value
Build cargo check clean
Linting cargo clippy --all-targets -- -D warnings0 warnings, 0 errors
Tests 1,745 tests, all passing, including 130+ integration/e2e tests
Audit ✅ FAANG-level audit — all 11 findings resolved (A-09 through A-15, F-19 through F-22); CBM audit — all findings resolved; Compiler-IR audit — all findings resolved; R-43a + R-43b FAANG audit — zero critical/high findings
Languages ✅ TypeScript, C#, Rust, Java with Angular/Spring Boot/.NET meta-layers, execution semantics across all 3 language layers
IR Transport Protocol ✅ Stateful instruction-level delta transport — compile once, send deltas thereafter
Execution Semantics ✅ R-43a: 4 new CoreOp variants (DataFlow, ControlFlow, SideEffect, ExecutionContext) — 6 wire formats, SemanticIntent on IRDelta, Rust/C#/TS language layers
Program Graph ✅ R-43b: Lightweight local program graph with 6 edge types (calls, extends, implements, injects, dataflow_read, dataflow_write) — structural only, no CBM data
Inference Layer ✅ R-43b: Ephemeral confidence-scored layer — NEVER serialized into wire format, CBM enrichment with confidence < 1.0, 29 tests covering all sources/edge types/edge cases/stress
Pass Pipeline ✅ R-43b: Composable 7-pass pipeline (Core → Language → Meta → Exec → Graph → Inference → Validation) with IRPass trait
IR Validator ✅ R-43b: 10 validation rules (E001-E010) — structural, behavioral, and side-effect consistency checks
Query Engine ✅ R-43b: IRQueryEngine with local + CBM-enriched queries and confidence scores for async detection, fan-in/fan-out, dataflow tracing
Semantic Delta ✅ R-43b: Intent detection (RenameSymbol, AddMethod, ChangeSignature, AddInjection, etc.) on IRDelta
Round-trip Tests ✅ 18 tests covering all 6 wire formats + compact delta + randomized property tests (100/100/50 iterations)
CBM Integration ✅ Filter-first architecture — symbol importance scores drop low-importance symbols before compression; InferenceLayer enrichment for cross-file edges
Delta Transport ✅ IR-level + text-level, field-patch encoding, compact delta format
Persistence ✅ SQLite cross-session persistence with three-tier reliability
Proxy ✅ Multi-platform proxy (Anthropic/OpenAI/Generic) with auto-cache + tool filters
Filters ✅ 26 built-in TOML filters — cargo, npm, eslint, docker, go, and more
Largest file ~170 lines (down from 913)
Unsafe code Test-only (env var manipulation)

Documentation

Document Audience Content
README.md Users Installation, configuration, usage, opcode reference
CONTRIBUTING.md Contributors Overview, process, quick links to detailed docs
docs/ARCHITECTURE_OVERVIEW.md Architects System design, module structure, pipeline stages, design decisions
docs/DEVELOPER_DOCUMENTATION.md Contributors Building, testing, adding languages/tools/opcodes, code quality gates
docs/COMPILER_IR.md Architects Compiler IR protocol, delta state transport, wire format, phase implementation
docs/ANGULAR_META_LAYER.md Developers Angular Meta-Layer design, marker vocabulary, template extraction, graph
docs/EDIT_TYPE.md Developers Edit categorization vocabulary for delta transport annotation
docs/TROUBLESHOOTING.md Users Common issues, error codes, diagnostic commands
docs/PERFORMANCE.md Architects Benchmarks, caching, memory profile, optimization checklist
docs/SECURITY.md Administrators Compliance checklist, hardening, SBOM, air-gap deployment
docs/CHANGELOG.md All Version history with all additions, fixes, and deferrals
docs/INTELLIGENCE_LAYER_PLAN.md Architects Intelligence Layer: PageRank scoring, blast radius, token budget packing
docs/CBM_INTEGRATION_PLAN.md Architects CBM filter-first architecture, pipe-level proxy, domain-tagged stats
docs/ROADMAP.md Contributors Future plans, prioritized items, carry-over from audit

License

CC0-1.0 Universal — Dedicated to the public domain.