Context
ECP.Registry already provides semantic compression. We need a public RFC to evaluate incremental improvements without breaking compatibility.
Goal
Collect concrete options for improving compression efficiency while preserving deterministic decode behavior.
Discussion points
- Dictionary evolution strategy and compatibility rules
- Candidate heuristics for better token coverage
- Benchmark methodology (before/after, same vectors)
- Migration impact for existing dictionary users
Acceptance criteria
Why this matters
A documented RFC process improves technical transparency and reduces regression risk.
Context
ECP.Registryalready provides semantic compression. We need a public RFC to evaluate incremental improvements without breaking compatibility.Goal
Collect concrete options for improving compression efficiency while preserving deterministic decode behavior.
Discussion points
Acceptance criteria
Why this matters
A documented RFC process improves technical transparency and reduces regression risk.