https://shenxianpeng.dev/series/open-delivery-spec/Recent content in Open Delivery Spec on Xianpeng ShenHugo -- gohugo.ioenxianpeng.shen@gmail.com (Xianpeng Shen)xianpeng.shen@gmail.com (Xianpeng Shen)Copyright © 2017–2026 Xianpeng Shen. All rights reserved.Sat, 08 Aug 2026 00:00:00 +0000https://shenxianpeng.dev/posts/2026/open-delivery-spec-update/Sat, 08 Aug 2026 00:00:00 +0000xianpeng.shen@gmail.com (Xianpeng Shen)https://shenxianpeng.dev/posts/2026/open-delivery-spec-update/Three weeks ago I introduced Open Delivery Spec (ODS), my side project for governing AI-assisted code in CI. Since then the CLI has shipped 5 releases and grown two new pillars: deterministic merge-confidence signals that answer “is this AI PR safe to merge?”, and an auto-generated, standards-based evidence document on every PR. As always, this post sticks to what actually ships — no hype.https://shenxianpeng.dev/posts/2026/open-delivery-spec/Fri, 17 Jul 2026 00:00:00 +0000xianpeng.shen@gmail.com (Xianpeng Shen)https://shenxianpeng.dev/posts/2026/open-delivery-spec/Over the past few months, I’ve been working on an open-source organization called Open Delivery Spec (ODS) in my spare time. The initiative stemmed from the increasing volume of AI-generated code and the lack of reliable governance mechanisms within teams. This article records the thought process, progress, and boundaries based on the project’s real-world status, without any exaggeration.