Hello, my name is Bessam Tabara and I am the CEO and founder of UpBound and one of the creators of the Crospine project. I thought a good way to kick things off today is to start with the origin story of Crospine, which goes back to 2017. This was the year that Kubernetes won the Container Orchestration Wars. While Kubernetes is known for being the gold standard in container orchestration, I don't believe managing containers is its true superpower. Nor do I believe it's the primary reason that it won. I believe Kubernetes won because it defined a new operating model for managing applications and infrastructure. And it did so with a strong ecosystem and a community-driven approach to open source. We were inspired by this approach and I wanted to walk through each of these from a perspective of Crospine. Let's start with the operating model. There are several properties of Kubernetes you probably take for granted today, but have played a critical role in the project's success. The first property is that you interact with Kubernetes through a RESTful API. This seems so obvious, but it's a far departure from other tooling in this space, especially infrastructure as code tooling that expects templates or programs. The Kubernetes API exposes an independent RESTful endpoint for each resource it manages. Authorization, access control, and other policies can all be enforced centrally and at a granularity of a single resource. Because it's an API, users can pick any language, tool, or framework to interact with it. APIs offer the greatest levels of interoperability and have fostered the largest of ecosystems. The second property is how the Kubernetes API was designed for two personas. Platform engineers who have an intimate knowledge of infrastructure and application engineers who have intimate knowledge of their applications. This separation of concerns leads to organizational efficiencies and scale. Application teams use simpler abstracted APIs like POD and persistent volume claim, while platform teams use full APIs like nodes and volumes. Both teams use human workflows to arrive at their configuration. Storing configuration in Git has become an industry standard, and doing so enables teams to use pull request flows and source management tools for collaboration. With Kubernetes, configurations can be authored via YAML, programming languages, or templates. It really doesn't matter because they all result in the same API calls. All automation, operational, and business policies live behind the API line. Kubernetes APIs follow a thin crud approach and merely manipulate declarative configuration within the config store. These API calls do not perform any synchronous provisioning or deployment acts. Once the declarative configuration is updated, this marks the end of human-based workflows. From this point onwards, controllers are activated asynchronously to read the declarative configuration and act autonomously to implement it. These controllers are rooted in control theory and are in a continuous loop, reading declarative state, observing actual state, and reconciling the two. This is why we call it a control plane. Importantly, human operators are not involved in this Reconciliation Act, a major departure from other approaches that require humans to approve plans, handle drift, and require other systems for monitoring and observability. With this new operating model, organizations can achieve a high degree of automation, once reserved for hyperscale cloud providers. This democratization and implementation of control theory is the reason Kubernetes won the container wars. We started cross-plane because early on we saw the power of this operating model and wanted to take it beyond container orchestration. We believe containers are simply the first use case of this operating model and that this operating model is applicable to the management of all applications and infrastructure. Cross-plane makes that happen. It extends Kubernetes by adding APIs and controllers that enable it to manage resources and services from multiple cloud and infrastructure vendors. Platform teams and application teams can now simply author configurations for databases, caches, networking, and other services. Configurations are continuously reconciled by cross-plane and day one and day two automation is handled out of the box. With Kubernetes and cross-plane, we see the industry moving off of infrastructure as code tooling and onto control planes. While projects like Terraform have been wildly successful, we are starting to see their limitations. Organizing teams around templates has not proven effective. Templates are a much weaker form or much weaker contract than APIs or data. IAC tooling focuses on initial provisioning and requires humans to approve execution plans and that does not scale. The lack of access control has also proven problematic, requiring organizations to create artificial templates to represent team boundaries. Lastly, the lack of API and the vendor-driven nature of these projects has limited the ecosystem around them. Within the cross-plane community, we are starting to see many companies replacing their IAC footprint with cross-plane. Some of these companies will be speaking here today. Control planes offer a declarative API that promotes interoperability and results in a much larger ecosystem. The separation of concerns enables self-service and controllers enable full automation scenarios and avoid the drift. We see cross-plane and Kubernetes ushering a new era of application and infrastructure management that will lead to a much higher degree of self-service and automation. These are the prerequisites to increasing the pace of innovation within most organizations. To usher in this new era of automation, we are investing in formalizing the underpinnings of cross-plane in the same way that Kubernetes has formalized the Kubernetes resource model or KRM. Cross-plane defines a strict extension of KRM that we empathetically call the cross-plane resource model or XRM. It captures the lessons learned within the community in managing external resources. It deals with mixed external naming, identity, adoption of existing resources. It includes cross-resource references, handling connection secrets, and credentials. Composition is the popular feature that enables platform teams to define new self-service APIs for their application teams. And finally, a package manager designed for cross-plane scenarios. Building all of this takes a village and we have been humbled by the ecosystem we're seeing emerge around the cross-plane project. Part of this is due to the fact that if your tooling works with Kubernetes, it will automatically work with cross-plane. But we're starting to see tooling emerge, which relies not just on the KRM, but also on XRM. In terms of cross-plane providers, the community started by bootstrapping the major cloud providers ourselves, but have now transitioned to working directly with the cloud providers and other infrastructure vendors. Our approach has us generating cross-plane providers from their back-end SDKs, and we are doing that successfully right now with AWS and Azure, with more coming on the way. Vendors like IBM Cloud have authored their own native cross-plane providers and are maintaining them. Finally, we've recently added support to generate cross-plane providers from Terraform providers, bringing the entire Terraform ecosystem to cross-plane. To ensure the ecosystem remains healthy as it grows, the cross-plane community applied to start a conformance program for cross-plane. This program is still subject to the CNCF governing board approval and will be run by the CNCF. There are two levels in this program. The first is for distributions of cross-plane. This level is for vendors that plan to incorporate cross-plane into their commercial offerings. Certifying distributions ensures consistency across different vendors. The second level is for cross-plane providers and ensures that infrastructure vendors are compliant with the XRM. If you're interested in the conformance program, please reach out today. The conformance program comes at a time when cross-plane is growing faster than we've ever seen. Organizations of all different sizes are adopting it in production. They are augmenting their existing Kubernetes deployments, while some companies are using it as a centerpiece of their cloud-native transformation, moving off of IAC tooling entirely. All this momentum in the community has led us to apply for promoting cross-plane to incubation status at the CNCF. The TOC will vote on this shortly, but we are extremely excited by the progress. Finally, I wanted to throw in a word from UpBound, one of the companies sponsoring this event and the company that started the cross-plane project and donated it to the CNCF. We are on a mission to bring cross-plane to organizations of all sizes and have a number of product offerings around cross-plane that we will be announcing later this month. Please stay tuned. If you want to be part of our mission or want to learn more about UpBound, please visit our website. Thank you and have a wonderful cross-plane community day.


The hippocampus plays an important role in learning and memory consolidation through replay of neuronal sequences. These sequences are constructed from past experiences and can be modified according to current spatial constraints. However, replay does not always reflect previous behaviors or construct new ones. A new stochastic replay mechanism has been proposed which prioritizes experiences based on three factors, experience strength, experience similarity, and inhibition of return. This prioritization results in more efficient replay and improved performance compared to random replay. Additionally, the model is able to reproduce diverse replay statistics due to its stochastic nature and the fact that different experiences result in different weights for each factor. This article was authored by Nicholas Dykeman and Sen Cheng.


I was just gonna, I was just gonna make my own. Thank you. All right, are we ready? No. It is 4.30 p.m. and I'm calling this meeting of the design review board to order. Recording secretary, could you please call roll? Board member Birch is absent. Board member Cook? Here. Board member Liptak? Here. Board member Sharon? Here. Board member Withrich is also absent. Vice chair Weigel? Here. And chair Jones Carter? Here. Item two, approval of minutes. We have item 2.1. May I move to approve the minutes? Thank you. Item, item, okay. Okay, no. We're getting rid of that motion. Minutes are approved as submitted. Item three, public comment. We are now taking public comment on, sorry, non-agenda items. This is a time when any person may address the board on matters not listed on this agenda, but which are within the subject matter jurisdiction of the committee. Recording secretary, can you please instruct the public? If you're attending in person and wish to make a comment, please make your way to the podium. And chair Jones Carter, we don't have any participants, if you assume. Public comment is now closed. Item four, board business, 4.1 statement of purpose. Zoning code chapter 20-52.030F project review. The review authority shall consider the location, design, site plan, configuration, and overall effect of the proposed project upon surrendering, surrounding properties, and the city in general. Review shall be conducted by comparing the proposed project to the general plan, any applicable specific plan, applicable zoning code, standards, and requirements, consistency of the project within the city's design guidelines, architectural criteria for specific areas, and other applicable city requirements. Item 4.2, board member reports. Are there any member reports? We do have one from Vic. Yes, thank you. I attended the Waterways Advisory Committee, my first meeting with them. Last Thursday, May 25th, we saw the review, it's not the review, it was the Canary Project was presented out of courtesy, which we had seen already. That was very good for the committee to see that because it's on Rosen Creek. And we heard from the Heritage Commerce Project, which is industrial on North Point Parkway, which abuts a creek, and I have written Rosen Creek, and I know it's, I don't believe it's Rosen Creek, but in any event. So we met with the owner was there to discuss the project as well as the planner trainee, which was kind of great. So we obviously stated our concerns about Waterways, and I can't wait to go back. Great, thank you. I believe I have to open public comment. If you're attending in person and wish to make a comment on item 4.2, board member reports, please make your way to the podium. And again, Chair Jones Carter, we don't have any participants via Zoom. Okay, public comment is closed. Item 4.3 is none. Item five, department reports, and I believe that is none as well. That's correct. Thank you. Item six, abstention, statements of abstention. Do we have any? I will need to abstain from item 8.1 due to a financial relationship with one of the consultants. Thank you. Well, thank you for coming. Item seven, consent items. There are none. Item eight, scheduled items. This is a concept design review for fire station number five, and Christina A will introduce the item. Thank you, Chair Jones Carter. This is Christina Tumians. I am the senior planner and here to present a concept design review for a fire station number five, located at 1400 Fountain Grove Parkway. The reason this is before you today is code section 20-52.030 subsection two requires that city projects go before the designer view board in order for the designer view board to offer advice to the either view body or agency that's constructing the city project. And we have the plans here. And just to give you a context of where this fire station is located. Oops. So it's at the southeast corner of a stagecoach road and Fountain Grove Parkway. So to the north, to the northeast, you have the Fountain Grove Square Plan Development, which is about 21 residential lots. The project site itself is surrounded by Keysight Technologies, which is a says light industry. And then across the street on Fountain Grove Parkway directly to the east or to the west, you have the Villas Capri Verena Care Center. And then just up the road to the east, you have the Fountain Grove Golf and Athletic Club. And the aerial that you see is where the proposed fire station five will be located and is giving you a context of the surroundings views from the project site. Here's a site plan showing where the building would be placed along with associated parking and landscaping. Here is the proposed landscaping showing streetscape planting and site planting. Here's a floor plan for the fire station showing how the rooms would be laid out and the purposes for each room. And here are the elevations. So the top image is the north elevation. So that would be the main entrance. The image below is east, the east elevation. The top image is the south elevation, so the rear of the building and the bottom image is the west elevation. Here are some site sections showing how the building would fit on the slight slope of the property.  And the applicant team is here, design team is here to present. They have a Vimeo link that they are gonna show. So I will step back and let them introduce the team. There's a little button. Green, good, yeah, thanks. Hi. So everybody can hear. That's great. Supervising engineer for a capital project. So I work for the city of Santa Rosa, Lisa Welsh. And I am the project manager for this project from the city perspective. And then also I'm here with our designer who's gonna be kinda leading you through the layout. I can just ask you to put the mic a little closer to you so we can hear you clearly. Thank you. Yeah, do you want me to repeat that? No, that's okay. Okay. And did you wanna, I can do. You wanna introduce the mic? Yeah, so Steve McCulloch? Steve McCulloch from Wright Contracting. And the Wright Contracting is the design builder for the project. The history of the project is that we actually solicited for design builder a bit ago when we just executed the contract. It's not been very long since March. We have an executed contract. We've been pursuing the design for the past couple of months and we're bringing it to you right at the beginning of this phase of the design build. But it is pretty exciting. It's the first fire station we're doing design build with the city. So yeah, it's fun. But, and then also we have Mark Lagourg. Okay, Mark Lagourg from FIRE. That's also our support in this meeting if you have any questions for FIRE. And I'm Jeff Katz with Core Design Group and the lead architect on the project working with Wright Contracting as our design build partner. So you've seen the plans for the project. We did put together a video walkthrough that I'm gonna start here momentarily to kind of explain the site. This image that you're seeing where the video is starting, the site does have a pretty good slope across the site. So this is the public parking on the upper level here. It is very small site to accommodate all of the FIRE needs on site. So that the parking is here at the southwest corner of the site up at the higher elevation. And we can see where start is. There we go. So this is taking you down Fountain Grove. We have some fencing and screening there to screen the bunk rooms that are facing out towards Fountain Grove on that west face of the building. And so anybody parking at the public parking area would walk down Fountain Grove the way this video is showing now towards the corner. As we're coming down the sidewalk there is a secure patio for FIRE personnel that is off of the kitchen area. And so that's kind of what you see right in front of you right now. And then we're coming down around the corner to the public access to the front door. We also have the signboard that will be visible from both Fountain Grove and Stagecoach. Where the FIRE department will post any public notices about events or FIRE conditions. So as we come around the corner you're seeing the front entrance there on the right hand side of the image and the apparatus bay doors there on the left hand side. The architectural elements for the project we have primarily Stucco as the exterior finish with some fiber cement panels, equitone panels that make up the tower element that you see there with the five on it as well as off on the right hand side that material is used there as well and around the apparatus base. The balance of the building is Stucco. So that gives you a little better view than the 2D elevations that we showed in the previous drawings. So with that, that concludes our presentation. We're happy to answer any questions that you may have. Thank you. Are there any questions from the board? Should we do public comment? Open public comment again. Before we move on to public comment we'll have to, oh nevermind. We had to stop the share on the other laptop but we're okay now. Alrighty, so if you would like to make a public comment and you're attending in person, please make your way to the podium. I don't see anybody making their way to the podium. Chair Jones-Carter, we still don't have any attendees via Zoom so we can move on. Public comment is closed. Are there any questions from the board? We'll start with Vic. So I'm still grappling with the difference between questions and comments. Is this a question time or is it, like is it a question? Okay, I'll ask a question. I'll ask it as a question. I can do that. I am so excited about fires. So that's a comment. I know it's a comment. I am excited about fire station five. But the, and I know the area. I walk in the area a lot and the only people on the sidewalk are people who are walking for exercise. It is the only, so the question is, does it have to have a fence right at the sidewalk? It is forbidding. Even if it could go back, could there be something next to the sidewalk other than that fence right there? It's the only one on, you know, seeable on Fountain Grove and the only other fence is on Stagecoach and it encapsulates this very ugly set of sort of kind of public utility stuff. So I would love to have a little more site area to be able to accommodate that. We can certainly take a look at it. The challenge we have is we do have a tight site. We have egress windows from those bunk rooms. We need to have room for somebody to get out of those bunk rooms. And because of the grade change, because the grade is set down quite a ways at that point, that fence is almost more of a guardrail than security to prevent somebody on the sidewalk from essentially walking or falling onto our site. So we would be inches not feet of being able to accommodate that, but it's certainly something we can take a look at. Thank you. Adam, do you have any questions? I have no questions. Drew? Yeah, I have a couple. So obviously, if anybody lived in Santa Rosa in 2017, they would know that the previous Fire Station Five was a victim of the Tubbs Fire. So I guess the question is why was this site chosen over other potential sites for the new Station Five? Hi. Yeah, I asked Mark down here because he's fire, so he's more of that specific thing. But from the project's perspective, what I do know from our grant funding, this is a mitigation project, so the site is being, it was chosen because it is more desirable in terms of a fire. We aren't rebuilding right where it was. You can clearly see that. So we went through the acquisition of putting it in a new location, and that's due to a defensible space and also where it is located. I think provides that. Response times were about even. It's definitely to add to response times also. When it was put up on the top of the hill, it really pulled Station Five away from where most of the calls are coming from. And in that explanation, you saw there's that, the golf course, the senior living, there's a lot of senior living that's gone on, put in that whole area. All that falls on Station 11 right now, which is on Lewis. And so the call volume for Lewis Road, Station 11, is really high. By moving five, it will aid in that. And then we also have future plans of adding because of our east side of Santa Rosa. We have Station Six that sits out in Rincon Valley all by itself. And so second due to that district is very far and takes a long time. So our future plans are to add a Station 12, which would be our next and move Station Six to in and about the Mountain Hawk Highway 12 area. So close to where it sits now, but then Station 12 would be in the area of Montecito Boulevard and Benisha, kind of by the Oliver's. And that would add a second response up to Fountain Grove much faster than we have right now. So it's really a strategic move to go along with future moves, if that helps. No, it does help. And I, you know, this, I kind of a comment too. I actually, when I've looked at this, I kind of was like, oh, that's actually a really good spot for fire station. Yeah. Just given the amount of development that's happened since the fire and things that are getting put in and around those areas that we've actually reviewed at this board of all that several years. So it was actually really great to kind of see this infrastructure component go in, in that location. So I was just curious that as, you know, the fire department, how you guys were thinking about it and it sounds like you're very much, you very much thought about how this can help the city, which is fantastic. Very much. So just like down the avenue, we have, you know, Station 9 Future Plans and we have an old site that most people know of, Franz Kafka, which really isn't, it just isn't gonna work anymore. So we're looking further down the avenue. The same thing kind of happened with five. They had many years ago planned on putting it at the top and I think they, when given the opportunity, they just built instead of, you know, re-looking at everything and, you know, hoping for future growth or looking at future growth. So I think we're in a better place for everybody, for response times and for the citizens. Yeah, that's great. And then the only other question I had was, if I'm reading this right. So there's, I guess, firefighter parking that's located on the same level as the bay entrance and all that kind of stuff. And then the four spaces, the two ADA and two standard spaces, that's public parking for people coming to visit the station for whatever reason, correct? Am I reading that correctly? That's correct. Fire personnel parking will be in the secure lot down at the elevation of the building. Okay, cool. Yeah, and so then you just have to walk down the, hopefully ADA approved grade down into the door. It will be. Yeah, I figured it will be, but yeah. So it's not, but I understand the constraints, obviously with the width of the bays and everything else. So it's kind of, you're kind of horned in a little bit there. And there's a future, there's also future considerations about putting parking on the street. That's just not part of this initial phase, but there is considerations there if you had preference for that. And then additionally, the parking is quite large for the station behind. So any like known tours that would be happening at the station or any like planned event, the gates down the side could be opened, you know, and allow public to, you know, whether it be a school, a small school bus or something like that, to be able to park on the property, you know, would be available. Those are the only questions that I had. Okay. Okay, I didn't actually have any questions. So sure. I'm gonna ask a follow up question because I was just thinking about where station five is now and what's left of it. And that won't be there. And I very much appreciated the identification of station 11 on Lewis and the way coverage works. I'm thinking ahead because, and here's a street name I had hoped I'd never have to say out loud because I don't know how to pronounce it. Chenate, Chenate, Chenate. Anyways, I live right near it and I always say it three ways. That's gonna have a huge, I mean that is slated for major development and the fire station that was closest to it, obviously was station five. Although station 11 is not far away. So is that the plan? That's the question. Is that the plan that station 11 will cover whatever happens on Chenate, Chenate? Yeah, that's actually a very quick run street as far as we exit the station up Lewis to, I believe it's called Humboldt right there. It's one of Santa Rosa streets. That changes its name four times from Franklin to Humboldt to Brookwood, yes. So, but they can go and that's a very quick, that's what we call a run street which are the streets we like to take in the fire engines to get to places quickly. Also by adding that station down, hopefully station 12 in the future in that area of the Oliver's Center. I mean, I think Chenate and Montecito Avenue even would be well defended and have good response times by all three of those engines, five, 11 and hopefully the future 12. I actually do have another question. Is the fire station obligated to provide art with this building? Okay, I'm gonna say. So the city, we are providing art. So there is an art process. It's just going through a different committee but Art and Public Spaces is going through a process parallel to our design builds and we are gonna be giving them locations. I think actually it was on. The last slide in the package that we submitted identified three or four areas that from our perspective would lend themselves towards public art depending on what that art, what form that art takes and our hope would be to work with whomever is selected by the city to do something that integrates with the design of the building. Great, thank you. Let's see, do we have to open public comments again? No, we're done, thank you. All right, I'm gonna call on board members for comment. If you have any. Vic, would you like to start? Oh, I can start with Adam, how's that? Adam. I heard Vic first, so thank you, Chair. And unfortunately Vic, my comments will probably be quick. Yes, yes, of course, was glad to see this come before us for many reasons, of course, public infrastructure is always a great and important thing to work on. But then of course with the trauma that the area has gone through and that the fire department's gone through, really I'm glad to see that this is moving forward and that we're getting you guys back to capacity. So I'm certain, yeah, I'm certain you're glad to. So I was glad to see this to come forward. So thanks to everyone for all your work. Yeah, as far as the design, I don't have too many comments. I think that there's a very solid design. I think it's going, I think there's, let's see, site-wise. You've taken a kind of a complicated site and have done really great work with it. Quadriga, again, with their candidate-plant list is comprehensive and great. Yeah, I went to a school up in Seattle, and that was in 2010, 2013.  And so it was really amazing to go around the city and see these beautifully designed new public works of infrastructure and also facilities and that's civic pride, civic, it provides multiple wins is what I'm saying, you're providing safety. But this is also a way for the city to really anchor itself in the found grove neighborhood. And I feel that this corner is a great choice. Of course, with this response times, I feel like the building is going to announce itself well up and down the drive or a found grove parkway and stagecoats, people are gonna know where this is. And it's visible, while also the design choices have, they're fitting into the neighborhood context and to the vernacular that's there. So I think it's a sensitively designed building and site and I don't have too many constructed comments. I will look forward to seeing this move forward. Thanks very much. Well, I obviously threw in comments earlier in the question period, but I also, I thank the whole team for the work they've done so far. I really appreciate the expertise that Core brings to the project for the fire station. And I think it's a great site. I was there today because I knew we would be talking about it. And I can, the positioning, the view out and then the ability of the public, whether it's local public or people who are passing through or going to the country club for the first time, it's a significant building. And it comes across that way without, let me make this positive while it fits in with the Fountain Grove and stagecoats, Parker Hill neighborhood. So I'll look forward to walking by it. Thank you. Sure. Yeah. So like Adam, I appreciate the effort that's gone into this and it sounds like since you executed your design bill contract, it's been fast and furious, which is fantastic. So I think that's the great thing about alternative delivery methodologies that we utilize them a lot on school projects and other civic work too. So I guess the only kind of design comments that I have are I'm not like in love with the equitone color. It feels too adjacent to the stucco. I think if there was more materiality difference that might be intriguing. Cause I think, I think what's really nice about this building the way it is, is that the massing is really nice, is like kind of on point, right? I mean, what's exceptionally well done as you turn the corner is you have the layering of massing kind of from the smaller kind of from the kitchen and the entry space. And then you have the number five tower and then you turn the corner and you get to a large bay and you go back down again to the kind of the service spaces. And so I think the massing is really nice. It's just the materiality from that equitone to the stucco, it's just, it's too similar and not dissimilar enough for me. I don't know if the answer is using a different fiber cement manufacturer that's got a color, a different texture. I don't know what equitone is a little pricey as fiber cement goes. There are less expensive options out there that kind of do the same thing. I really like the doors on the front. So like the thinned kind of element on the bay. I would keep that for sure. And then the only other thing that's kind of nagging at me is the little itty bitty bit of the fiber cement panel at the very top. But I'm wondering if that's maybe just a rendering kind of hiccup thing. Because obviously the panels are a certain height, right? They're either eight feet or 10 feet or whatever. And so the tower element just has that like little leftover foot. You know what I'm talking about? Yeah, it's just, it'll drive you bonkers, right? So maybe changing the height of that element just a little bit to get rid of that little sliver at the top.  And you're like, but no, if you'd like just added an inch or two inches, it would fix that. See, I just maybe adjust that a little bit. And then I don't know if this makes sense because maybe it's a little too flashy. But I really like the kind of the CNC routed kind of signage on I guess the fountain grove side and the stage code side. But I kind of like, I kind of, I don't know, like they need to be illuminated from the inside. That'd be really cool. Like so they glow at night. I don't know, maybe that's cheesy. But it makes it really readily identifiable where the fire station, I've seen a lot of really cool and kind of modern fire house design across the country that utilizes light elements or glazing or other things and that kind of monumental entry component that easily and readily identifies the station's location, whether it's kind of a glowing box with a backlit number or the number itself glows. I think that'd be really cool. And then it kind of sets a precedent for how the maybe stations get renovated and everybody knows, hey, like there's the big glowing number five. That's where the fire station is. That's where you go. It becomes an easy place to make a landmark. But you don't have to do that. I just think it'd be interesting and cool. But other than that, I really like it. I think it really fits this area and it's a tight site. All the different site elements are well thought out. I mean, the reforestation area, the drainage swales, the buyer retention, I mean, there's just a lot going on and you guys did a lot with a little. So I really appreciate that. And I think hopefully the fire department is gonna, everybody's gonna wanna work at this firehouse. So, yeah. No, sorry, you have to work at fire station one. Sorry. But I think, yeah, they're gonna wanna work here. This is a great, it's a great building. So, great job. And my final comment is pretty much like truths that I think you have an opportunity to add something to this to make it not blend in so much. I don't know the technical terms, but I'd like to see something that makes the building stand out a little bit more. I don't know if it's the trim color. I don't know what it is, but it does just fade into the background for me. Yeah, I mean, I wouldn't change the stucco, the steel facias. I think those are all just, they're so clean. They're easy to maintain. I wouldn't really change a whole lot of that. I mean, and the metal, the wood colored metal soffit material, the low maintenance, that's great. I mean, and it's all wooey, compliant. I mean, that's what's fantastic about all these materials. But I think just finding a way to make the equitone material do a little something different other than kinda looking concrete might help, I think. Or maybe something to the tower. Okay, thank you very much. I appreciate all the hard work that you put into this presentation and we wish you good luck. And there's no action required on this item. So with that, I'd like to adjourn the meeting of the design review board.