Show HN: An open-source multi-tenant, AI-native software factory
An autonomous, multi-tenant, AI-native software factory Most AI tools tell you what they did. Every question you ask, every answer that comes back, every retry, and every token counted is appended to a file on your disk as it happens. What you see on screen is read back out of that file.
- ▪An autonomous, multi-tenant, AI-native software factory Most AI tools tell you what they did.
- ▪Every question you ask, every answer that comes back, every retry, and every token counted is appended to a file on your disk as it happens.
- ▪What you see on screen is read back out of that file.
Hacker News (AI / LLM) files mainly under ai. We currently carry 4,255 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/missingstudio/eva |
| Publication time | Mon, 10 Aug 2026 10:40:40 +0000 |
| Retrieval time | 2026-08-10T10:50:47.849Z |
| Last seen | 2026-08-10T10:50:47.849Z |
| 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 | 6AFiJ_ggnlZw · 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
Eva Evidence, not claims. An autonomous, multi-tenant, AI-native software factory Most AI tools tell you what they did. Eva writes it down first. Every question you ask, every answer that comes back, every retry, and every token counted is appended to a file on your disk as it happens. What you see on screen is read back out of that file. If Eva shows you an answer, the file already had it. There is no second version of events. That sounds like a small thing. It is the whole design. What it looks like $ eva EVA Evidence, not claims version 0.1.0+e839c8a model claude-sonnet-4-5 branch main cwd ~/code/eva type /help for slash commands › what's the difference between a cache write and a cache read? A cache write stores your prompt prefix so later calls can skip re-reading it.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at GitHub.