<?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>SDD on yishiashia's Blog</title><link>https://yishiashia.github.io/tags/sdd/</link><description>Recent content in SDD on yishiashia's Blog</description><generator>Hugo -- gohugo.io</generator><language>zh-TW</language><copyright>Copyright © 2023 yishiashia@gmail.com. All rights reserved.</copyright><lastBuildDate>Thu, 10 Sep 2026 21:45:00 +0800</lastBuildDate><atom:link href="https://yishiashia.github.io/tags/sdd/index.xml" rel="self" type="application/rss+xml"/><item><title>[AI 軟體工程] 規格即合約：把「要做什麼」固定成可驗證的版本基準</title><link>https://yishiashia.github.io/posts/spec-as-contract/</link><pubDate>Thu, 10 Sep 2026 21:45:00 +0800</pubDate><guid>https://yishiashia.github.io/posts/spec-as-contract/</guid><description>在 harness engineering 的信任鏈裡，第一環是「合約」。本文從規格漂移談起，說明如何透過 DECLARE 與 BIND，把需求、非目標與架構決策固定成可對帳的版本基準，並釐清數位指紋、數位簽署與授權之間的差異。</description></item></channel></rss>