<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"><channel><title>Derek Niedringhaus — Writing</title><description>Essays on object thinking, design systems for the AI era, and how systems encode meaning.</description><link>https://derekn.com/</link><language>en-us</language><item><title>Object-Native Architecture: Giving Software a Meaning Layer</title><link>https://derekn.com/writing/object-native-architecture/</link><guid isPermaLink="true">https://derekn.com/writing/object-native-architecture/</guid><description>Software was built for a human reader who could fill in the blanks. Agents can&apos;t. So an object&apos;s identity, its governance, and the contracts it answers to have to live on the object itself, in something built to be read. An architecture problem, not a model problem.</description><pubDate>Sun, 31 May 2026 00:00:00 GMT</pubDate><category>agents</category><category>design-systems</category><category>protocols</category><category>governance</category><category>ai-tooling</category></item></channel></rss>