<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Signatures on Programmer.ie</title>
    <link>http://programmer.ie/tags/signatures/</link>
    <description>Recent content in Signatures on Programmer.ie</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Fri, 28 Aug 2026 10:10:00 +0100</lastBuildDate>
    <atom:link href="http://programmer.ie/tags/signatures/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>DSPy From First Principles 02: A Prompt Is Not Yet a Program</title>
      <link>http://programmer.ie/books/dspy-from-first-principles/02-chapter/</link>
      <pubDate>Fri, 28 Aug 2026 10:05:00 +0100</pubDate>
      <guid>http://programmer.ie/books/dspy-from-first-principles/02-chapter/</guid>
      <description>&lt;h1 id=&#34;a-prompt-is-not-yet-a-program&#34;&gt;A Prompt Is Not Yet a Program&lt;/h1&gt;&#xA;&lt;p&gt;In chapter 1 we built a reasonable handwritten prompt and found the real problem: one prompt string was carrying the task semantics, role and behavioral framing, output request, and model assumptions at the same time.&lt;/p&gt;&#xA;&lt;p&gt;The next move is not to make a more elaborate prompt. It is to decide what properties an LM component needs before we should reasonably call it a program.&lt;/p&gt;</description>
    </item>
    <item>
      <title>DSPy From First Principles 03: Define the Contract</title>
      <link>http://programmer.ie/books/dspy-from-first-principles/03-chapter/</link>
      <pubDate>Fri, 28 Aug 2026 10:10:00 +0100</pubDate>
      <guid>http://programmer.ie/books/dspy-from-first-principles/03-chapter/</guid>
      <description>&lt;h1 id=&#34;define-the-contract&#34;&gt;Define the Contract&lt;/h1&gt;&#xA;&lt;p&gt;In chapter 2 we stopped treating the prompt string as the program. We defined a small DSPy module around a signature:&lt;/p&gt;&#xA;&lt;div class=&#34;highlight&#34;&gt;&lt;pre tabindex=&#34;0&#34; style=&#34;color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;&#34;&gt;&lt;code class=&#34;language-text&#34; data-lang=&#34;text&#34;&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;sentence&#xA;&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;editorial_goal&#xA;&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;local_context&#xA;&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;    ↓&#xA;&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;rewritten_text&#xA;&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;rationale&#xA;&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;confidence&#xA;&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;p&gt;That is better than a handwritten prompt, but it raises the next problem. The program boundary is only as good as the contract we put at that boundary.&lt;/p&gt;&#xA;&lt;p&gt;This chapter is about signatures from first principles. A signature is not a prompt template. It is a task contract.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
