'Who's on First' for AI Risk?
AI AI Risk – a User’s Guide (Part II): ‘Who’s on First’ for AI Risk? It is the same logic that’s worked for decades with traditional software procurement where you buy the license, the vendor is liable for defects, you move on. I want to walk through why that story doesn’t hold for AI systems, and why the legal reality is far messier and far more your problem than most procurement teams currently assume.
- ▪AI AI Risk – a User’s Guide (Part II): ‘Who’s on First’ for AI Risk?
- ▪It is the same logic that’s worked for decades with traditional software procurement where you buy the license, the vendor is liable for defects, you move on.
- ▪I want to walk through why that story doesn’t hold for AI systems, and why the legal reality is far messier and far more your problem than most procurement teams currently assume.
Hacker News (AI / LLM) files mainly under ai. We currently carry 4,777 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 | Home: sdarchitect.blog |
| Canonical URL | https://sdarchitect.blog/2026/09/13/ai-risk-a-users-guide-part-ii-whos-on-first-for-ai-risk/ |
| Publication time | Mon, 14 Sep 2026 11:16:45 +0000 |
| Retrieval time | 2026-09-14T11:21:51.259Z |
| Last seen | 2026-09-14T11:21:51.259Z |
| 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
AI AI Risk – a User’s Guide (Part II): ‘Who’s on First’ for AI Risk? Posted by Sanjeev Sharma on September 13, 2026September 13, 2026 Buying the AI Doesn’t Transfer the Risk There is a comforting story a lot of enterprises tell themselves when they adopt a third-party AI tool: “we bought this from a reputable vendor who has indemnified us in their contract, so the vendor owns the risk.” I understand the appeal of that story. It is the same logic that’s worked for decades with traditional software procurement where you buy the license, the vendor is liable for defects, you move on. I want to walk through why that story doesn’t hold for AI systems, and why the legal reality is far messier and far more your problem than most procurement teams currently assume.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at Home: sdarchitect.blog.
Discussion
0 commentsMore from Home: sdarchitect.blog
