Show HN: A fail-closed evidence engine for norms used by AI agents
Version 0.1.0 · claim-by-claim evidence: CLAIM_MAP.md · not independently verified. The admissibility model and claim-map linter, as pure functions. It is the engine an MCP server would consume.
- ▪Version 0.1.0 · claim-by-claim evidence: CLAIM_MAP.md · not independently verified.
- ▪The admissibility model and claim-map linter, as pure functions.
- ▪It is the engine an MCP server would consume.
Hacker News (AI / LLM) files mainly under ai. We currently carry 3,381 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/Angeliasrl/norms-mcp-engine |
| Publication time | Mon, 03 Aug 2026 12:26:21 +0000 |
| Retrieval time | 2026-08-03T12:30:41.825Z |
| Last seen | 2026-08-03T12:30:41.825Z |
| 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 | lYrxe_1EEpvm · 1 stories |
| 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
norms-mcp-engine Experimental prerelease. Engine only. Not an MCP server. No I/O, network, persistence or transport. Version 0.1.0 · claim-by-claim evidence: CLAIM_MAP.md · not independently verified. The admissibility model and claim-map linter, as pure functions. No I/O, no network, no transport. This is not an MCP server. It is the engine an MCP server would consume. There is no entrypoint, no tool handler and no deployment here. norms-mcp, the server, does not yet exist as a published artifact. The naming distinction is deliberate: claiming a transport that is absent would be exactly the kind of overclaim this library exists to make visible.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at GitHub.