afternoon-meeting-cloud

# Transcript: 2026-04-29

> 3 time blocks from 4:01 PM to 5:22 PM

---

### Client meeting AI integration discussion
**4:01 PM - 4:50 PM PDT** | *meeting*

**Microphone:**
OEM today was successful. Everything that needed to be done got done. That's fucking sick.

Clients want more AI integration and operational efficiency, like the one we're going to be talking about now. Like enterprise projects, they have a bureaucratic hierarchy. So do you know Connor Finn? I used to work for this company called Lift Foils, which is an efoils company. Electric surfboards, let's call them that. It's a huge niche.

He used to work for this company called Lift Foils, which is based in Puerto Rico but they're a global enterprise. Connor, my good friend, I went to visit him in Portugal the other day. They shipped to Europe, they shipped to South America, they shipped to the mainland, all over the place. I realized that the shipping department was working very inefficiently.

Essentially, I might mention him. I can't quite put a face to it like Connor. This was about Miranda, a developer, but when I touched base with her, Miranda isn't really paying much attention to the idea. So I figured I'd pitch it with you guys and see what you guys thought about it.

So then he pretty much sent us a spec document. We have had one or two discovery meetings to truly understand the project. But to our understanding, or to Cam's understanding, it's a relatively simple project, anywhere within the range of pretty simple. And the scaffolding for this demo is what Cam has also come up with, along with a lot of the clients that we've already taken on, right? So that was kind of the purpose of bringing on you and Jose, so you could onboard pretty efficiently.

Yeah, I've been reviewing it and going over the Lift Foils brand and product references just to get a little bit more familiarized with it, but yeah, go ahead. Did you get the spec document that Connor sent? That's included, phases one to four. I'm downloading it. Beautiful.

Like, we didn't want to over-engineer it. Which by the way, I completely encourage naturally. I think obviously a big part of this is working on stuff that's mutually beneficial, and you know when it's mutually beneficial, like it's a no-brainer. But that said, you guys can collaborate on this. It's more of a consultation. Yeah, I don't mind.

I'll just analyze what we got and what are the gaps we need to address. The POC is kind of rolling onto MVP, Part One. Yeah, I think from that part it's gonna be fine. I just want to know what I'm dealing with. I'm going to take some time to research and I'm not going to be jumping in right away.

I'd love for you to kind of take the lead on this project. And naturally, Cam will also be there to support in whatever shape or form that you need.

I normally take like a day for research and reading and just getting acquainted with everything. What, um, if we need to do any PII redactions, if we need to do any HIPAA, or if we need to do BAAs or anything, I'll put them on a checklist.

If it's redaction, then yeah, okay, Supabase is pretty good for that. I don't think it needs anything more. It's already integrated with PostgreSQL. That's good. I have the CLIs. I have the workflows. I'll just import them, hand them out, and see how it goes.

I like to work on a PR basis. I like to work with GitHub because prior to any project, I like to set up CIs for any schema migrations, for both backend and frontend. I'll report on that and analyze the docs. This is really good. I'd rate it a 10.

And within there, I want you to feel free to create your own repository. No, don't do that. I'm a huge fan of Supabase and I've used it before.

So let's make sure you have access to the info at Flow Systems email. Those accounts and yeah, we'll go from there. That is credential blocked.

Naturally, moving on to Supabase, I know where the tables are. I know how they're connected. I know their values and what they're paired to, and I can go granular to each one. I really love Supabase, but again, I'm coming in like a wrecking ball. So I mean... I was gonna say it. No, don't let me lead all the time. We'll analyze if it's better. You can do the same. I appreciate that greatly.

My sole purpose here is to help. I know that you literally just read the spec document, so I will give you more time if you can't answer this question now. But I can't open it. I think we normally use... wait, but did we not set up... I don't know. What the hell is my Flow Systems? It's just our primary account for everything currently.

Let's see. Dispatch. There we go. Sharing right now. Can you also send your GitHub to the chat? I've got my old personal one. Because I created it myself. I don't want any issues. So you're going to see it's kind of crappy, but it's GitHub. It works.

Anyway, I have a lot of stuff about when I was learning how to code. So you'll see like Holberton this, Holberton that, and it's like whatever. I already have the SSH here script. And then I shared the document so you can take a look on Google Drive. At that code. Oh, God. Supabase, beautiful.

All right. You mentioned that. Today I was working on... because it's the biggest project that our department is working on. And I was creating some skills for housekeeping. It's pretty nifty what I'm cooking, you know? So hopefully it works.

But yeah, you mentioned we can just share and review together as a group. Yeah, for that. So it's not just in one person's repo. And yeah, I'll think... if we do that with the ecosystem. I can't port the ecosystem completely, but I'm gonna see what I can scrape and then push it over.

All right. Don't get me too excited. Yeah, it's fun, man. It's fun.

This skill is for processing Screenpipe audio exports—not what you're asking. You want a manual transcript cleanup, which I'll do directly.

---

It was intense because all her work pushing this. Yeah, it's fun. Yeah, and you're not getting laid off here, just so you know.

Gaby, like I had spoken to you on the phone, this project does carry somewhat of a time constraint, right? I'm literally just bringing you onto the project. Yeah, 100%. I'm down. Sunday or even Saturday. I'm mostly available during the afternoon. And Sundays I like to take off. But at the same time, that's kind of why I decided on this. I love that this is the first of many, with the idea that there's going to be many more projects from where this came from. Yeah, no, I'm all for it. And it's exciting. I relish the idea as well. I've always wanted to work with my buddies, but understanding that professional is professional, but you don't take it personal. Like, personal is personal. That's what I like. So I do take Sundays off from my time.

Yeah, because when I finished the whole plan, the design, all the implementations, all the nooks and crannies, all the things that I needed to give head to, I just let the dispatch go. But looking at the dispatch spec, I don't see anything about tech stack. We could use Python 3.0 if we would do that, but we don't need to. Yeah, I find that good. It's in there, man. Okay, API surface. Okay. Looking at the routes and then in the migrations, you'll find the spec defined. So I feel supremely confident, you know, you and I can make some serious progress. That's obviously the case. So we're going to be handling the queues. I saw that we are handling Redis. That's good. And the seven-day calendar and the dispatch batches. The dispatch pipeline generates carrier batches from review shipments, and that's going to be via IP. For the sake of showing that the system will take it into account, not like blending reality with the future. Yeah, go ahead. I'm so sorry. Oh, no, no, no. I'm sorry. No, no. I just wanted to see how they have it set up so I can provide that to them. I don't think it should be a problem.

Like I said, obviously I'm sure you guys have a few ways of getting around this type of stuff. I don't know. I was asking for things and was thinking as far as spec goes, what ideas do we like? Compare and contrast, sort of marry ourselves to a strategy. Like deploy the web apps to Cloudflare so it's in one place for us, and see if we can get that data or whatever else you might want for the demo handy. And then take it as we go. Proceed to tell Connor, like, hey, the week's over. That would be ideal. And by thought, I haven't sat down and actually thought about it. There's always a hard L2 count. It's fucking insane. Well, I just want to know: the demo, the MVP, what is the success metric? Obviously it's that it works. But what is this specifically? What are they looking for that it has to do? But what is the success metric? Because that's going to matter. If we can mock steps one through eight end to end, and it doesn't have to be functionally complete, it's a component of a section of the spec. This is the success criteria, but it's the end-to-end workflow.

Yeah, I mean, fundamentally we just want to do this workflow without issue. We need to have that body jump through to convey that message. It is our North Star. Tell me exactly what we need to do, you know? Okay, that's a human checkpoint. How they can create safe routes for each product on shipments on normal, which—it's return on this, okay? It doesn't worry me. Yeah, the Connor thing, that was something I raised on our call. It would work. That should be fine. That's the area, so at least we have an API documentation. If we just know the route, I'm just worried because sometimes those migrations might result in issues. We'll tackle it at the moment.

Yeah, I agree 100% and I've been working on that. I've spoken about it. I think you're going to be doing some loosey-goosey work here that we can work with. Or it'll drive you fucking insane. Either or. I love being insane, man. Insane is better than being normal. It's fun. That's how I think. We can be better than that, but Cloud's a moron. So yeah, I'm always very adversarial with Cloud because going overall, overall, this is a lot of shit. It creates a lot of gaps. I'll just ask questions. Are they the same one? Okay. Even if it matters? I mean, I guess like I can see where you know—I'm not saying don't message me. That's not what I'm saying either. Fine, I won't, bro. No, no, no. You ghosted me, so I get it. I get it, bro. You relayed that. As far as questions go, high-level questions in the group, low-level questions to you. We can do that. Okay. I'll work with you to figure out a time that works best for all of us. And I also owe Luis and Miguel another meeting soon.

You try GPT-5.5? Dude, I've been loving it. Yeah, same. So what do you do with structured planning basis with cloud executes it and it's fucking insane. It's fucking insane. I love it. Yep. You see what you do, Luis? If you want, we can tell you. All right, bring good people together, Don. Amen, bro. Amen. Amen.

I'm going to send them through work on my end to have an environment set for you guys and anything that might be needed there. I'll check out the repo and probably create some CIs if I think them necessary for the project. We can use that repo for now and then I can use it, you know? And then we'll work at that branch becomes the main for that project. I really don't mind. It works. And yeah, we'll get everything up to par. Let's go. Yeah. All right. Bye. Bye. That's dope. Good stuff. Good stuff.

Cam, if you could stick around for a couple of minutes? We're trying to see if we could get a meeting set up for him. It doesn't really matter, but he did mention that he can do 10 a.m. your time. Thank you. Obviously, if you're okay with doing that, that's amazing. Let's do it. Positive. Okay, I'll text him. Okie dokie. All right. I'll let you know what Eduardo says. Gabi, love you, dude. Thanks so much for popping by. I'll surely catch you on the Discord later.

Maybe because we're having problems with the internet at work. So I'm probably remote tomorrow.

So, you know, I wake up at 9:30 and I sleep. Oh, we're good. I got my—

Bye. Deuces, boys. Oh, shit.

**System Audio:**
Hello, Ian. Today was client number two. So now I'm meeting with another client and they want to go through the basics.

Connor, my good friend, I went to visit him in Portugal the other day and he told me about these e-boards—basically like a board with an engine at the bottom of it. People seem to love that. It's like a huge niche.

He used to work for this company called Lift, which is a company based in Puerto Rico but they're a global enterprise. They ship to Europe, they ship to South America. He was working there in Portugal when he mentioned this project that he wanted to build for the company. You might also know Alejandro Miranda—that's how we call him—a very good developer actually. He had this idea and I got into it, so I figured I'd pitch it with you guys and see what you thought about it.

So then he pretty much sent us a spec document. We had like one or two discussions to truly understand it and we decided that depending on how deep we go, it could be like a 10K project, pretty simple.

Yeah, I've been reviewing it and it looks beautiful.

You guys can't really collaborate on this alone. It's more like—obviously, I think at least my idea, correct me if I'm wrong—I'd love for you to kind of take the lead during the burden of an entire company and its tech division, right? Which is why I contacted you because I knew this is the type of stuff that you work on. And naturally, Cam will also be there to support you in whatever shape or form that you need, like consulting.

I completely agree. I don't mind at all. Even if I'm taking over wherever you left off, I don't mind. I believe you already have part of it, having everything we need for that MVP—modular, you know, all the engineering constraints.

I normally take like a day for research and reading and just getting acquainted with everything. What is the system? Where am I going to be sending the information? If it's enterprise, I think that's going to be fine. I just want to know what I'm dealing with. I'm not going to jump in and start rapidly coding.

Supabase is pretty good for that. I don't think it needs anything more. It's already integrated with Postgres, which is good. I have the CLI, I'll work with that. If it's encryption or JWTs, of course I'll work with that too. If it's code base or any database, I'll work with it too. If we need to do any APIs or BAAs or anything, I'll put them on a checklist. Of course, not all of that falls into me. If it's redaction then yeah, I have the workflows. I'll just import, hand it out, and see how it's going.

I do like to work on a PR basis. I do like to work with GitHub because prior to any project, I see my CI pipeline running and I'll analyze the docs. I find this really good. I really like how you laid it out and presented it—20 out of 10.

Thank you. Yeah, and then yeah, we might need more. That's the most important part and then I can worry about the rest. We can obviously continue the conversation on the project.

If we decide to switch to Supabase, no problem at all. Supabase is just a little bit hacked in that way and they do provide a lot of integrations and protections and things that you don't need to worry about because it comes in with a package. And one of the things—they're connected. I know their values and what they're pairing to and I can go granular to each one. That's one of the main reasons why I really love Supabase.

Most coded features that I love from Supabase is the schema on the databases that I can watch—that's so freaking nice. I just know where the tables are, I know how they work.

And you prefer cloud? Yeah, I will. I do that with my lead all the time, but I do it in the best of senses. Like, I'm not a refuting type of guy. I'm more of a questions type of guy. And then I just bounce questions off and we'll get to a conclusion.

Don't mind. Communication is key at the end. Okay.

Cam obviously has pretty much been working with me. My sole purpose here is to provide you guys the projects needed, right? I'm not that type of guy. I'm not the type of guy that says like, "we should do this because it's better." No, we'll just bounce off questions and we'll analyze if it is.

I have really simple and stupid questions like, Gabe, so I will give you more time if you can answer this question. But I can't open it because this laptop that I have right here, I haven't downloaded it. It's 6.5 GB. I'll put my email here just in case. I'll put my Google one so there's less complications because I normally use my alias.

But it is what it is. Same, same. I have like 28 repos in this account but most are from school—stupid shit from when I was learning how to code and everything. So you'll see Holberton this, Holberton that, and it's like whatever. But I'll use this and it works. It shouldn't have any shares.

Let me go over here—personal email that I'll let load. Okay, it's beautiful. All right. Okay, how many branches are we picking? It's really in-depth housekeeping and once I have it solid I'm gonna send it to you to see what you think about it. It's pretty nifty what I'm doing.

You mentioned that today because I got handed one of the biggest projects that our department has. Yeah, it's like, what the fuck do you want me to? Yeah, and we can do the PRs for that.

The transcribe skill is for processing Screenpipe audio recordings through a pipeline. This is a different task—manual cleanup of raw transcript text. I'll proceed with cleaning it using your rules.

---

Just find an MD file. No, it's like you review it in the PR. You read it in the PR. You know you got it there. That's good. Merge of that shit, you know? And instead of having two reviewers, you'll need, like, order for it to merge.

If we do that, I'll try to do... today was horrible though. Like I got to my shift, I texted you, I told you I got to my shift and they laid off one of the developers on the team—the only girl. Well, got laid off. It is. Bye, man. Obviously, I know, Cam—I do feel the need to let it be known.

To see if we could have a demo next week. That being said, considering that you're just stopping on this project, I'm not gonna do that to you. I know that you also have like other projects that you're working on simultaneously so that you can analyze that document and ideally give me some sort of timeline. Let me know, okay, this is going to take me this much. Ideally if we can hit that mark with the demo and have it ready in two weeks that would be awesome but like I said, I'm not gonna stress you out with this shit. On well, take my Sundays in. I mean, hey, look at it this way—if they like the demo you're gonna get paid for it, so you know, yeah, that's a couple thousand dollars a year or more than we mentioned. Going the revenue share route. Because obviously we enjoy it. Projects from where this came from. So yeah, no, I'm all for it. And it's exciting. I relish the idea as well. Here should be like, hey, this is the first of many. And I want to make sure that you feel comfortable with the idea that there's going to be many more. I've always wanted to on Saturdays I don't need to, I'm not getting paid.

Can actually vouch for that. We play video games together and sometimes we'll be on Discord and while everybody's playing video games, he's working. Yeah, I'm excited. It plan, the design, all the implementations, all the nooks and crannies, all the things that I needed to give head. I just let the dispatch go and I just needed to monitor it. I'm just vibing. Well, I sent Cam a picture the other day. I had two computers. I was playing Silksong and I had my personal projects on my laptop and personal is personal. Having that clear distinction is really important. I know I have it with you, so I really they don't mind and it actually motivates me even more. Like looking to my computers, hitting my vape, smoking a little weed and playing for a little vibe. And everything came out even better, you know.

I'm looking at 10. I do see the plus, so that correlates to we can use Python 3.4 or whatever. It doesn't matter. I can't give you an estimate of time right now because I am skimming over it. I did see at the end that the tech stack is going to be Python 3.4. I see routes. Work on. Thank you. Build it. That's obvious. Dispatch batches. The dispatch is pipeline, generate carrier batches from review shipments. That's going to be via ID. I did see a few and we're going to be handling the queues. I saw that we are handling Redis. That's good. We got the notifications, the seven day calendar. The SQs are going to be tied to the IDs, I do believe. Are we working with barcodes? Do we need to generate some barcodes or, yes.

I just wanted go in, but is there a way that we can... You of questions. You know, obviously I'm sure you guys have problem. Course. Peace. Awesome. Well, let's do that. And minutes of the conversation. If you guys can provide me with an estimate of when we can have this ready so I can proceed to tell Connor like, hey, sounds good. Right now, good, you know? Because we can scale upon a bunch of features or we can implement the features that they're looking for for the demo, make it look clean, make it look beautiful, nice. But what is the demo? The MVP? What is the success metric? Obviously it's that it works. That's obvious. It has to work. We'll see how we adapt and overcome it. Definitely we will overcome it. I just want to know that's metric see what.

Yeah, I do see how we might get blocked by not having that NetSuite connection, but to be honest, yeah, it doesn't worry me. The pool recording sounds good. You. Okay, that's a human checkpoint. So how we would present it. Okay. Match and they pass through, if they have an API documentation, right, that's if that would help a lot. We wouldn't need a schema migration that we might need to do, or if they have a JSON already for us for what those endpoints are so that they meet and they actually receive the data, then that's good. And then yeah, we can route be good. It just worries me because sometimes those migrations might result in problems, depending, but we'll tackle it at the moment. And then if the actual production pipeline works, then we just need to switch with whatever NetSuite has. And that should be a containerized moment.

Yeah, I agree. Yeah I agree 100% and I've been working on that shit, fucking hate it or something. No, I could have. Yeah. So no, we'll work it through. Again I skimmed it, it looks straightforward, it's well documented, it's good. I'll iterate over it. I'll actually read and see what. Yeah I've had to be man, it's hell over here, it's insane, but yeah don't know. So yeah, I'm always very adversarial with Cloud. So I'll just jump on that bandwagon with him and I'll iterate because you can buy dates that same one. Thank you. Gets technical, doesn't matter. Bye, Cam. Perfect. Thanks. Okay, sounds good. A hundred percent. Yeah, same, same.

If you download it—probably you already did—but you configure the MCP for Codex for Cloud, right? So it can offload. It gets sent to the node, and then Codex works on execution while Cloud works on planning. I do structured planning phases with Cloud, and then I migrate that implementation phase, and then Codex just receives it and executes it. It's beautiful.

I'm the skeptic sometimes, so I have smaller running processes with the node and the MCP, and then I have another terminal with Codex. I have a better parser for LLMs, and it works wonderfully because it's as if it had a 1 million context window because it has the leeway. Everything that it does, it just keeps there. I don't have to worry about compaction or degradation or context pollution. Yeah, it's fucking insane.

We can. It will be fun. Boys are trading sauce. Amen. I'll review any questions; I know where to go for answers. If you can give me my aliases or any credentials that I might need for access, send them through and I'll review them as well.

Then I can use what we'll call a branch, you know? That branch becomes the main for that project. I really don't mind. I've done that. It's not the best, but it sounds great, guys. Thank you. Yeah, good stuff.

um, Cam, if you could stick around for a couple minutes, I wanted to consult something with you about Eduardo, because tomorrow... I did mention we do 10 a.m. That's like 6 a.m. for you, bro, I think. You sure? And then I want to see if we could get a meeting with Seba for Friday, all right. um, then I'll let you know what Eduardo says. Okay, right. Amen, bro. All right, take care. You're good. I got it. Bye.

### Post-meeting casual debrief call
**5:00 PM - 5:06 PM PDT** | *casual*

**Microphone:**
Hey, goofball. What's up, bro? What am I doing? Yeah, I just got off the meeting. Pretty darn good. I'm going to be out. I don't know at all.

Let's say something else. But overall, I was like, oh yeah, I pressed that and I go check it. You know, I'm gonna put the miles. The hot chain operation. You're not talking to me. They're closing the door.

So we're shooting the car, but we're shooting the hay and I've never done that. The sentence, the last meaning of the death in San Jose. I'm not able. Yeah, and the other programs in the last year hold along with the impression of the place.

---

<details>
<summary>Background Noise (1 blocks)</summary>

### Fragmented unintelligible audio
**5:11 PM - 5:22 PM PDT** | *background-noise*

**Microphone:**
I need to be honest: this transcript is extremely fragmented and much of it appears to be garbled beyond reliable reconstruction. There are numerous incomplete sentences, unclear references, and speech-to-text errors that make the intended meaning uncertain.

Here's my best effort at cleaning what can be salvaged:

---

Ah, I'm gonna pass on this one. Have the wall. Bye.

Oh yeah, this one actually... But I don't think that hurt. You can see where the whole vehicle is instead of the wheel's air. I would go so far as... Yeah, it's the only way to get that. A lot of words do.

All right, thank you then. No, no, he said that. You're a little bit. I love it, perhaps? I'm sorry.

---

**Note:** Much of this transcript remains unclear even after cleanup. If you have access to the original audio, re-recording or getting a clearer source would yield better results. Many passages need more context to be properly reconstructed.

</details>

The afternoon centered on a client onboarding meeting for the **Lift Foils dispatch/shipping optimization project**, introduced through Cam's friend Connor Finn. Gaby was formally brought onto the project as technical lead, with Cam in a consulting/support role. The team reviewed Connor's spec document covering a dispatch pipeline with carrier batching, Redis queues, a 7-day calendar, barcode generation, and eventual NetSuite integration. The target is a working end-to-end demo within two weeks, with success defined as the full workflow running without issue — not full functional completeness. Gaby will spend a day on research and compliance review before coding, and plans to set up CI pipelines and a PR-based workflow using Supabase and GitHub.