Assay – Open-source mechanical checker for web pages, no tests, no LLM
assay Find out whether a generated web page actually works. Point it at a page. assay opens it in a real browser, measures every control it renders, works out a test plan from what it finds, drives all of it, and tells you what broke. The plan comes from the page, so a program written ten seconds ago can be checked ten seconds later.
- ▪assay Find out whether a generated web page actually works.
- ▪Point it at a page. assay opens it in a real browser, measures every control it renders, works out a test plan from what it finds, drives all of it, and tells you what broke.
- ▪The plan comes from the page, so a program written ten seconds ago can be checked ten seconds later.
Hacker News (AI / LLM) files mainly under ai. We currently carry 5,874 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/awss1i/assay |
| Publication time | Mon, 21 Sep 2026 14:37:45 +0000 |
| Retrieval time | 2026-09-21T14:38:48.982Z |
| Last seen | 2026-09-21T14:38:57.167Z |
| 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 | OV5vkRL4nxlY · 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
assay Find out whether a generated web page actually works. Checking a generated paint program. Nobody wrote a test. Point it at a page. assay opens it in a real browser, measures every control it renders, works out a test plan from what it finds, drives all of it, and tells you what broke. Highlights No tests to write. The plan comes from the page, so a program written ten seconds ago can be checked ten seconds later. No LLM. Purely mechanical. No API key, no tokens, no rate limit, nothing to bill. It gives the same answer twice. No baseline images and no recordings. Nothing to capture first, nothing to keep in step with the design. It says why. Not case 14 failed, but the first press did nothing and the second did something, so this control is one behind.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at GitHub.