SovereignFlow gets its own repository
I separated a domain-neutral RAG foundation with a document model, pipelines, APIs, and no code-analysis assumptions. The repository also includes audit, ingestion, and authorization code.
View source ↗A dated record of development milestones, based on GitHub history and published architecture decisions.

Why I am building my own DataGrid and what the current WPF and Avalonia implementations can actually do. Screenshots, architecture, and release plans.
Read article ↗I separated a domain-neutral RAG foundation with a document model, pipelines, APIs, and no code-analysis assumptions. The repository also includes audit, ingestion, and authorization code.
View source ↗I documented the decision: LocalAI-RAG stays focused on code analysis, while domain-specific assistants receive a separate core. TaricAI was the first planned validation.
View source ↗I created the public repository for PhialeGis, DSL work, and desktop components. The code remains proprietary.
View source ↗A repository change introduced SQL history and security scripts, ACL validation, and UI settings cleanup.
View source ↗I started a tool for inspecting rendered prompts and pipeline traces; subsequent commits added Trace Explorer and diagrams.
View source ↗I opened the repository for local code analysis with RAG. Later work expanded pipelines, access control, and snapshots.
View source ↗I began public development of the .NET indexer. Later iterations added SQL/EF graphs, migrations, and support for multiple .NET environments.
View source ↗I created the PhialeGis repository (private). The first changes covered the project structure and themes for the base visual control.
I publish longer technical reflections on architecture, AI engineering, experiments, and the choices behind my own software. The newsletter lives on LinkedIn; NeptunTech links to the original articles.