Show HN: Check if your AI audit logs would survive an independence challenge
evidence verify One command that answers the question your AI audit logs can't: who guarantees this log wasn't altered by the system that produced it? $ evidence verify receipts.jsonl entries checked : 5 chain verdict : CHAIN VALID independence : SELF-ATTESTED — would not survive independence challenge. Every hash in this chain was produced and stored by the same system it describes; a compromised producer can re-sign the entire chain. Why this exists The EU AI Act's Article 12 requires automatic event logging for high-risk AI systems (Annex III obligations now apply from December 2, 2027 under the July 2026 Omnibus amendment; retention ≥6 months under Articles 19/26(6)).
- ▪evidence verify One command that answers the question your AI audit logs can't: who guarantees this log wasn't altered by the system that produced it? $ evidence verify receipts.jsonl entries checked : 5 chain verdict : CHAIN VALID independ
- ▪Every hash in this chain was produced and stored by the same system it describes; a compromised producer can re-sign the entire chain.
- ▪Why this exists The EU AI Act's Article 12 requires automatic event logging for high-risk AI systems (Annex III obligations now apply from December 2, 2027 under the July 2026 Omnibus amendment; retention ≥6 months under Articles 19/26(6)).
Hacker News (AI / LLM) files mainly under ai. We currently carry 4,171 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/Rehanrana11/evidence-verify |
| Publication time | Sun, 09 Aug 2026 12:17:10 +0000 |
| Retrieval time | 2026-08-09T12:25:42.113Z |
| Last seen | 2026-08-09T12:25:42.113Z |
| 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 | hX6R9_M67Zx5 · 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
evidence verify One command that answers the question your AI audit logs can't: who guarantees this log wasn't altered by the system that produced it? $ evidence verify receipts.jsonl entries checked : 5 chain verdict : CHAIN VALID independence : SELF-ATTESTED — would not survive independence challenge. Every hash in this chain was produced and stored by the same system it describes; a compromised producer can re-sign the entire chain. No external anchor found. Why this exists The EU AI Act's Article 12 requires automatic event logging for high-risk AI systems (Annex III obligations now apply from December 2, 2027 under the July 2026 Omnibus amendment; retention ≥6 months under Articles 19/26(6)). Most vendors answer with hash-chained logs. A hash chain proves sequence.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at GitHub.