<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Verification on strall.com</title>
    <link>/tags/verification/</link>
    <description>Recent content in Verification on strall.com</description>
    <generator>Hugo -- 0.148.1</generator>
    <language>en-us</language>
    <lastBuildDate>Fri, 09 Oct 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="/tags/verification/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Building Agent-First Systems That Learn From Evidence</title>
      <link>/posts/building-agent-first-systems-that-learn-from-evidence/</link>
      <pubDate>Fri, 09 Oct 2026 00:00:00 +0000</pubDate>
      <guid>/posts/building-agent-first-systems-that-learn-from-evidence/</guid>
      <description>&lt;p&gt;Agent-first engineering begins with human intent. Agents help translate that intent into systems through a deliberate sequence:&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Human intent → specification → architecture → implementation → verification → evidence → human review → deployment.&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;Each stage produces something inspectable: requirements, design decisions, code, test results, deployment plans, and operational observations. Humans retain authority over consequential changes. Evidence makes that review concrete.&lt;/p&gt;
&lt;p&gt;The sequence also needs feedback. A failed test may expose a design assumption. A deployment plan may reveal a missing permission or an unclear ownership boundary. An operational result may show that the specification defined success too narrowly.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
