May 13, 2026

# Transcript: 2026-05-13

> 1 time blocks from 4:35 PM to 5:50 PM

---

### Informal conversation with expletives
**4:35 PM - 5:50 PM PDT** | *casual*

**Microphone:**
I'm gonna see if it's fucking me. You never know. Bro, I think it's me. Holy shit. Whoops. Damn, let me see if this worked. Wait, uh... Check, check. One, two, check, check, check. It's me. Oh no. God damn, I'm so sorry man. I'm like, well, it's your problem. That's so good, dude. I was like, oh man, it's so strange though; my Google Chrome is picking up the audio. So yeah, no, no, at least we figured it out. Where the fuck did I put that shit? I'm getting in XY. I do like your shirt. Oh, thanks man. I am definitely fucking allergic to drugs. Give me a fucking vape pen, dude. Yeah, for real.

All right, so I just wanted to crunch out—we're gonna be meeting with Connor on Friday, right? Sounds like it's gonna be during the night, okay, but that's good. And I assume that in a worst-case scenario, let's say that you hadn't had a chance to like try doing the daemon stuff with the cloud or tunnels, but yeah, if we want to walk through that really quick just to make sure that it works on your end and that you've got like a LAN backend working for you. Yeah, I put... and then just copy this. So I'm going to save this and then I'll point it to this session. 

It was just the deliverables that I had at the moment: the reviews that I was doing on what we had and what was missing. These were particular things that I found, like, at least all headers in the tables need to be toggled for filter view, so you hit one of the headers and it auto-filters to that or like ascend or descend. Totally. It needs a dashboard. And I was wondering what KPIs we could represent for LiftFoil. The Q is good, but in terms of analytical, what they want to see—I don't know which KPIs they are looking into. I would need to read the handoff; I think they are there. I'm thinking that we can probably just throw up whatever, and then we can talk through that with Connor. Beautiful. Beautiful. 

And then the ops agent pane needs to have an adjustable side if the... and you can see the orders being scanned. Instead of seeing like 0 to 37, I might check on that again just to make sure it's not a bug, but you see "one of 37," like "5 of 37" or "10 of 37" being scanned. It just gives like trustability. I find this really good. Held, autoclear. Weird. I love the pagination here. Seven day clicking on these—I was going to work on it. I know we talked about it, but clicking on them so we have a detailed view here. We have a lot of space that we can work with the barrier badges and they opened well. 

And then compliance: so we do have a few things like talk to OFAC and the AEAs and everything. I wanted to revamp this. When you go to Compliances, you see each and every one and how they are being completed. Then I see the connectors. This is the NetSuite TalkRest, and these are the external systems that are going to be wired to LiftFoil's dispatch. So we have the Cloudflare, Anthropic Claude—because that's going to be the agents—we have the recent transaction email, the ShipEngine, the EC port rate, and the NetSuite, which is the API that they have. Obviously, it would be good that these were in like toggles so if I click on them, I can have them or they paginate to somewhere else. 

What else? Sources? I think this Open Design—Open Design is a reverse-engineered open source of Anthropic's Claude design. So it's open source, completely open source. I was going over here what I wanted, so I stopped because I said, let me do it with Cam. So I was like, what's the primary use of the dashboard? It's going to be dispatch operators, compliance officers, operations, and leadership. I think it's mostly this. Just to see what it brought up, I'm asking for three mocks: high fidelity, real feeling, pixel type, with tech and warm just to have some contrast in both views, pick a direction because I don't want any brand just yet. What do you think? 

Yeah, I mean, I'm definitely on the same page there as far as—I don't think we need to like LiftFoil's branding and how it goes and what's there, because the success story about LiftFoil is having that place where they can monitor the orders in and out, like where it's going, if it's following the compliance. It's really cool. I have it right over here. This is the Open Design. Yeah, I might steal that shit. Yeah, bro. And it's a really juicy problem. I'm sure you got your finger on the pulse on this stuff since you're probably doing a lot of very... anything interesting in this repo? So I'm glad you showed me that. 

Yeah, bro, just give it a hack and to be honest, it's fucking annoying at the beginning, then you'll get it sorted out. Because I think one of the issues is that everybody ends up having their own workflows, so everyone ends up having different modifications to skills or different agents. Keeping quality and checking it is a problem because if someone's using a degradative version of a skill or an agent, then the output is going to be different. How's their workflow? How are they tested? How are they iterating over the problem? How are they making sure that the models are not hallucinating, that they're adhering to rules, and it maps the template of rules to the empty? 

So nobody pushes the empty; they push the template. The template is the same for everybody. If anybody has a new rule that Claude needs because of something that happened, right? They push it to this template. They update their Claude MD personal, they do a push to GitHub, and then everybody pulls the latest, and then they use the skills, and then it reads the template and it passes over the update to the Claude empty without any issues. That's one of the many, many, many other issues that comes with working together with agentic environments. Yeah, and yeah, it's just finding... yeah, it's hard. I kind of—we all already know, we've already kind of solved it, but I feel it's different for each team.

Because it depends a lot on how you work and where you go to present the data. We used to use ClickUp, but then we started finding better ways to communicate documents or parts that we need. It depends a lot; it's really hard. It's one of the problems that we had with my team.

I know there are many ways to bake a cake and not all of them are right. Amen, literally bro, literally. It's a pain in the ass at the beginning, but once you guys set it up, it should be good. 

One thing I'm thankful about is that this project in particular is about enabling non-static publishing with an Anthropic plugin soon. Oh, what's the plugin? Let me see. I do have it in CRM. This is work stuff, but I pulled it over. It's not here. Let me see if I pulled it over... and I do have it, right? Pardon. Yeah, it's right here because I did add it. Let me see if I added it here. No, it has to be global. And if it's global, it has to be in skills. I don't have it. 

Well, no, if it's global, that means it's in your root directories.cloud, yeah? Well, yeah, but the way that I open my root is with all my projects inside; I like to do this. So this is my root technically—projects—so it would be really right over here on top of CRM. It would be cloud, and it's not here. This is the CRM one; I want to check the CRM because this is where I pulled it from. 

No evals, no clean all, no requirements. I definitely see it in your .gitignore there. Yeah, it is in my .gitignore, but I'm looking for the file and skill name: "general hardening." Okay, and then copy path and let's see where that... Project CRM.cloud, bro. You were looking at it. Project CRM.cloud and it says skills. No, no, no, this one—I think nope. 

I would love code. Yeah, there's a lot of accents; that's the thing: graph-powered code intelligence. Do we use this a lot at work? I found it, and after that, I'm looking for the dashboard. Oh, there we go. We haven't stopped using it. So it provides a knowledge graph of your code. Agentic bots most of the time, they just hallucinate and they don't know what they are. Or let's say that you have a page and there's already an element created, and it duplicates it because it didn't see that it had that element created prior to that it could use it. 

Well, Axon helps with that. So what do I do with this? I plug it into the skill and then it looks at my tasks. It analyzes it—the task it indexes with Axon—it looks at the coverage map that it provides so where that issue or plan is. If I have security, it will pick up a security. 

So it's a finite state machine. It comes to mind when you said the skill degradation, because one of the degradations is you want to implode them with shit always; then quality lowers as well. So it goes into the finite state machine and it says, "What stage am I in from the pipeline? What are the tools that... and what am I going to invoke depending on the material that I have?" Am I substantiated? Do I have evidence? No. Then I need to gather it. Do I know what I'm... to do research. It iterates, iterates, iterates, iterates, iterates. It takes all the deliverables and starts testing them one by one, taking screenshots. That subdirectory has two subdirectories. So it's success or fail? To success, it works. 

Question for you: let's think screenshot for every single valid validation, to throw away anything. I like to have context because then it forgets. So there's a ledger and there's a review and there's a markdown progress harness. It's housekeeping, and then you have clean all. So I wanted to do housekeeping first, but then housekeeping was too lengthy, so I broke down housekeeping into four: keeps GitHub issues, enterprise architectures for modularity and scalability—and it implements it for you—and then any still process that you have in the back end, it starts closing it out. 

So, down into sister skills. And then, if you don't want to do cleans on something that it shouldn't be cleaned—it's not explosive or destructive—but still, I don't want to use it here, but if I do hard and doctor... I should do harder than doctor with general hardening. I still need to read this. 

And then the three directions, do we need to choose that? Like, I mean, I'm not a fan of large serif headlines mono kickers; one warm accent confident leadership deck feel is great for exec review slides, but it's tough, you know. A web application we're building, so I think that's safe for our mocks. Ooh. Let's do gold accents. Yeah. Okay. All right, let me see if I have a go at it. 

Yeah, absolutely. Pretty sweet, and I'll show you the documents for it. I don't have them right here; I wanted to show you the diagrams and how it worked. I have it in the actual skills folder, but it works best... At the end of the day, take a big skill, break it down into smaller skills or sister skills, create a family of skills, and then they communicate between each other. The best way is to make it interoperable with itself. It's like having an FSM harness in hand. And that's how I've seen it. 

Thank you. I'm thinking like if I were to spin up some sort of janky gate for certain tasks in the workflow: if steps one and two pass this way, settings.json where parameters for this stage are. And it would discern which stage it is at, you know? So, the classes and everything—documents that it will start creating. This reads the hardened intake, it substantiates, right? It designs. Evidence, local test results, PR open, and then ready to merge.

It researches, if need be, to understand why it's not working, and most of the time it gives you a solid answer. So it brainstorms, investigates to find out why it's not working, and then it jumps to name is Class D Bug Fix with TDD Red-Green that Claude gave it. It gets Class D bug with the reproducer, presses the stage two light, stage five in both super five. Okay, so this is the part where it starts developing and starts substantiating, and then it updates the hardening intake, which ledger, right? You keep iterating through this stage until you go into four. All these documents are getting read; all these documents are getting funneled. General hardening—this is not the full FSM, actually much, much longer. You would basically break it down into these; it adheres pretty good to this.

Yeah, I mean... And to be honest, what you start like putting in hooks there for commits. So every time Claude is doing a commit, do this except from doing the fucking job. You know, it loves it, because sometimes I do want him to go off. Right? And I'm like, "She's bro, she's the best practices. She's the best answers." Ah, an ephemeral chat, which I really like as well. Code is that. Absolutely. Codex has it too. Codex, if you put like, slash side, yeah. I love that shit. Chat. Like, it's so annoying that you can't fucking follow up with P2. I can't do over here is fork. Mm-hmm. Fuck says oh bro, it's so clunky. Come on, Amelie. Come on. Yeah, like, dude, use Mythos. Quite actually, bro. It's fucking insane. Fucking insane.

Bye. Anything per se, but to the plugin, it's helped us out to push the CMT. We did a complete CRM in three weeks, bro. It's fucking insane. They put me as the lead of the project. It was app.cmt.com. Yeah, should be this basic shit. I think I... Matt Burr. No, it's a good one. But I do... well, there's a website that I created for work. I hate it, delete from this website. So it's basically they need that compliance for attorney-client privilege. So there's law paralegals because they need to maintain that attorney-client privilege, which is like protected by—um, it can't be on a cloud or anything. 

So I needed to deal with like extraction. Mm-hmm. That hasn't been used in a minute. I don't like out; this was high peak when I was actually working on it, you know? Can render it right. It's here. I can zoom in or whatever, and then I could see the correct just go approving or doing anything. And I also added this history, so this is like no re-extract, and let's say that I approve it. I see a document right over here. And then you see the history down here, which is pretty nifty. And then if you want to export it, you can export it; it will already have my email prepared with the data extracted. I don't know why it's other. Yeah. Deep blanking on opposition, whatever have, I really love this. Did this alone, only a month—the backend spinning up local model being trained and everything. And then I also have more; there's logs for everything. They will appear here. They're not coming next because I have an idea for it. Any tenant I receive, and I receive pictures century, but more as an admin, I can see it right over here and I can see the test or the 555, and then I can get back to them.

Really, that's me. That's my boy, Gabby. Yeah. But I don't care if you see my password, I just want to make sure that I have it right. It's, I mean... Maybe you broke off earlier. Maybe man, I'm just kidding, is this Cloudflare? No, it's not Cloudflare access, I was gonna say. And he was like, "Yo, Gabby, this fucked." Thank man. You're supposed to know more, right? These pages or something like this—see that it's fitted or can paginate inline in the card. Something like this for lift foils, right? Graph, love the animations that you're at it. Them too, bro. They're so nice. Out and then the line going, I love it as well. And then eat. Move this over here. I fucking hate you, bro. Huh? Let me get you out of the way. 

As a test yesterday, I created this beautiful, beautiful PowerPoint presentation. I did. I did. Think they're really going into, they're really grinding out bat when somebody used, like, I don't know, the image or when Nano Banana came out and it was really, really good. But hard to like, is it AI? You don't know, you don't know. No, I mean I had some prototypes mocked up by GPT Image 2; it was like it's an image or source, not as preview. Okay, that's good. Full screen with it. Mm-hmm. There we go. OK. Better. Okay, this is the index. Could be a good, let's say... Yeah, most definitely. Most definitely we can add this to like a slide. You never know. From this for compliance, better tracking. Um... Thanks. 

I like how it presents it right over here: color-coded bars, and then it shows the top. Okay, exception—fewer, more top age ones. Yeah, think of overwhelming them. And yeah, the second one is just a little too cluttered; a lot of decimal places and numbers that might not necessarily have any bearing on what the system is doing. So yeah, just first initial thoughts: I'm definitely feeling that first one over the second comments. Yes. And then that's just for us whenever we move on, by the way. Oh, that sounds good. 

The one thing I'm not sure of is like—yeah, it's just like too much here, but I like the clean... exactly, the design is really nice and there might be some use for some sort of like summary heading at the top where it's just "these, this many packages were shipped." Just thinking out loud of like how we might use that space. But it doesn't necessarily have to, because it could be a pending process of an action that was made. Right, actions, but actions is the overall, and then you have active misintending. And then yeah. All right. Yeah, it's definitely sexy, that's for sure. Mm-hmm. Really nice.

It's in calendar being accessible, easy—add all these comments? This call is being recorded on my computer by a local model. Good, it's great. Please, this comment. Okay, I'm just trying to get a little bit more familiarized with it.

So, Operator 2, two of chat bar, it's like what you know in the second dashboard? The one that was carrier mix, which was cool. Worry about you going too far down one path and then Connor's like, "I'll throw it all away and do this." Not that I agree—not that we'd have to listen to him or anything—but just getting Connor's sense like, "Oh, that's important," "That's not important," and like, "Oh, if we could bring that, you know, to top of mind."

No, but I completely agree. Sometimes you can hyperfixate in the rabbit hole and it's being more costly than just doing it simple. At the end of the day, simple is better. For the foreseeable future, types that we whipped up as we were merging from these three designs—I like this part; it is more minimalistic. 

Okay, this is the one that I wanted to talk about. Yeah, this is the one that's missing. You can hover over and see a flyover of what it is. I preferred this one over... color-coded, I can understand which one it is. Yeah, I like it better like this. I'm sort of on the same page. It should be more of a comparison chart with carrier mix from the third. I like how the other ones have it; they made it look like a live stream. So, is it worth building some fucking mock functionality that only a couple people will see? I don't know. 

The constraint will be: when do you need to present it and is there actually value in it overall? The idea is to receive one or two orders every 30 minutes; I don't really know. We would need to know exactly that volume, I guess, right? It comes with recurrence, like what is the... It's super valuable. Yeah. It has no bad—one person sees it and it's going to be an accident, like, "Yo, this auto-refreshes on XY time." So we could say that it's not necessarily seen. In a tech shop, I imagine nobody's gonna be complaining if we throw a refresh button up. Yeah, and maybe that's something where we could have the availability to reload the page. 

You know, it sounds like these guys want it in an animated fashion—just like "three new jobs" and a toast notification, or "three new rows at it," making it look and feel sexy before we do a demo or anything, you know? Interesting and valuable. Oh, can you click on the side items in that index? Like, sorry, queue and ships—what displays is it? Ah, fuck me. Yeah, I was just curious; I figured it out. Aha. It's the same, right? Okay. I think there's the other one. You have to click one over here and then click here. Oh my god, yeah, that's like the last one, the last, last, last one. Well, if they are old people, like old-type school—okay, Boomer. Have fun with your congested dashboard. Literally, bro. Oh, fuck me. 

The other design that we're sort of slating, I guess it was the third design, here is why: exactly, just like empty negative space for no reason. That's where my head's at, at least. I'm not sure if you've got any strong opinions here. Yeah, no, what I think is we can take the... I think that's right, number two. The more I see this, the more I like it because it gives me the preview of the day. I don't know how much is needed. And to be honest, this can be passed on to the public bots, so it's not needed. But that's exactly it. Like, I think it's like a card with, ah, here's at the top of your page somehow—good, but I'm sorry. Yeah, I'm going to go Hero cards. I won't ponder anymore on that. 

Like, I like that it's held for review, but I don't need that much information. Yeah, I agree on that. So now, right, and then there's what I'm going to do. Come over here, read the index codebase that we have. Sean, are you able to—I always forget, I'll try it with you. Yeah, Pip, yeah, I already did this. Where was beginning? Accent UI? Oh, I did. Were you missing the A? Yeah, I'm not sure. Where do I have Axon actually, bro? Are you retarded? Yeah, for real. No, me too. Melissa Lee, CDA, City thought... Bro, I'm inside Axon, how do you say it's not? Yeah, that's definitely where my mind would go. 

I'd also wonder, it's not an NPM package there, right? Huh. Yeah, I was gonna say, like normally with a CLI package that's Node, you'd be like, "Maybe I gotta link the package so that it's available globally," but that doesn't appear to be the case. Excellent IQ. I've already got an indexer running in the background, but I'm downloading it right now. Bro, this dude's tripping. That's probably should be axon-index-ui. Set up cloud cursor MCP server, I think. Yeah, it's actually an initialize and then full, but it's inside there. Let me see if I can call it. Hooray!

**System Audio:**
The other thing, I'm gonna see if it's fucking me. You never know. Let me see. Can you imagine? Could be. Bro, I think it's me. Holy shit. Damn. Let me see if this works. Wait, wait. Oh, I think it's me. I think—God damn. I'm so sorry, man. I'm like, "Well, it's your problem." Yeah. No, no, no. At least we figured it out. Where the fuck did I put that shit? I'm getting... Oh, thanks, man. I am definitely fucking allergic to mornings. Yeah, for real.

Alright, so I just wanted to crunch out. We're going to be meeting with Connor on Friday, right? It's going to be during the night. Okay, but that's good. Alright, so I'll just take this. I'll do this. Yeah, I put... should be it, right? Um, no, it's C-fat. It's C-fat, so you're very fat. Okay, and that's the—yeah, that's the token, that's good. And then I'll just copy this. So I'm going to save this and then I'll point it to this session. 

This session was just a... The deliverables that I had at the moment, the reviews that I was doing on what we had and what was missing. These were particular things that I found: like, at least all headers in the tables need to be toggled for filter view. So you hit one of the headers and it auto-filters to, like, ascend or descend. It needs a dashboard. And I was wondering what KPIs we could represent for Lift Foils. The queue is good, but in terms of the analytical side of what they want to see—I don't know which KPIs they are looking into. I would need to read the handoff. Again, I think they are there. Yeah. Beautiful. Beautiful. Beautiful. 

And then the ops agent pain needs to have an adjustable side if the stack gets long or anything. Yeah, it already cleared it, but now it actually, like, goes through each order on the first run and you can see the orders being scanned. Instead of seeing 0 to 37, I might check on that again just to make sure it's not a bug, but you see "1 of 37," "5 of 37," "10 of 37" being scanned. It just gives trustability. I find this really good. Held, auto-cleared. I love the pagination here. Seven day... clicking on these, I was going to work on it. I know we talked about it, but clicking on them so we can have a detailed view here—we have a lot of space that we can work with. The barrier batches, and they opened well. And then compliance. So we do have a [view of] how they are being completed. 

And then I see the connectors. This is the NetSuite TalkRest and these are the external systems that are going to be wired to Lift Foils dispatch. So we have Cloudflare, Anthropic Cloud because that's going to be the agents. We have the recent transaction email, the ShipEngine, the EC Port Rate, and the NetSuite, which is the API that they have. Obviously, it would be good that these were toggled so if I click on them, I can have them or they paginate to somewhere else. 

What else was I thinking? This open design. Open design is a reverse-engineered open source of Anthropic's cloud design. It's open source, completely open source. I was going over here what I wanted. So I stopped because I said, "Let me do it with Cam." So I was like, what's the primary use of the dashboard? It's going to be dispatch operators, compliance officers, operations, and leadership. I think it's mostly this, but I wanted to see a mix just to see what it brings up. I'm asking for three mocks: high fidelity, real feeling, pixel tight. I'm going with tech and warm just to have some contrast in both views. Pick a direction because I don't want any brand just yet. What do you think? Right? How it goes and what's there, because the success story about Lift Foils is having that place where they can monitor the orders in and out—like, where is it going, if it's following the compliances. The most important is the threshold of... And then a lot of fucking skills and shit that already comes in, some shiny skills as well. It's crazy. It's really, it's really cool. I have it right over here. This is the open design. 

Yeah, bro. It's really good. Let me see if I can show you the... Google systems. Thank you. Yeah, bro, just give it a hack. And to be honest, it's fucking annoying at the beginning. Then you'll get it sorted out because I think one of the issues is that everybody ends up having their own workflows. They end up having different modifications to skills or different agents, and then keeping quality in check is a problem because if someone's using a degradative version of a skill or an agent, then the output is going to be different. And how's their workflow? So how are they testing? How are they iterating over the process? 

The MD—so nobody pushes the MD, they push the template. The template is the same for everybody, but if anybody has a new rule that a cloud needs because of something that happened, right? They push it to the template. They update their Cloud MD personal, they do a push to GitHub, and then everybody pulls the latest and then they use the skill sync skills, and then it reads the template and it passes over the update to the cloud update without any issues. It's one of the many, many, many other issues that comes with working together with agentic environments. 

Yeah. And... yeah, it's just finding... Yeah, it's hard. We already kind of solved it, but I feel it's different for each team because it depends a lot on how you work and where you go to present the data. Like we use ClickUp. We used to use it, but then we started finding better ways to communicate documents or parts that we needed. It depends a lot, man. That's—it's really hard. It's one of the problems that we had with my team. And yeah, I know where I'm at. You at amen literally, bro. Literally, it's a pain in the ass at the beginning, but once you guys see... So let me see, I do have it in CRM—this is work stuff—but um, I pulled it over. It should be in... it's not here.

Let me see if I pulled it over. I do have it right here because I did add it. Let me see if I added it here... No, it has to be global. And if it's global, it has to be in skills, and I don't have it. Well, yeah, but the way that I open my root with all my projects inside—I like to do this—so this is my root, technically: projects. So it would be right over here on top of CRM; it would be dot, like it would be cloud, and it's not here. This is the CRM one; I wanted to check the CRM because this is where I pulled it from. 

But let me do a quick prompt... prompt, prompt, prompt. There's a template: create PR, no, no, no, no, evals, no, clean all, no requirements. Yeah, it is in my .gitignore, but I'm looking for the file and... Oh, skill name: general hardening. Okay, and then copy path and let's see where the—that's it: project CRM cloud. I was just there: Project CRM cloud, and it says skills. Oh my God. No, no, no. This one, I think. Nope. Code base index. 

Yeah, there's a lot of Axons, that's the thing. This one: graph-powered code intelligence. And we use this a lot at work. I found it and after that we—I'm looking for the dashboard. Oh, there we go. We haven't stopped using it. So it provides a knowledge graph of your codebase. So, you know, a general... LLMs, most of the time they just hallucinate and they don't know what the fuck they are doing. Or let's say that you have a page and then there's already an element created and it duplicates it because it didn't see that it had that element created prior to, right? That it could use it. Well, Axon helps with that. 

So what do I do with this? I plug it into the skill and then it looks at my tasks. It analyzes the task. It indexes with Axon. It looks at the coverage map that it provides so where that issue or that task is going to target, right? And then it says what I need to modify. Right. Agent, and it will review the security part. So it's basically a harness. What I created is an FSM needed. So it goes into the finite state machine and it says: what stage am I in from the pipeline? What are the tools that I have? And what am I going to invoke depending on the material? And then you want to implode them with shit, and that's error number one because adherence lowers. And when adherence to the skill lowers, then quality lowers as well. 

So it's a finite state machine. It comes to mind when you said the skill degradation, because one of the parts of skill degradation is that they become lengthy. So peer review, hard in the plan. So it summons agentic agents to review the parts that are purchased. It creates a subdirectory, right? Let's say success or fail, right? So all the screenshots that are success go into success and all the screenshots that fail go to fail. I can research, cut off. Then I have to do research. It iterates, iterates, iterates, iterates. And then at the end, it does a battle test. So it spins up a local environment that I have. Am I substantiated? Do I have evidence? No, then I need to gather it. Do I know what I'm doing, or is my training knowledge the screenshots and see the deliverables and evidence of if it actually got done? It works. Yeah. 

Mm-hmm. Everybody can have it; it housekeeps your codebase architecture. And if you don't have an architecture, it researches top-tier enterprise architectures for modularity and scalability. So I wanted to do housekeeping first, but then housekeeping was too lengthy, so I broke down housekeeping into four. It housekeeps GitHub issues; it housekeeps sessions, so it can keep tabs on what's been doing. And if an agent did something, it can corroborate it. So I do push it to our git to have context because then it forgets. So there's a ledger and there's a review and there's a markdown progress of what's going on. I don't like to throw away anything. 

So I'm going to go ahead and see what's going on. It implements, starts closing it out, running and cleaning out shit. Because... not explosive or destructive. But I've used it like four times and I've really, really liked it. But still, I won't—I don't want to... Let me see. Sign, and where the fuck did he put it? Or no, very. Let's vary. Right? Yeah, yeah. It's a fan, or to go with accents. Fuck it, do something else because it has no task. The sign, open the sign. There's no need to harden this. 

Let me see if... Once I publish it and I make sure that everything's done, but it's been the actual skills folder. Or sister skills, you create a finite state machine harness. It doesn't need to take very complex ideas or skills and actually make them work, you know? No, no, no, no. But yeah, you're in the right thing because you would need... Thank you. You can declare what are the parameters for the next stage and how it would—hardening intake. What is what I'm going to class A, and then keeps proceeding on the nine stages to produce the named artifact, right? It does either serial cases, it does a plan, and then skills invoked: brainstorming plus investigate. This is a problem or issue or something that you need with external research if need be, or understanding why it's not working. And then it jumps to the ID too. It still classifies the class D bug with the reproducer, compresses the stage 2, light, stage 5 in bug supervisor.

The name is "Class D Bug Fix" with TD red, green, whatever. That is the name the cloud gave it, I guess. But it's basically a subprocess that needs to be completed and then it adheres pretty good to this, you know, off-base eval. All these documents are getting read, all these documents are getting funneled, and there are other parts because this is just one. This is the part where it starts developing and starts substantiating, and then it updates the hardening intake, which becomes the ledger, right? And then it orchestrates them and they call each other.

To be honest, when you start working with the local settings JSON, like putting in hooks there—cloud adheres to hooks and hooks are very good because they fire on certain conditionals, right? So you can put hooks for commits, put a hook practices, choose codebase. And then once I have what came out, I'll study it and I'll be like, "Ah, right." Or sometimes I'll do fork on cloud. It's so fire, bro. But for it, it could be... man. And it says, "Oh, you can resume the other conversation by using this string." Bro, I'll do it, fuck it, I'll fork, right? Fuck it. I'm in a new conversation, but I still see the old conversation. I don't want to see the old conversation. So clunky. Come on, Emily. Come on, bro.

It's super over the top, that skill, the app, CMT, tiger teams, team at work. Ah, boom. I changed this—change it again? I think I forgot a password. Not going to do that. No. Look, I want to show you this one I created. There we go. So it's basically machine learning, AI extraction for paralegals. So there's a law that's regulating AI—well, let's say IPA or whatever—but like, spinning up a GPU server so that I can download a model. Then a minute, let me move this out. 

And yeah, 30 days or anything. There we go, right over here. The correct document that is approved with all the fields that got approved with their percentage of confidence. What were the approvals or what were the corrections? Blah, blah, blah, blah, blah. And then you see over here, I see it approved and I see a document right over here. And this is the docs go approving or doing anything, right? And I also added this like history. So this is like, "No, remember that I told you this" or whatever. Then if you want to export it, you can export it directly, and then boom. Yeah, exactly, the permissions and everything. It's really, really nice. This was my project manager. I did this shit for this project. 

And then there are parameters on the models and making it more cost-effective for any tenant that wants to use the app. And then the feedback that I receive—and I receive pictures—the training signals is what's coming next. It's because I have an idea for training different models and then lowering the feedback, right? With new or received, it's like a type of sentry, but more in the UI admin, which is really nifty. To be honest, I really... it is me. Yeah. But it was intense. It was intense. I made it through, and then they gave me the fucking CMT, which I hate with my life and I'm dying, bro. Bro, I swear to God. 

Can you make it work? See that it's fitted over here. Something like this for lift foils, right? Lines or right? I love them too, bro. They're so nice. Like taking them out and then the line going beep, beep, beep, beep. It's like, "Fuck you, man. You're supposed to know more." But yeah, I was thinking about... okay, so let's open. Let's see, open full screen. Oh, but did you like it? Because cloud is not very good at being creative with front end—AI to create a front end. And with the ChatGPT 2.0 now, the image... it's really hard to tell, is it AI? It's getting insane. But I can do that. That's good. And I'm just still really mad that I can't fucking... 

Okay, yeah, we can add this to like a slide over and then we can ponder on this style for... Pass rate. I like pass rate here: color-coded bars, and then it shows the top exception queue needs ships, mints, and flight DG compliance 93%. Okay, exception at DG rules. I like this for compliance better—tracking the platform connectors and notifications. That's good. Audit chain and attestation, not bad. A landing page that they wanted, which I doubt, but you never know. From this, I like the dashboard: queue shipped, calendar dispatch, you know? I am clean. Okay, this could be a good, let's say... yeah. 

You fucking asshole, stop, let me move you out of the way. You don't know, you don't know. Yeah, near grayscale, blah, blah. These are $42 average, the fuck up. But this is more like mono. You know, it's more like code. Yeah, I agree. Normally, I'm not going to battle with it. Whatever. I'm not going to... yeah, fuck this. Okay. 

And then the third one. This one is very clean. Too much here. I like the clean. Actions to take, and that would be... mist pending process of an action that was made. Okay, those three could be... right. Yeah. Well, there's the index. Let's see the dashboard. Huh, this one. And I want to add them. I think that should be it. I don't know if this is needed. Jesus, this stuff. Like them. Oh, DG compliance. Let me see from operator two, two of the three holds are a lot 24 A of the... Beautiful, beautiful. That's good. Describe this sign you want. There's a comment. No, boom. Oh, cool. Thank you. I agree. So they can see the intentions platform and application, which would be good. Hero cards, fine. This is more minimalistic. I believe nowadays that like the sidebar—I would add the sidebar over here, a button, right? I would like this as well. Just click them all. Yeah. Harrier mix from third. I like it with... yeah, so let's do this. I'm going to pick the first one. No, no, no, no, no, no, no, no, no. And I get it color-coded.

I can understand which one it is, but yeah, I like it better like this. The live stream, a trip. Mmm. What's the overall idea? What's the constraint will be... When do you... Thank you.

Hmm. Yeah, so we would need to know exactly that variable. The variable is, what is the variable? But volume comes with the rate? So if they have—but if they have a mid to low rate at all, there should be a reload. Yeah, it doesn't give him; yeah, it only does three mocks, it's currently static. Ah, fuck me. To be honest, I really like other ones. Oh my God. Yeah, it's like, whoa. This is awesome. Okay, boomer. Have fun with your congested dashboards. Mm-hmm. Literally bro, oh fuck me. Well, if they are old people, like old type school, like they might like this. Yeah, why? Aesthetic of number one, two, with carrier mix from third. And the more I see this, the more I like it.

Yeah, no, what I think is we can take the—yeah, thank you. To be honest, this can be passed on to the bot, so it's not needed. Like, uh, I'm just going to ponder no more on that. I don't like this. Yeah. Exactly. What I want to see is—I don't want to ruin the mux here. Let's do a prompt. Come over here and then I'm going to go over here, call Axon, "give me the number of pages and services." And I should be able to—I always forget their command. I actually never tried it, so I'm going to try and... wait. And there we have. Also, Axon should be on: view sample flows, I need refactor user class, knowledge graph model, fine, fine, fine, this is good.

Where was the command you're prone? Axon UI. Okay. Fuck you. Ah, yeah, it's not global. I have out. Axon UI. Bro, are you retarded? Axon UI. Bro, I'm inside Axon. How do you say it's not? Maybe I'm having PowerShell. Yeah, for real. No, me too. LSLA. It is here, right? I am looking at it. I didn't talk to you blockages. Pip. Yeah, I think it was pip install IQ, but it did use PowerShell. All that's probably it. Next: impact, dead code, cipher, watch host, UI setup, cloud, cursor, MCP server, I think. So it should be now. CD back. Suspicious detected.

Cameron and a collaborator held a working session focused on the **LiftFoil dispatch dashboard** project, reviewing three high-fidelity mock designs and converging on a hybrid direction: the clean aesthetic of designs #1/#2 combined with the carrier mix visualization from #3, using gold accents and no brand identity yet. They cataloged UI gaps — sortable table headers, KPI dashboard, adjustable ops agent pane, compliance tracking views, and connector toggles for external systems (NetSuite, ShipEngine, Anthropic Claude, Cloudflare). A significant portion of the session covered **agentic workflow management**: FSM-based skill harnesses, Axon (graph-powered code intelligence), skill degradation prevention via shared templates, and hooks-driven quality control. They agreed to hold design decisions for Connor's input at Friday's meeting rather than going too deep down any one path.