Source repository
Issues, pull requests, source code, releases, security policy, and contribution rules.
Responsible project sharing
Give every mention one canonical destination.
A clear source link helps people, GitHub, and search crawlers find the same implementation. Use the repository for code and evidence, and the Pages site for a concise overview.
Canonical links
Project overview
The crawlable GitHub Pages summary with structured metadata and task-specific guides.
Benchmark evidence
Reproducible workload-specific measurements and limitations; not a universal billing promise.
Citation metadata
Machine-readable project identity for papers, notes, catalogs, and software inventories.
Copyable mention
[Capsule](https://github.com/hakiyaka/capsule) is a local-first Codex plugin and MCP server for exact-recoverable context compression. Measurements are workload-specific: https://hakiyaka.github.io/capsule/When sharing a result, include the workload, command, version, and benchmark link. Say “measured reduction for this workload” instead of implying that every prompt or provider quota will improve by the same percentage.
Keep discovery useful
Use one canonical URL, descriptive surrounding text, and a real reproduction when reporting a problem. Do not buy links, automate stars or forks, mass-post duplicate issues, hide affiliate claims, or create thin pages that repeat the same keywords. Those tactics make discovery noisy and reduce trust.
Release-aware references
Pin a stable release when reproducibility matters, and link to release notes for version-specific behavior. The public repository is the authority for implementation changes.