<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"><channel><title>Luvian Blog</title><description>Insights on MBSE, systems engineering, AI-driven design, and the future of complex system delivery.</description><link>https://luvian.io/</link><item><title>What Comes Next: A Practitioner&apos;s Manifesto for MBSE 2.0</title><link>https://luvian.io/blog/practitioners-manifesto-mbse-2/</link><guid isPermaLink="true">https://luvian.io/blog/practitioners-manifesto-mbse-2/</guid><description>MBSE 2.0 isn&apos;t a new standard or a new tool - it&apos;s a set of principles the industry must adopt to move past the current crisis. A manifesto for practitioners, by practitioners. This is Part 10 of The MBSE Reckoning.</description><pubDate>Mon, 22 Jun 2026 00:00:00 GMT</pubDate><category>MBSE</category><category>Systems Engineering</category><category>Digital Engineering</category><category>SysML v2</category><category>Manifesto</category><author>Luvian Team</author></item><item><title>Models That Run: The Case for Executable System Architecture</title><link>https://luvian.io/blog/models-that-run/</link><guid isPermaLink="true">https://luvian.io/blog/models-that-run/</guid><description>The endgame isn&apos;t better documentation. It&apos;s models that are operational infrastructure - version-controlled, diffable, integrated into CI/CD, generating downstream artifacts. This is Part 9 of The MBSE Reckoning.</description><pubDate>Mon, 15 Jun 2026 00:00:00 GMT</pubDate><category>MBSE</category><category>Digital Twin</category><category>SysML v2</category><category>CI/CD</category><category>Systems Engineering</category><category>Executable Models</category><author>Luvian Team</author></item><item><title>AI Won&apos;t Save MBSE - But It Might Make It Usable</title><link>https://luvian.io/blog/ai-wont-save-mbse/</link><guid isPermaLink="true">https://luvian.io/blog/ai-wont-save-mbse/</guid><description>AI is the most-cited hope for MBSE&apos;s future, but &apos;AI-powered MBSE&apos; is mostly marketing in 2026. What AI CAN do is solve the accessibility crisis. This is Part 8 of The MBSE Reckoning.</description><pubDate>Mon, 08 Jun 2026 00:00:00 GMT</pubDate><category>MBSE</category><category>AI</category><category>Machine Learning</category><category>Systems Engineering</category><category>SysML v2</category><category>LLM</category><author>Luvian Team</author></item><item><title>Intent Doesn&apos;t Survive the Pipeline (And That&apos;s the Real Problem)</title><link>https://luvian.io/blog/intent-doesnt-survive-the-pipeline/</link><guid isPermaLink="true">https://luvian.io/blog/intent-doesnt-survive-the-pipeline/</guid><description>All five gripes are symptoms of one structural failure: intent degrades at every handoff in the engineering pipeline. At each boundary, the &apos;why&apos; gets stripped away, leaving only the &apos;what.&apos; This is Part 7 of The MBSE Reckoning.</description><pubDate>Mon, 01 Jun 2026 00:00:00 GMT</pubDate><category>MBSE</category><category>Product Management</category><category>Intent Engineering</category><category>Systems Engineering</category><category>Digital Engineering</category><author>Luvian Team</author></item><item><title>The Priesthood Problem: MBSE&apos;s Stakeholder Visibility Crisis</title><link>https://luvian.io/blog/the-priesthood-problem/</link><guid isPermaLink="true">https://luvian.io/blog/the-priesthood-problem/</guid><description>MBSE was supposed to be the single source of truth. Instead, it created a priesthood - a small group who can read the models - and everyone else gets PowerPoint translations. This is Part 6 of The MBSE Reckoning.</description><pubDate>Mon, 25 May 2026 00:00:00 GMT</pubDate><category>MBSE</category><category>Stakeholder Management</category><category>Systems Engineering</category><category>Program Management</category><category>Digital Engineering</category><author>Luvian Team</author></item><item><title>Two Tribes: Why Systems Engineers and Developers Can&apos;t Hear Each Other</title><link>https://luvian.io/blog/two-tribes/</link><guid isPermaLink="true">https://luvian.io/blog/two-tribes/</guid><description>Systems engineering and software engineering evolved as separate disciplines with separate toolchains, cultures, and value systems. The gap isn&apos;t tooling - it&apos;s ontological. This is Part 5 of The MBSE Reckoning.</description><pubDate>Mon, 18 May 2026 00:00:00 GMT</pubDate><category>MBSE</category><category>Software Engineering</category><category>Systems Engineering</category><category>SysML v2</category><category>DevOps</category><author>Luvian Team</author></item><item><title>The Maturity Myth: Why Nobody Knows Where They Are</title><link>https://luvian.io/blog/the-maturity-myth/</link><guid isPermaLink="true">https://luvian.io/blog/the-maturity-myth/</guid><description>Both tool builders and tool adopters are flying blind. Vendors ship features without acceptance criteria. Organizations adopt MBSE without maturity models. This is Part 4 of The MBSE Reckoning.</description><pubDate>Mon, 11 May 2026 00:00:00 GMT</pubDate><category>MBSE</category><category>Maturity Model</category><category>SysML v2</category><category>Product Management</category><category>Systems Engineering</category><author>Luvian Team</author></item><item><title>The Shelfware Problem: When Models Don&apos;t Connect to Work</title><link>https://luvian.io/blog/the-shelfware-problem/</link><guid isPermaLink="true">https://luvian.io/blog/the-shelfware-problem/</guid><description>When the model isn&apos;t connected to the actual work, it becomes shelfware: a document nobody reads, written in a language nobody speaks. This is Part 3 of The MBSE Reckoning.</description><pubDate>Mon, 04 May 2026 00:00:00 GMT</pubDate><category>MBSE</category><category>Digital Thread</category><category>Integration</category><category>Systems Engineering</category><category>Digital Engineering</category><author>Luvian Team</author></item><item><title>Your MBSE Tool Was Designed for the Wrong Person</title><link>https://luvian.io/blog/your-mbse-tool-was-designed-for-the-wrong-person/</link><guid isPermaLink="true">https://luvian.io/blog/your-mbse-tool-was-designed-for-the-wrong-person/</guid><description>MBSE tools optimize for ontological completeness, not for the act of engineering. The result is tools inaccessible to 90% of the people who need system data. This is Part 2 of The MBSE Reckoning.</description><pubDate>Fri, 24 Apr 2026 00:00:00 GMT</pubDate><category>MBSE</category><category>UX</category><category>Systems Engineering</category><category>SysML v2</category><category>Tooling</category><author>Luvian Team</author></item><item><title>The MBSE Reckoning: Why the Industry Is at a Breaking Point</title><link>https://luvian.io/blog/the-mbse-reckoning/</link><guid isPermaLink="true">https://luvian.io/blog/the-mbse-reckoning/</guid><description>MBSE has won the argument. Everyone agrees models beat documents. But the tools, practices, and organizational structures around it are failing practitioners. This is Part 1 of a 10-part series on what&apos;s broken, what&apos;s possible, and what comes next.</description><pubDate>Fri, 10 Apr 2026 00:00:00 GMT</pubDate><category>MBSE</category><category>Systems Engineering</category><category>Digital Engineering</category><category>SysML v2</category><author>Luvian Team</author></item></channel></rss>