My AI Wishlist
My AI Wishlist Compared to my post on AI coding milestones, this is a bit more general on tooling + interfaces that might exist someday… I just wish they existed today. Business Logic Verification Many people are interested in formal verification, like TLA+, Lean, or Rocq. That’s great for proofs, cryptography, and llm training data, but not useful for most engineers.
- ▪My AI Wishlist Compared to my post on AI coding milestones, this is a bit more general on tooling + interfaces that might exist someday… I just wish they existed today.
- ▪Business Logic Verification Many people are interested in formal verification, like TLA+, Lean, or Rocq.
- ▪That’s great for proofs, cryptography, and llm training data, but not useful for most engineers.
Hacker News (AI / LLM) files mainly under ai. We currently carry 3,083 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 | Diverging Run |
| Canonical URL | https://diverging.run/checkpoints/ai-coding-wishlist/ |
| Publication time | Thu, 30 Jul 2026 14:38:53 +0000 |
| Retrieval time | 2026-07-30T14:42:06.611Z |
| Last seen | 2026-07-30T14:42:06.611Z |
| 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 | None |
| Cluster logic | Not yet clustered, or no peer story found in the clustering window. |
| 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
My AI Wishlist Compared to my post on AI coding milestones, this is a bit more general on tooling + interfaces that might exist someday… I just wish they existed today. Business Logic Verification Many people are interested in formal verification, like TLA+, Lean, or Rocq. That’s great for proofs, cryptography, and llm training data, but not useful for most engineers. What I actually need, day-to-day, is verifying business logic. This is much harder because “business logic” is famously squishy. Even if you did translate all your business logic into Lean, few would be able to read it let alone debug it. In an ideal world, “tests” would look like business requirements that are evaluated regularly across code (and perhaps proactively on metrics).
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at Diverging Run.
Discussion
0 commentsMore from Diverging Run
