<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Instructional Segment Embedding: Improving LLM Safety with Instruction Hierarchy · HackerPapers discussions</title><link>https://hackerpaper.kaipfister.de/p/2410.09102/</link><description>Collected HN comments and submissions linking this paper.</description><language>en</language><lastBuildDate>Mon, 02 Nov 2026 11:16:22 GMT</lastBuildDate><atom:link href="https://hackerpaper.kaipfister.de/p/2410.09102/feed.xml" rel="self" type="application/rss+xml" /><item><title>Instructional Segment Embedding: Improving LLM Safety with Instruction Hierarchy — mentioned by plaidthunder</title><link>https://news.ycombinator.com/item?id=48633815</link><guid isPermaLink="false">urn:hackerpapers:mention:2410.09102:48633815</guid><pubDate>Mon, 22 Jun 2026 18:15:42 GMT</pubDate><description>&lt;p&gt;It seems like there&amp;#x27;s an opportunity to embed identity information into tokens themselves, the way we embed sequence information. The trouble is... it&amp;#x27;s quite a challenge to train. Sequence is easy to derive for any corpus of data, but identity is not. https://usize.github.io/blog/2026/april/why-no-ai-coworkers.... &amp;gt; In similar fashion to how sequence information is embedded within input tensors, an approach called “Instructional Segment Embedding”2 adds a parallel embedding channel for identity information. This gives models real awareness of provenance. And it works. But they only tested…&lt;/p&gt;&lt;p&gt;&lt;a href="https://hackerpaper.kaipfister.de/p/2410.09102/"&gt;Paper and discussion history&lt;/a&gt;. A mention is not an endorsement.&lt;/p&gt;</description><category>cs.LG</category></item><item><title>Instructional Segment Embedding: Improving LLM Safety with Instruction Hierarchy — mentioned by alexbecker</title><link>https://news.ycombinator.com/item?id=45006956</link><guid isPermaLink="false">urn:hackerpapers:mention:2410.09102:45006956</guid><pubDate>Sun, 24 Aug 2025 19:30:02 GMT</pubDate><description>&lt;p&gt;There have been attempts like https://arxiv.org/pdf/2410.09102 to do this kind of color-coding but none of them work in a multi-turn context since as you note you can&amp;#x27;t trust the previous turn&amp;#x27;s output&lt;/p&gt;&lt;p&gt;&lt;a href="https://hackerpaper.kaipfister.de/p/2410.09102/"&gt;Paper and discussion history&lt;/a&gt;. A mention is not an endorsement.&lt;/p&gt;</description><category>cs.LG</category></item></channel></rss>
