<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Platform Engineering on Cliff Hults</title><link>https://www.haguest.com/tags/platform-engineering/</link><description>Recent content in Platform Engineering on Cliff Hults</description><generator>Hugo -- gohugo.io</generator><language>en</language><copyright>© 2026 Cliff Hults</copyright><lastBuildDate>Sun, 20 Sep 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://www.haguest.com/tags/platform-engineering/index.xml" rel="self" type="application/rss+xml"/><item><title>Designing an Automated Artifact Factory: A Case Study in Turning Pipeline Pain Into a Platform Boundary</title><link>https://www.haguest.com/posts/2026-09-20-automated-artifact-factory/</link><pubDate>Sun, 20 Sep 2026 00:00:00 +0000</pubDate><guid>https://www.haguest.com/posts/2026-09-20-automated-artifact-factory/</guid><description>&lt;p>Every team wiring the same three security checks into its own pipeline isn&amp;rsquo;t really a security problem. It&amp;rsquo;s a platform problem wearing a security costume.&lt;/p>
&lt;p>This is the story of how we traced that pattern back to a structural issue, and the design we landed on to fix it: an automated artifact factory that turns signing, vulnerability scanning, and antivirus scanning from something every team bolts onto their own pipeline into something the platform just does for them.&lt;/p></description></item></channel></rss>