This is a transcript recording about basically the weekly review process, how it works, what each of us does, and the bot that we have to create Right. So you can ask me the question to begin with while I eat a potato. Okay. So we discussed earlier the need to create a a workflow that will avoid us for having to pay the project manager to do this. It seems doable with existing um tools and personnel we just need to applies off how exactly do you envision it working? It's a simple bot that we create. It should be across different platforms so that's just start on Telegram that listens for an audio file that's been posted to it. We could make it more complicated with keywords and stuff like that. It takes the audio file, transcribes it, and then uses an AI prompt to basically pull out of it the information it needs to summarize. For the weekly review, in particular, who the named person was, what the date of the work was, and how many hours under what category. So the audio notes. uh that you post to that channel are basically scrum notes which should have been agreed roughly the the areas that we're working on for the next week in the planning meeting uh which should probably be Sunday but it could be Monday morning right and then planning meeting we can skip it's not essential right um uh and you just post a note saying what I did since yesterday so be something like I spent like um two hours uh discussing with Matt the plan for the week I um uh then wrote that up and I posted it to the Telegram group. I then spend an hour writing about what I'm going to be doing with regard to the Berlin meeting. uh on the identity stuff because I want to post it to Audrey Tang. Um I will link the um URL to that and post it to the wiki And that's all I did today, but what I'm going to do tomorrow is blah blah blah. And these are my blockers. And the bot needs to pull out two hours. um David uh the title of what I did and a link to that particular transcript file right and then at the end of the week you just should should also say a second thing to the bot and just say review uh create review planning document the review planning document then should say david works um um you know Monday, Wednesday, Thursday and Friday, a total of 24 hours, 10 minutes, or you know, it can be just very rough estimate. on the following topics, links to pages or what have you. If this is clear and Matt works um uh six hours and whatchamacallit, right? And whoever else work this. And then we should just sort of uh discuss it. Ideally that would have been sent before the meeting so the person doing the reviewing meeting can just click and sort of look maybe tidy it up a little bit uh um we can obviously then improve the bot and there should then be a sort of decision saying hey how did the week go for everyone um this is uh a summary of what everyone did, what are the lessons learned, what we could do better and what have you. And if that's all agreed, I'm gonna press this button and It can either be a button in the bot or it can be another audio agreement saying, you know, whatever the phrase is, burn to dynamic equity, right? then the dynamic equity adds up the hours to some text file somewhere or some database somewhere which basically then should call the API for um the um uh slicing the pie um thing um uh that exists yeah that exists right um so that but in the end it will be our own platform we do but it's good to just lean on the methods and the the things and the contracts and everything of slicing the pie and then each week we can see that and then that also means we can add someone else this week who just wants to work doing some volunteering for us and get some dynamic equity right if we want to give them dynamic equity and so we can add people or also if you know You said fuck this is too much hard work. I've got to focus on my work, right? I'm gonna take the next uh two months off, right, to focus on my work and we get someone else uh to come in to do the Oasis 5 coveting bit or what have you. We can be dynamic and flexible then. But what we want is the the the admin of that review meeting going together. with that and it should just be one bot and it should basically be as lighter weight as possible admin which is dress-based scrum meetings. So the scrum should be fun to just listen in on a weekly basis. You you know, you just check in, send in your audio note. You're telling other people what you're doing. You also listen to other people The review meeting should be oh there's a nice little summary. Um if you've got any disputes, let's say someone is um uh putting in loads of work but they've only invoiced for four hours because they're totally unconfident. their worth their work was worth it said look you went and what went on a meeting and you had a whole day talking to someone you should be invoicing for that or someone's uh being really inefficient and they've said I've worked 20 hours on this code but it's actually not what we're supposed to be doing or what have you you can say well um I think that's great you've done that 20 hours but we only agreed at the beginning of the uh the week to work on this. So park that if we start to use it and agree on it, but you can only invoice for two hours for that. Those sort of meeting, those sort of grumbles about the efficiency stuff is generally should be the job of the the scrum manager to sort of like or the consensus of the group and we've got to work it out but whatever it is the bot has to have that um simplicity of invoicing and What are the the the security or safety uh features that we should mean uh if you have an if I've sent voice memo that doesn't have the necessary information um should there be some safeguards to to respond and say this was not a complete voice um update? Well the the the scrum manager um would like if the bot doesn't understand or the audio files corrupted it should just say say something error report it should say um I couldn't transcribe this or I transcribe this but there weren't any hours uh registered there and then the scrum manager should just go and have to listen to that or read the transcript or ping that person and say hey you didn't add uh any hours uh you do not want to invoice for that and that's the job of whoever is the uh the the the the agile manager for that week So there should be a responsible person for that and he should have to do as little as possible because the bot should be doing it. Right? Although all the work should be done really in the planning meeting, which should be like, hey, uh next week, what do you think you're going to do? Max. I'm really really busy with work, but yeah, I can be in the meetings and I'm going to be thinking about basically what we could do with the anarchive and swarm um but I'm not gonna be available for more than probably three hours this week, right? And I say, well, I'm gonna be preparing for going to Berlin. I want to write a lot every morning, uh two hours of morning, and in coding I want to get up to speed on Oasis and and but actually work on this bot uh together with all of you to the extent we can so that we can start coding this. And we say, hey, let's not work on the bot this week is good enough as it is, what we really need to work on is the website, right? So can you do that and say, okay, yeah, yeah, I'll focus on the website, this is the thing. What I'll do is the writing and I'll also do the vibe code. and I'll work with Henry on this, this and this. And uh how long do you think it'll take? Well it'll be I'll probably spend 10 hours this week on that right and that should get more and more efficient so that you should have on the planning meeting is right Dave says he's gonna do 10 hours on graphic design on the website he's gonna do uh eight hours on writing he's gonna do this right and now I've got a brief and I would just in my thing I spent two hours on the website. I would put for another four hours on the website. Nothing on the website this week and I'm got in my mind that I agreed that I would do ten hours, right to achieve this result, right? And at the review meeting you said, you said you spent 10 hours, but you spent 16 hours, right? That's more than we hoped, right? Why was that? Right? And like that also is just the basis like of uh negotiation if we're working with a programmer or developer, we basically develop some techniques there and we try and have some processes there and agreements there that we eventually train the bot on as well. Right. So we want this kind of scrum management book and we'll probably find that there are some other people and projects working on the same thing or a commercial company that's done it well and then we've got to decide whether we want that as part of our product or or we want to uh just pay for someone else's. But um that's the s the service of it. What we want to do is make sure that we have the hitchhika branding for the dynamic equity the reporting this very minimal sort of so that you're not a full software developer. You just learn this way of sending in an audio note and now you can work as a team. And then you can take it to more complicated things, adopt this proper scrum application that someone's created, or decide that you want to do some other thing, you know, and there should be s several almost product you could pay for or adopt or service, you could hire in a proper sc agile scrum manager to do it for you based on um dynamic equity or time bank credit credits or uh pay them in cash, right? And people should there should be a uh a a library of sort of services for that kind of work, right? But we specialize in this early age, early stage, dynamic equity, thing that is good enough for us not to argue about things where things are clear and we do these understandings and we try and do but just best practice on that and when it gets more serious we go to using Jira, GitHub, whatever it is, Monday. com if we want, or we just improve the customize the the functionality but what we're trying to do is vibe code the future so what we want to do be able to do is be able to fork that particular project and say right what we now want to do is assess the quality by doing review of GitHub commits. Can we link the GitHub API to this? And can we use the issue tracker on GitHub for the this and this and we got um a more elaborate sort of project management thing that we decide we want to do and then we say oh that's really cool now we offer it to the community and they can fork that into if they want to use that and they might pay us for that uh code right you know i in some way or other but So but the basic thing we want to do is that you've got any specific questions on what we need to do or how it works or what you might see as being a a problem between me, you, and Mitch doing that. Um uh in I I wanna know uh how how how far along Mitch is with his uh telegram bot when we use any of what he's done already he's got some i assume we will yeah yeah um and whether or not we want the bot to actually speak to you um and and whether we use exclusively one group so we've got that mice group but do we we well as soon as we got real groups so I want to do it with David Ellams. Okay yeah. just imagine just me me and him for now. Yeah. Um I want to do it with um um I I want to integrate it. Like you say, we can build upon that. So I want to integrate into the podcast. So ideally the daily check-ins get kind of mixed with some sort of uh interesting AI background and then the weekly reviews become an actual meeting which we've recorded and we're talking about it, the graphics come up, the AI's speaking or singing or doing what it's doing. doing right um and um there's a guest um uh person come in uh and we record it and that's kind of whatever you call it it's the kind of build-in open um uh process that uh uh was a a bit of a a fad four or five years ago, but it's a standard kind of thing in a open source world where you just sort of basically every week you're telling everyone what you're doing, but it's just your review meeting, let's say. that you're doing that you're brought and you can make it public completely or you can make it discoverable, not promoted and public, or you can make it pro invitation only for hitchhikers or members. or whatever it is, right? Um or just only of available to the people working your current project guide and vision fish and what have you. But definitely the link into the podcast and the audio will be important. Yeah. And also each one of these things Well I imagine it working with the proof of understanding and Mitch's stuff is that every meeting is input to the uh the proof of understandings, right? Particularly like in the meeting where I don't know Mitch says I'm gonna do this, this and this. And if I'm the project manager and I say, well, I got you what you said, Mitch, is you're going to do this, this, and this. Is that what you said? And he said yes. That's a proof of understanding between us, right? And also in the review meeting, if we've done that, that's a kind of proof that this the understanding was delivered. that's greater trust all the time. So here's trust graph staff should come out of that. Also in the meetings they should be as quickly and short as possible. and any problems should be followed up as one-on-ones afterwards. So if you're in the meeting you see that Mitch is doing that and you didn't quite get it, you say, I don't quite get what you're saying, but I believe you. I'll check in with you later. And later you have a one-on-one call with Mitch and you get a proof of understanding for that, right? And it's that kind of thing. And then you can make some graphs and visualizations saying Oh, Max is really knowledgeable about all that stuff, but this weird stuff over there that David's doing. There's not very much understanding about that. That's fine. But now we're having a meeting with this person. You should probably we should probably focus on that. area where we're not kind of aligned. Do you know what I mean? Yeah. And um the all that kind of graphing and project management together with the you know the the onboarding types that you talked about before. It's like oh you're an action orientated type A D E F G all of those sort of things also feed into that but starting simply we just want to get the dynamic equity timing and the bot that will process those audios and then we can start innovating with different prompts and different visualizations and different other things. When we upload the file the audio file. Yeah. Do we w we want to be storing it somewhere too? Um well at the moment the way that I would do it, um, but we c we can figure it out out is there's um um local file There's a particular um so to save costs on AI processing and tokens, it seems a waste of time to pay a service to transcribe it because it's actually quite expensive. Yeah, but that's using tokens. Um Yeah. You're paying silly man money for no good reason there, right? Well You should have a local transcribing whisper model right um and then it's free yeah right so i i I've got uh it's really easy to do I've got whisper as well Right. Yeah. So uh if cursor is issuing it locally on the commands, right, then that's fine, right? But what you don't want is to be using some cursor service or some uh cord service that's doing that scale it becomes unwieldy? Um I'd soon well because you know it's just It's lots of um I mean obviously you're paying a hundred pounds but we don't two hundred but we don't all want to be paying two hundred. Yeah. And we want to use that two hundred for really important stuff rather other than stuff we can do for free with five minutes work. So locally hosted with uh it's not it's it's locally hosted yeah yeah um um But not necessarily locally hosted. We can also host the code on our server. So at the moment we've got a server, let's say it's the Vercel server, right? We just add the Whisper command line tool to that and a little Python script that we can run on it, right? And put a little API on that, right? And or we make so wait, but what where's Whisper? Where what who is uh did is Whisper an A an an AI itself. No, it was just a command line tool. But where does it C plus plus library? Okay. So in which case I mean that's how incurrently works for me on cursor. So a lot because I thought Whisper might be a ChatGPT function. Well it is as well. Okay. It's an open AI library that they open source. They use it internally. So when ChatGP wants to transcribe it, it uses Whisper, right? But then you pay for it. It eats up whatever your your thing is, because it costs them processing time and they've got millions of people doing it, right? And usually it comes within if you do a small uh your normal token allowance, right? But it's just one of the things that because we should be doing local stuff as much as possible, makes total sense to do because it runs perfectly locally. Now I don't know how your cursor stuff works because you're not paying a lot of attention to the detail of it. it as long as it works you you're happy with it if you know what I mean if the API calls is just using the AI to figure out what the command line at all and then it's issuing a shell command to or a bash command to something that is a cursor library running locally, then great. You shouldn't be, it'll just be using a tiny number of tokens. And You know, you shouldn't even d need to do that really, but it's not a big deal, right? But basically what we want is to be writing code that if it runs locally, we can also put it up on our server so that it's globally available as well to everybody. everyone. Yeah. Right. And we've just got a local mirror. So we've got a choice of running it in the home lab setup setup or just saying ru run it globally. And and it's just a bit more accessible because if we're running it locally it's only available via some weird messaging thing or via the tail network but that's all the networking stuff right And what about the storage of the actual voice memos themselves? Do we want to uh keep them somewhere? Well, like I said, at the moment, the easy thing to do, like what we can do with this and what I've been doing at the moment is I create a weekly page for each thing that's worth documenting And I put a little audio play in there so you can play the full audio. I put a link to the transcript and then I put a link to the AI summary And the audio file is just in a named folder, named the same as the wiki wiki uh uh page, so it's unique, right Right? And they're all sitting there like that. So it's a flat file system, which could be on Vercel or it could be on the existing stuff we've got. The important thing is we want the and the idea would be to look at Oasis so that we can do the replication thing. Right. So that um I can say Oas uh like Oasis put it on my uh local uh file system, right? Or I can say no Oasis put that uh in the Vercel Postgres database or MongoDB database or what have you or I can say Vercel put it s uh on pignata or what have you, right? Yeah. But um it's like um we should have the choice to be able to move it with the same api that we program against. Yeah that's that's how that's how it works Okay, uh no more questions.