 Okay. I am back. Hello everybody. I realized that I probably didn't introduce myself earlier. My name is Evan Gilman. I am one of the maintainers on the Spiffy Inspire projects. So I, you know, I'm just trying to kind of help facilitate today, give the opening remarks, and I'll kind of kick off the day of talks here with an update on the Spiffy project. Earlier, I described some of the velocity, like high level velocity and growth metrics, adoption metrics from the Spiffy project as a whole. This is going to be a little bit more zoomed in on specific things and activities that we've done over the last year and where we've come from. So when I was doing these slides and I looked back on the last year and I was thinking of like, you know, what themes are there? The only thing that I could really come to my mind is this idea of stabilization or maturation. The last year in Spiffy, both the Spiffy project itself, the specification set and across all the sub-projects including Spire. The last year has been a lot of kind of like standing down rough edges, making it more usable, making it more performant, making it more stable, all that kind of stuff. You know, in the past years, we've had big announcements like new specs coming out and new things like that. This year, we had a little bit of that, but it was mostly around stabilization. So what do I mean by that? I think probably the biggest and most meaningful part of this stabilization story is all the governance work that we've done over the last one year. This is really, really, really, really important and critical to Spiffy Inspire as a whole. It's kind of this dirty work that nobody wants to do, but it must be done because if you cannot show continuity, business continuity in the project, if you cannot make people feel that, hey, this thing is here, it will be supported if something happens, I can rely on it, how can you adopt it in any meaningful fashion if you cannot depend on a project in this way. So having that governance be really, really strong, having strong bust factor, having good rules in place and policies and the good structure, all that stuff is critically important. So in that, you know, we did a lot of things in that of that ilk in the last one year. One of them was that we renewed the charter or actually wrote, wrote charter for the TSC. You know, this group is a group of people that have oversight over all kind of the Spiffy Inspire sub-projects. Oversight is not maybe not the right word, but they're there to help support the projects. They're there to help connect people, to help spot gaps. They're there to help unblock, they're there to help facilitate across all the Spiffy projects as a whole. One way to think of them is kind of like the CNCF talk. CNCF talk as it is to CNCF projects is a similar body there to service Spiffy and its sub-projects. So we put this new charter in place that defines, you know, the mission, exactly what this group is going to be responsible for and how to get on it and people who are on it, what all the responsibilities for them are and is all clearly codified. So that was a pretty big, pretty big deal for us. People with sharp eyes may have noticed in that last screenshot that one of those changes was that we actually renamed the group. Oh no. I'll go back.