WeSearch

Show HN: Musts – Open-source validation loops for AI coding agents

·5 min read · 0 reactions · 0 comments · 33 views
Show HN: Musts – Open-source validation loops for AI coding agents
TL;DR · WeSearch summary

Musts is an open-source tool designed to enhance the reliability of AI coding agents by enforcing a local definition of completion for code validation. It allows developers to specify validation tasks directly alongside their code, ensuring that all necessary checks are completed before a task is considered done. The tool operates in a loop, continuously validating and recording evidence until all tasks are resolved.

Key facts
How this story was covered

2 outlets in our directory ran this story, first to last over 18 hours. All of the coverage we found sits in one bucket: centre. That one-sidedness is itself worth noticing.

Centre · 1
About this source

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

Original article
GitHub
Read full at GitHub →

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 publisherGitHub
Canonical URLhttps://github.com/bitomule/musts
Publication timeMon, 25 May 2026 16:44:39 +0000
Retrieval time2026-05-25T16:57:38.841Z
Last seen2026-05-25T16:57:38.841Z
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.
ClustertFBiwVNvqrIT · 2 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

musts AI agents are fast at editing code. They are less reliable at knowing when verification is actually finished. musts gives your repository a local, enforceable definition of done: The task is not done until musts validate is empty. Instead of hoping the agent remembers every build, test, UI check, and architecture rule, you declare those checks next to the code they protect. When files change, musts validate reports the exact validation tasks still pending. The agent runs them, records evidence, and repeats until the report is clean. Get Started 1. Install the CLI # Homebrew (macOS / Linux) brew install bitomule/tap/musts # Cargo (from crates.io) cargo install musts --locked # Precompiled binaries cargo binstall musts # or download directly from GitHub Releases 2.

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

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

Discussion

0 comments

More from GitHub