 I think most people are pretty good idea what we're doing so kind of screws through this and just focus on one or two things. Our mission statement to bring open interoperable conversation layers over all knowledge, which means open source, clients server interoperable system based on standards conversations for humans or machines in layers coming from different community groups or even different services and over all knowledge. So any format, any document, any media type browsers, devices, etc. Based on a standard web annotation standard from the chip last year. So, you know, kind of conceptually, this is what it looks like. And these are the basic product themes that we have so one is around format coverage text images video. Another focus is on comprehensive browser support, both through the client itself as well as plugins. The ability to be embedded so plugins for OJS and WordPress and even things like Google Drive and so forth. So a lot of focus on frictionless authentication supporting different models. I'll talk about federated architecture and then communities really is about the idea that there's lots of different potential use cases of annotation happen in different layers for yourself for for a group of people that you invite for a broader community. Coming right now we're shipping didn't change that sentence. LMS plugins and LTI support for Canvas Moodle Blackboard and other systems. Education is a big use for us. A lot of effort this fall on scaling. We're starting to see higher volumes. So we need to be able to support that, both for system that we run as well as infrastructure that other people might run on different group models. And we support closed groups, but we're about to flip on open and read only groups for broader deployment. We have kind of going and limited deployments now, and then special kind of group modes like having a group that requires an orchid in order to be able to participate in notifications. So being able to be notified of an annotation that somebody annotates some page you said I want to listen to any for any annotations on that page being able to listen to two annotations from a group to be able to subscribe to annotations from an user, all those different kind of social modes. Other kind of key features like much more comprehensive export capabilities and things like that. And then the last thing is the multi service client, which I'll talk a little bit here. So these different annotation layers should be able to become to be able to exist in that you can have different layers, but they should also be able to come from completely different services run by different organizations so kind of conceptually in our little group pull down at the top it might look like this like elive is running their own service hypothesis is running a service and a pharma company is running a service behind their own service hypothesis is running for their own purpose in annotating documents, everybody should be who's operating in very different modes within the community for different purposes commercial not commercial should be able to use the same infrastructure to do the things that they need to do that supporting that kind of ubiquitous model that implement that's fundamentally based on the standards. And what we would love is your ideas about how to use this kind of capability to serve these kind of layers so one thing we'd love to walk away with today is is ideas we talked to Ivan at retraction watch for instance about having a retraction layer that's universally lots of annotations happening use is increasing and then thanks to a lot of you who've been partners with us and bring that forward.