<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Projects on Embedded Leadership</title><link>https://embedded-leadership.com/projects/</link><description>Recent content in Projects on Embedded Leadership</description><generator>Hugo -- gohugo.io</generator><language>en</language><copyright>© 2026 Christophe Le Douarec</copyright><lastBuildDate>Sat, 11 Apr 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://embedded-leadership.com/projects/index.xml" rel="self" type="application/rss+xml"/><item><title>SARA</title><link>https://embedded-leadership.com/projects/sara/</link><pubDate>Sat, 11 Apr 2026 00:00:00 +0000</pubDate><guid>https://embedded-leadership.com/projects/sara/</guid><description>&lt;p&gt;SARA (Solution Architecture Requirement for Alignment) addresses a common
challenge in complex organizations: requirements and architecture documents
scattered across teams, repositories, and formats — making traceability painful
and consistency almost impossible.&lt;/p&gt;
&lt;p&gt;SARA aggregates documents from multiple Git repositories into a unified
knowledge graph, connecting business needs to implementation details through a
clear hierarchy: solutions, use cases, scenarios, system requirements,
architecture, and detailed designs.&lt;/p&gt;
&lt;p&gt;Key capabilities:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Validation&lt;/strong&gt; — detect broken references, circular dependencies, orphans,
and duplicates&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Traceability&lt;/strong&gt; — query upstream toward business needs or downstream toward
implementation&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Reporting&lt;/strong&gt; — generate coverage reports and traceability matrices&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Comparison&lt;/strong&gt; — diff knowledge graphs between commits or branches&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;AI agent workflow&lt;/strong&gt; — serve as a knowledge base for AI agents and leverage
them to generate or refine requirements and documentation&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;The approach: plain markdown files with YAML metadata. No vendor lock-in, full
version control, code review friendly, and ready for AI integration.&lt;/p&gt;</description></item></channel></rss>