Show HN: Coherence – drift detector for AI-driven repos
Coherence is a Git-native drift detector designed for AI-assisted repositories. It identifies inconsistencies in codebases edited by AI agents, ensuring that code, documentation, and tests remain aligned. The tool operates locally with deterministic checks and offers an optional LLM pass for deeper analysis.
- ▪Coherence detects broken links between code, documentation, tests, and other project artifacts after AI edits.
- ▪The tool runs locally and does not send code anywhere during its checks.
- ▪Coherence provides a detailed algorithm reference and examples for understanding its drift detection signals.
Hacker News (AI / LLM) files mainly under ai. We currently carry 3,306 of its stories.
Story provenance
Source · retrieval · rights · ranking — open for full record
inspect →
Story provenance
Attribution is not the same as permission. This drawer separates discovery metadata, excerpts, WeSearch-generated summaries, reuse status, and whether the publisher receives the visit. Nothing here claims a legal grant the publisher has not made.
Record
| Original publisher | GitHub |
| Canonical URL | https://github.com/fireharp/coherence |
| Publication time | Thu, 21 May 2026 19:13:40 +0000 |
| Retrieval time | 2026-05-21T19:16:35.672Z |
| Last seen | 2026-05-21T19:16:35.672Z |
| Headline source | Publisher (no WeSearch rewrite) |
| Excerpt source | publisher body |
| Excerpt method | First ~120 words (~800 chars) of extracted publisher body, fair-use limited. |
| Summary | WeSearch · cerebras-chat (WeSearch summarizer) |
| Summary source text | contentText |
| Citation coverage | Summary is a WeSearch-generated derivative; primary citation is the original publisher URL. |
| Cluster | RdxNyHGJsT38 |
| Cluster logic | Grouped by semantic title/content similarity across sources within a rolling window. Same-publisher template collisions are excluded from coverage comparison. |
| Ranking reason | Story pages are not engagement-ranked. Hub feeds use recency, with optional source-diversified chronological ordering (cap consecutive stories per source). No personalized ranking. |
| Publisher visit | Yes — open original |
| Substitutes article? | No — link-out required for full text |
Rights status (four layers)
WeSearch handling by dimension
| Indexing | May the item be indexed (stored, ranked, made findable)? | Allowed |
| Snippet | May a short excerpt of the publisher's text be shown? | Allowed |
| AI summary | May WeSearch generate its own short summary of the article? | Limited |
| Retrieval / RAG | May the content be exposed for third-party retrieval-augmented generation? | Not asserted |
| Model training | May the content be used to train AI models? | Not asserted |
| Commercial reuse | May the content be reused commercially? | Not permitted |
Basis: Derived from the published RSS/Atom feed. Contact: [email protected]. Reviewed: 2026-07-24.
Opening excerpt (first ~120 words) tap to expand
Coherence Git-native drift detector for agent-assisted repositories. Docs site: https://fireharp.github.io/coherence/ Coherence is not an AI reviewer. It is a repo consistency harness for AI-edited codebases. Tests pass. The repo still drifts. Coherence catches the broken links between code, docs, ADRs, tests, metrics, generated files, endpoints, and evidence - especially after AI-agent edits. Coherence runs locally. Deterministic checks do not send code anywhere. The optional LLM pass is disabled by default and only runs when COHERENCE_LLM=1 or --llm is set. Algorithm reference: docs/ has a long-form page for every drift meter and check, with the algorithm, JSON output shape, signal interpretation, and a benchmark scenario example. Start there if you want to understand a firing signal.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at GitHub.