WeSearch
Our EU AI Act compliance engine has zero LLM calls, and CI blocks adding any

Our EU AI Act compliance engine has zero LLM calls, and CI blocks adding any

Opencomplai· ·1 min read · 0 reactions · 0 comments · 0 views
More from Opencomplai ai Compare coverage Trending Talk Blindspots Daily Sources Live wire
TL;DR · WeSearch summary

I decided no LLM would go near my compliance decisions.If a tool decides whether your AI system is legal to ship, the last thing I want deciding that is another model nobody can explain.Opencomplai's rule engine (packages/core) and CLI are fully deterministic. Not anywhere in the compliance decision path.That's a design constraint, not a line for the landing page, and I don't just assert it. It's opt-in, sandboxed to its own package, and it never touches the pass/fail decision.

Key facts
About this source

Hacker News (AI / LLM) files mainly under ai. We currently carry 6,293 of its stories.

Original article
Opencomplai · Opencomplai
Read full at Opencomplai →

Story provenance

Source · retrieval · rights · ranking — open for full record
inspect →

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 publisherOpencomplai
Canonical URLhttps://opencomplai.com/blog/no-llm-in-compliance-decisions
Publication timeThu, 24 Sep 2026 13:50:46 +0000
Retrieval time2026-09-24T14:05:26.716Z
Last seen2026-09-24T14:05:26.716Z
Headline sourcePublisher (no WeSearch rewrite)
Excerpt sourcepublisher body
Excerpt methodFirst ~120 words (~800 chars) of extracted publisher body, fair-use limited.
SummaryWeSearch · cerebras-chat (WeSearch summarizer)
Summary source textcontentText
Citation coverageSummary is a WeSearch-generated derivative; primary citation is the original publisher URL.
Clusterm_GnW_-CJMns · 1 stories
Cluster logicGrouped by semantic title/content similarity across sources within a rolling window. Same-publisher template collisions are excluded from coverage comparison.
Ranking reasonStory pages are not engagement-ranked. Hub feeds use recency, with optional source-diversified chronological ordering (cap consecutive stories per source). No personalized ranking.
Publisher visitYes — open original
Substitutes article?No — link-out required for full text

Rights status (four layers)

Publisher-declared
No publisher-confirmed rights record for this source yet.
Machine-readable
No source-specific machine-readable restriction detected beyond the public feed.
WeSearch interpretation
WeSearch declared handling (basis: Derived from the published RSS/Atom feed). This is WeSearch policy, not a legal grant on the publisher's behalf.
Unknown
Retrieval and training permissions are not asserted unless the publisher confirms them.

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

I decided no LLM would go near my compliance decisions.If a tool decides whether your AI system is legal to ship, the last thing I want deciding that is another model nobody can explain.Opencomplai's rule engine (packages/core) and CLI are fully deterministic. No LLM. No ML inference. Not anywhere in the compliance decision path.That's a design constraint, not a line for the landing page, and I don't just assert it. CI enforces it. Every pyproject.toml, package.json and requirements*.txt in the repo is scanned for unapproved AI/LLM packages on every PR, with excludes for tests, examples and fixtures so a demo notebook doesn't fail the build.Add a transformers import to the risk engine without going through approval and the build breaks before it merges.There is an ML path.

Excerpt limited to ~120 words for fair-use compliance. The full article is at Opencomplai.

Anonymous · no account needed
Share 𝕏 Facebook Reddit LinkedIn Threads WhatsApp Bluesky Mastodon Email

Discussion

0 comments

More from Opencomplai