<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Streamlit | Stefano Blando</title><link>https://stefano-blando.github.io/en/tags/streamlit/</link><atom:link href="https://stefano-blando.github.io/en/tags/streamlit/index.xml" rel="self" type="application/rss+xml"/><description>Streamlit</description><generator>HugoBlox Kit (https://hugoblox.com)</generator><language>en-US</language><lastBuildDate>Sun, 15 Mar 2026 00:00:00 +0000</lastBuildDate><image><url>https://stefano-blando.github.io/media/icon_hu_8d0dee6c10a3c598.png</url><title>Streamlit</title><link>https://stefano-blando.github.io/en/tags/streamlit/</link></image><item><title>RiskSentinel - Agentic Systemic Risk Simulator</title><link>https://stefano-blando.github.io/en/projects/risk-sentinel/</link><pubDate>Sun, 15 Mar 2026 00:00:00 +0000</pubDate><guid>https://stefano-blando.github.io/en/projects/risk-sentinel/</guid><description>&lt;p&gt;RiskSentinel is an &lt;strong&gt;agentic systemic risk simulator&lt;/strong&gt; built around a question I find both practical and conceptually interesting: if a large financial node is hit by a shock, how can we make the propagation of that stress visible, comparable, and explainable in real time?&lt;/p&gt;
&lt;p&gt;Built for the &lt;strong&gt;Microsoft AI Dev Days Hackathon 2026&lt;/strong&gt;, the project combines three contagion models, topology-aware analytics, and a bounded multi-agent workflow on top of research-grade market network data. The purpose is not only to simulate cascades, but to make them easier to inspect through natural-language interaction, interactive visualization, and model comparison.&lt;/p&gt;
&lt;p&gt;What makes the project work is the combination of several layers that are often separated: a proper network simulation engine, an interface that makes the results explorable, and an agentic layer that helps interpret what is happening without pretending to replace the underlying quantitative machinery.&lt;/p&gt;
&lt;p&gt;The result is a practical prototype for &lt;strong&gt;systemic risk monitoring&lt;/strong&gt;, sitting between quantitative finance, complex systems, and AI-assisted decision support.&lt;/p&gt;
&lt;p&gt;You can explore the project here:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;
&lt;/strong&gt;&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;
&lt;/strong&gt;&lt;/li&gt;
&lt;/ul&gt;</description></item><item><title>RiskSentinel for Microsoft AI Dev Days 2026</title><link>https://stefano-blando.github.io/en/blog/microsoft-ai-dev-days-risksentinel/</link><pubDate>Sun, 15 Mar 2026 00:00:00 +0000</pubDate><guid>https://stefano-blando.github.io/en/blog/microsoft-ai-dev-days-risksentinel/</guid><description>&lt;p&gt;&lt;strong&gt;RiskSentinel&lt;/strong&gt; is the project I built for the &lt;strong&gt;Microsoft AI Dev Days Hackathon 2026&lt;/strong&gt;.&lt;/p&gt;
&lt;p&gt;The core idea was to create a system that could make systemic risk more explorable and more tangible: instead of treating contagion as an abstract output in a paper or a notebook, I wanted an interface where shocks could be launched, propagated, compared, and interpreted in real time.&lt;/p&gt;
&lt;p&gt;The project combines &lt;strong&gt;network science&lt;/strong&gt;, &lt;strong&gt;contagion modeling&lt;/strong&gt;, and &lt;strong&gt;agentic AI&lt;/strong&gt; on top of research-grade financial network data covering &lt;strong&gt;210 S&amp;amp;P 500 stocks&lt;/strong&gt; and &lt;strong&gt;3,081 daily snapshots&lt;/strong&gt;. Under the hood, it integrates three propagation models, interactive network analytics with Streamlit and Plotly, and an agentic workflow built with &lt;strong&gt;Microsoft Agent Framework&lt;/strong&gt; and &lt;strong&gt;Azure OpenAI&lt;/strong&gt;.&lt;/p&gt;
&lt;p&gt;What I like most about this project is that it sits exactly at the boundary between my research interests and practical prototyping: financial networks, complex systems, decision support, and AI agents all in the same tool.&lt;/p&gt;
&lt;p&gt;👉 &lt;strong&gt;
&lt;/strong&gt;&lt;br&gt;
GitHub: &lt;strong&gt;
&lt;/strong&gt;&lt;br&gt;
App: &lt;strong&gt;
&lt;/strong&gt;&lt;/p&gt;</description></item><item><title>PokéNexus</title><link>https://stefano-blando.github.io/en/projects/pokenexus/</link><pubDate>Wed, 04 Feb 2026 00:00:00 +0000</pubDate><guid>https://stefano-blando.github.io/en/projects/pokenexus/</guid><description>&lt;p&gt;&lt;strong&gt;PokéNexus&lt;/strong&gt; was born from something very simple: I have loved Pokémon since I was a child, and at some point I wanted to merge that world with the kind of tools and ideas I now enjoy building with.&lt;/p&gt;
&lt;p&gt;The result is a Streamlit app that turns the Pokémon universe into an interactive space where &lt;strong&gt;graph visualization&lt;/strong&gt;, &lt;strong&gt;game mechanics&lt;/strong&gt;, and &lt;strong&gt;API-driven data&lt;/strong&gt; come together. I used &lt;strong&gt;NetworkX&lt;/strong&gt;, &lt;strong&gt;PyVis&lt;/strong&gt;, and &lt;strong&gt;Plotly&lt;/strong&gt; to explore relationships between types and entities, while &lt;strong&gt;PokeAPI&lt;/strong&gt; provides the live data layer for creatures, evolutions, and related information.&lt;/p&gt;
&lt;p&gt;Instead of being just a static graph, the project grew into a small playable system: teams can be managed, items stored, badges collected, and different progression loops layered on top of the visualization. That mix of structure, exploration, and play is exactly what made the project fun to build.&lt;/p&gt;
&lt;p&gt;It is not a research project, and it is not meant to be. It is a personal experiment where a childhood passion meets the way I now think about &lt;strong&gt;networks&lt;/strong&gt;, &lt;strong&gt;interfaces&lt;/strong&gt;, and &lt;strong&gt;interactive Python applications&lt;/strong&gt;.&lt;/p&gt;</description></item></channel></rss>