Exhaust the enemy's strength without fighting. Weaken the strong by nurturing the soft.
— The 36 Stratagems, "Wait at Leisure While the Enemy Labors"
P flipped the business card over and wrote one letter on the back: P.
Then P walked into the conference room.
P didn't do opening lines.
P doesn't have a name — not yet, not in this series anyway. But if you've read the earlier stories, you'd recognize the signature.
The first story — P's own article got flagged as "low quality" by the company's AI moderation system. P dug into the internal API, pulled 347 flagged records — effective accuracy came out to 38%. More false positives than correct identifications.
The second story — an AI payment gateway processing $2.8 billion. The CTO backed it with formal verification, claimed it was "mathematically bulletproof." P spent eight months quietly building an adversarial testing pipeline, and proved the gateway would approve illegal transactions.
P won both times. P left zero fingerprints both times.
After those two jobs, P stopped working for other people.
This time, P got brought in as an independent evaluator.
Two Companies, One Customer, Zero Questions
The customer was a mid-sized industrial IoT firm called FirmCore. Their production-line gear had been running for almost a decade. The monitoring system was going down once a month, and management had finally had enough. They decided to bring in an AI monitoring platform.
A good call — right up until they decided to run two vendors through POC at the same time and pick a winner.
"We want to see who can actually cover our failure modes," the VP said in the meeting. "We've also brought in an independent evaluator."
P was that evaluator.
The two AI monitoring companies were MonitorAI and SentryWave. MonitorAI's pre-sales team went first, slides blazing with "99.3% fault coverage, validated across 3 manufacturing customers." SentryWave followed right behind: "99.7% coverage, 7-day deployment" — bigger numbers, bolder font.
P sat in the corner, laptop open. P didn't write a single word.
The meeting wrapped. The client team gathered around P. "So, what do you think?"
"Nothing worth saying right now. Give it three months."
P didn't ask either company a single technical question. Didn't pull their data, didn't check their architecture, didn't ask to see prior POC records.
"Three months?" the VP pressed. "The POC contract is three months. What if you can't deliver a conclusion by then?"
P didn't look up. "Three months from now, I'll give you data. Right now I can't — the data hasn't spoken yet."
"At least give me a monthly update."
P didn't say yes. Didn't say no either.
The VP was quiet for a few seconds, then nodded.
P added one more thing: "I'll set up an independent data pipeline for the evaluation. I won't tell you in advance which metrics I'm tracking — if I do, you'll just stare at those numbers, and then I won't be measuring you anymore."
The VP gave P another look, then nodded.
P spent a week going through FirmCore's security review. Read-only replica access, config registry access, model metadata read access — every layer required a sign-off. The security team triple-checked "read-only, no impact on production, no change requests" and cleared it. Since it was just read replicas, fitting into an existing data audit framework, the approval followed a standard template and took exactly one week.
End of week one, P had a read-only replica pipeline running alongside FirmCore's production environment. Connected to more than just the real-time event stream — it was also hooked into the config registry and model metadata. No writes, no config changes, no production impact. Through the config tables, P could see exactly which data sources each vendor had connected to, without waiting for every failure type to trigger naturally. FirmCore's own ops team was drowning in production-line alerts every day — nobody was going to go digging through vendor config registries. That wasn't their job, and they didn't have the time.
Month One
MonitorAI's dashboard went live. Three numbers on the big screen: real-time fault detection rate 97.8%, false positive rate 2.1%, average response time 1.2 seconds.
Their slide deck had said 99.3%. P noticed the gap — and said nothing.
The VP posted a screenshot on Slack: "Now this is AI monitoring."
SentryWave didn't flinch. Their dashboard showed 98.2% detection rate, 1.8% false positives, 0.9 seconds average response — every number just a hair better than MonitorAI's.
The client project manager sent out a weekly progress email. Two tables, numbers polished to a high shine.
P read those emails. Then P looked at the data in the read-only pipeline.
Behind MonitorAI's 97.8% coverage number: out of 61 known failure modes, only 29 were actually covered. The remaining 32 — MonitorAI hadn't connected to the corresponding data sources at all. But the dashboard didn't say "uncovered," because their AI model counted false positives from similar patterns as "detected."
SentryWave's 98.2% was subtler. They'd connected to 34 data sources, but on 5 of them, the detection thresholds were set absurdly low — generating 200+ false positives per day. Those false alerts got auto-sorted into "low priority" and never appeared on the VP's dashboard, while FirmCore's ops team quietly dealt with them in the background. P knew: if SentryWave didn't fix the root cause, those false positives would keep coming for the full three months. Another 5 sources had thresholds set conservatively. P judged that if SentryWave later raised those thresholds further to suppress the false positive rate, detection on those categories would almost certainly drop below 50%.
By the end of the first week, the pipeline data already told the whole story. P closed the laptop. The rest of the time was just waiting — three months in which P would tell no one that the answer was already known. P had gotten used to this long ago: If you know too early, no one believes you.
Not time to speak yet.
Month Two
MonitorAI started bleeding.
Their model hit data drift in production. One of the production lines had sensor frequencies that didn't match the POC phase — MonitorAI's training data hadn't covered that frequency band, and the model started flagging normal fluctuations as faults.
Week one: false positive rate climbed from 2.1% to 7.4%.
Week two: 15.2%.
Week three: FirmCore's ops team muted MonitorAI's alert notifications.
MonitorAI's engineers pulled all-nighters retraining models, shipping patches. But every time they fixed one batch of false positives, a new batch surfaced — their training set simply didn't have data from that production line. Patches couldn't fix a fundamental coverage gap.
SentryWave seized the moment. They fired off an email to the VP with the subject line: "Stable, Reliable AI Monitoring — SentryWave's 30-Day Zero False Positive Upgrade."
P saw the email. P's reaction was nothing. The read-only pipeline showed exactly how SentryWave got to zero false positives: by raising detection thresholds. Fault detection rate dropped from 98.2% to 79.4%, but no one noticed, because no one was checking for the faults that weren't being detected.
P wrote a single line in the notebook:
"79.4%. It's safe now. And useless."
Then P closed the notebook and went to get a coffee.
Month Three
Both companies were struggling.
MonitorAI's production-line data drift hadn't been solved. Their second model update pushed false positives back down to 6.8%, but the cost was detection sensitivity — the detection rate fell from 97.8% to 83.1%, and genuinely new failure modes started slipping through. A patch nudged it back up to 86.4%, but new modes were still being missed. A bearing fault on one of the lines went unnoticed for 48 hours — until it triggered a cascading shutdown.
The outage lasted 4 hours. Estimated loss: roughly $47,000.
SentryWave didn't have data drift — because they'd chosen the most conservative integration approach, connecting only to the most stable data sources. The problem was, those stable sources happened to not cover FirmCore's most critical production lines. And those 5 failure categories P had flagged in week one as likely to drop below 50% — in month three, their detection rates landed exactly between 34% and 48%, matching P's assessment from three months earlier to the decimal point.
Final week of month three, a SentryWave config change triggered an alert storm. 3 AM. 1,400+ alerts in 20 minutes. 1,380 of them were false positives. FirmCore's on-call engineer got woken up seven times. PagerDuty went nuclear.
The next morning, SentryWave's explanation was "a one-time event during config migration." But the ops lead said one thing in the postmortem, and it made its way to the VP:
"I'd rather have no AI monitoring. At least I wouldn't be waking up at 3 AM to confirm a fake alert."
The VP didn't say anything. He looked at the increasingly ugly numbers in the weekly progress emails, then turned his gaze toward the corner where P had been sitting, silent, the entire time.
"Your evaluation. Where is it?"
P Had Been Waiting for Exactly That
P pulled a USB drive out of the bag. Plugged it in. Opened a folder.
Inside: four tables. That was it.
Table One — MonitorAI's real coverage:
Claimed coverage: 97.8% → 99.3%
Actual failure modes covered: 29/61
True coverage: 47.5%
The 32 uncovered modes include: high-frequency sensor fluctuation, cross-line cascading failures, multi-sensor joint anomalies
Table Two — SentryWave's real coverage:
Claimed coverage: 98.2% → 99.7%
Data sources connected: 34/61 (5 with thresholds too low → effectively 0, another 5 with detection below 50% after threshold increases)
Effectively covered: 24/61
True coverage: **39.3%**
Reason for gaps: connected only to the most stable data sources, avoiding critical production lines; sacrificed detection sensitivity to suppress false positive rate
Table Three — Three-month trend comparison:
MonitorAI: 97.8% → data drift → 83.1% → patch → 86.4% → missed detections
SentryWave: 98.2% → raised thresholds → 79.4% → alert storm → muted
P's parallel data: 47.5% / 39.3% (true failure mode coverage — not the fluctuating detection rate on the dashboards. Static. Never changed from day one.)
Table Four — Complete failure mode inventory:
All 61 known failure modes, each annotated with which company covered it, coverage quality, and — which ones neither company covered at all.
"There are 12 failure modes that neither company covers," P said, voice flat. "Those 12 modes appeared in 9 of your P0 incidents over the last two years. So even if both POCs had been successful, you'd still crash in exactly the same places."
Nobody in the room said anything.
The VP read through all four tables twice. Then he asked a question that, in three whole months, no one had thought to ask:
"What's our real fault coverage? Do we have data on that?"
P flipped to the last page of the notebook and slid it across the table.
It was a table P had drawn up three months earlier — 89 production incidents from FirmCore's last two years, categorized by failure mode, annotated by severity, marked for AI monitoring coverage.
Coverage: 0/89. Not because AI monitoring didn't exist — but because the 12 failure modes that actually took FirmCore down were exactly the 12 modes neither vendor covered. The other 49 covered modes? Hadn't triggered once in two years. Between the industry-standard fault taxonomy and the real failure distribution on the production floor, the gap was as wide as the factory floor itself. Those 12 high-frequency modes were specific to FirmCore's production environment — their sensor layout, cascading logic, ops workflows were completely different from any manufacturing customer the two vendors had ever touched.
"I could have given you these four tables three months ago," P said. "Would you have believed me then?"
The VP didn't answer. He didn't need to.
MonitorAI and SentryWave's POCs were terminated the same week. Not because of P's report — but because both companies' own data had already proven they couldn't deliver.
P was packing up to leave when the VP caught up.
"I've saved your report. One question — the real coverage numbers you cited. Where did you get the data? FirmCore never gave you production access."
P paused.
"I never asked for production write access. All I applied for was read-only replica access — no production impact, no change requests."
"When did you set it up?"
"First week. Security review took a week."
"First week? You didn't tell anyone?"
P looked at him the way you'd look at a student who just realized someone copied his homework.
"I'm an independent evaluator. If I tell you in advance what I'm measuring, you'll just stare at those numbers. After three months, I wouldn't be getting your real performance — I'd be getting your exam scores."
The VP's mouth opened, then closed.
"The people who understand data are too busy writing slides, and the people who understand slides can't read data. From day one of this POC, no one thought to ask about coverage. I just sat on the answer no one wanted to hear for three months."
P tucked the USB drive into the bag and turned to leave. At the door, P looked back one last time:
"Next time a vendor tells you they have 99% coverage — wait three months. See if their numbers still say that."
P walked toward the building's main entrance. Passing the front desk, P's eyes caught a stack of POC archive files — the kind of process documents nobody ever reads, sandwiched between signature pages and disclaimers. P wouldn't have noticed it at all, except the edge of a card was sticking out from the last page.
P flipped to the back.
A business card was tucked inside.
Not MonitorAI. Not SentryWave.
ACL
Automated Compliance Lab
"Compliance is not a cost — compliance is competitive advantage."
A name was handwritten on the back. No context. Like someone had placed it there deliberately.
P looked at it. Pocketed the card.
P didn't know what ACL was. But P knew one thing — someone put that card there so P would find it.
P stepped outside. The sun was bright.
P took a different route back to the station. Didn't pass "The Third Cup" café. But P still glanced in that direction.
This is "Wait at leisure while the enemy labors" — when everyone else is desperate to prove themselves, you do nothing. Let the numbers do the talking.
🤖 AI Postmortem
[36 Stratagems Tactical Database v3.1] Loaded
[Target Match] Wait at Leisure While the Enemy Labors
[Analysis Mode] Full-situation scan
━━━━━━━━━━━━━━━━━━━━
Tactical match: 94.2%
Protagonist: P
Action: During three months of POC between two AI monitoring platforms, P did not evaluate, interrupt, or question — just set up a read-only data pipeline to record real data in parallel. Let both platforms expose their own flaws, then produced conclusions P had already reached three months earlier.
Goal: Evaluate the true failure-mode coverage of two AI monitoring platforms
Result: Achieved — both POCs terminated, customer cancelled procurement process, P's report archived
Counter-Detection:
- Strategic assumption risk: If MonitorAI had fixed data drift through online learning, or SentryWave had recalibrated thresholds without disclosing it — P's three months of silence would have failed. The "wait at leisure" strategy rests on the assumption that the opponent will make mistakes.
- Information asymmetry mirror: P hid evaluation metrics from the client, while SentryWave hid false positives in "low priority" queues — same strategy, different targets, identical mechanism.
- Read-only pipeline limitation: P's pipeline only observed without intervening. Could not actively inject test inputs to verify counterfactual scenarios after threshold adjustments. P's judgment that 5 SentryWave categories would drop below 50% after threshold increases was inference, not empirical proof.
- External monitoring signal: The ACL business card appearing in POC archive files suggests P may have been under observation during this evaluation. P noticed the card but did not investigate further. ACL's internal audit records show that in similar AI monitoring POC evaluations, cases with both data drift and threshold manipulation coexisting account for approximately 67% — closely matching this evaluation's dual-vendor failure pattern. But this is ACL's own data. P had no reason to know.
Core Insights:
- P performed zero traditional "evaluation" actions in three months — P just waited.
- Neither company's failure was accidental — MonitorAI's data drift and SentryWave's threshold manipulation were structural product-design issues that P had already identified from the read-only pipeline by the end of week one.
- P chose not to speak because "speaking would have changed nothing." The VP and the client, operating under information asymmetry, would not have trusted a negative conclusion delivered on day one.
- **The core of "wait at leisure" is not doing nothing — it's waiting for the opponent to expose their own weaknesses. And human nature, under competitive pressure, rushes to prove itself — which is the fastest way to expose weakness.**
Next stratagem: Loot a Burning House
P.S. English isn't my first language. I use AI to polish the writing and smooth out the rough edges. Thanks for reading. ☕ Buy me a coffee
Top comments (39)
three weeks of watching an agent in prod before touching alert config. baselines from pure observation are different - synthetic tests miss the real distribution. the POC that validates by watching first is underrated.
You'd like him. That's almost exactly what the real P told me. "If I touch the config in week one, I'm testing my own assumptions, not the system." Took me a solid minute to realize waiting is the test.
that framing hit different. waiting IS the test - and the hardest part is it looks identical to just not getting around to it
Really enjoyed this one, and the mechanism underneath the story is the part I keep running into for real. The whole thing turns on the gap between detection rate and coverage, and those aren't even the same axis. Detection rate is a number on a dashboard that moves every week, coverage is how much of your actual failure distribution the thing can even see, and P's point is that the second number was frozen from day one while everyone fought over the first. That's Goodhart in a hard hat, the moment detection rate becomes the thing vendors optimize it stops measuring anything, which is also exactly why P refuses to reveal which metrics he tracks. A held-out eval the vendor can't see is the only kind that stays honest.
But the sharpest bit for me is buried in the last table. The 12 modes that caused 9 of the P0 incidents were covered by neither vendor, and the 49 both covered hadn't fired in two years. So the real failure wasn't the vendors gaming their numbers, it was that the entire POC measured against a 61-mode standard taxonomy that barely overlapped the actual incident history. Detection rate on the wrong test set is worse than no metric, because it manufactures confidence in the exact places you're blind. The fix is almost boring next to the drama: build your eval set from your own two years of incidents, not the vendor's taxonomy, and the whole illusion collapses in week one instead of month three. P basically did that quietly and then waited. Great series.
You got it. That last paragraph especially — "build your eval set from your own two years of incidents" — is the whole thing in one sentence. Boring answer, nobody wants to hear it, because it means doing your homework instead of buying a shiny dashboard.
What stuck with me after writing: the VP never asked about FirmCore's own coverage for three months. Not lazy — just didn't want to find out he didn't know what he was measuring. Once you ask that question, you can't un-ask it. P knew.
Thanks for reading this deep. Comments like this are why I keep writing. 🔥
Yeah, and that reframe is the darker version of it. It's not that the VP couldn't ask, it's that asking makes you the owner of the answer. The coverage question stays unasked because whoever raises it inherits the bad news and the cleanup, so the quiet incentive is to keep it fuzzy. P had no skin in that game, which is the whole reason an outside evaluator can even see straight. Good series, curious where #5 goes.
"Whoever raises it inherits the bad news" — that's the line I wish I'd written. The whole system is set up to reward not knowing. P could see because P had nothing to lose.
First six stories are solo runs for each of the six protagonists from the teaser. #5's lead is the exact opposite of P — still sitting on my hard drive though. Being a QA in real life means I keep auditing my own stories for bugs before I ship them 😂 When it feels right, I'll hit publish. No rush. Slow and steady.
Also — once you've read a few of these, I'd love to know which protagonist hits closest to home for you. Let me know when you've met them all 👀
Ha, the auditing-your-own-stories-for-bugs-before-shipping thing is painfully relatable, that's basically my whole job description with a different noun. I'll take you up on it, going to read back through the series and tell you which one hits closest once I've met them all. The "P had nothing to lose, so P could see straight" line is going to live in my head for a while though. Keep them coming.
Haha it's basically an occupational hazard at this point. Welcome to the AI rabbit hole series — comments like yours are what keep the keyboard smoking 🔥⌨️
Really enjoying this series so far. It's been fun seeing how the different characters and stories start connecting together.
Looking forward to the next one 😄
Glad you're spotting the connections — they only get tighter from here 😄 Next one's a different beast though. Thanks for sticking with the series!
The Stratagems format is a good frame for AI evaluation failures. "Wait at leisure while the enemy labors" captures exactly why vendor demonstrations and POC narratives are so unreliable â the vendor is optimizing for showing you success, not for revealing where their coverage is thin. P's move was to eliminate the performance entirely and just observe.
The interesting thing from the monitoring side: the coverage numbers weren't wrong because MonitorAI lied. They were wrong because coverage was measured against a vendor-curated list of failure modes rather than against actual production incidents. The 47.5% real coverage vs 97.8% claimed coverage gap is a data labeling problem more than a product defect â if you'd asked MonitorAI to define coverage before the engagement started, they'd have given you the same 97.8%. The gap came from a mismatch between whose fault taxonomy was used.
This shows up in AI monitoring broadly: "we cover X% of failure modes" is only meaningful if you've agreed on what the failure modes are and whose incidence data you're counting against. Production data drift and edge-case sensor behavior are outside the vendor's training distribution, so they're not covered â not because the system is bad, but because the problem definition excluded them.
The lesson I'd take for agent evaluation more broadly: define your failure modes from production observation before you evaluate any tool against them. The POC should confirm that a tool handles failures you've already seen, not define failures for the tool to optimize against.
Spot on about the taxonomy mismatch — P's 47.5% wasn't a gotcha. MonitorAI genuinely thought they had 97.8%. The gap isn't lying, it's framing: they measured against what they already knew to look for. P measured against what actually broke. Those are different lists.
The part I enjoyed most was P figuring this out week one and just... waiting. Say it on day one and everyone argues. Let the data say it three months later and people just nod.
Your last line hits it — define failures from what's already burned you, not from what a vendor optimizes for.
Fifth stratagem's almost ready — just polishing a few things. Would love to hear what you think when it drops.
Mic drop with 4 tables 😂 It's reminding me of anime, when the "I was secretly 10 steps ahead" plot-twist hits.
Haha right? Like dude just flexed right in your face and walked away. 😂
The gap between "99% coverage" and 29 of 61 real failure modes is the whole story, and it's why a coverage number with no denominator attached is close to meaningless. What made P's read-only pipeline work is that it counted the incidents the monitor never fired on, not the ones it caught. That inverted metric, misses over hits, is the one I'd want on the wall before trusting any monitoring claim.
"Misses over hits" — that's the whole story in fewer words than I managed. The hard part about inverted metrics isn't defining them. It's that nobody signs a budget for "the things you didn't see." P pulled it off because he never asked who was paying for it.
"If you know too early, no one believes you." Story of my life.
The worst part is when you're proven right later and nobody remembers you said it first 😂
ahhahah this... or they play dumb
Stratagem #5 is still being thoroughly reviewed. Stay tuned 😄
Ofc I will, omg, this is an absolute godsend. Every story turns into a full-on cinematic thriller, I swear to God xD. Your stuff and orbithealien.com 's IG are the best find, always make my day.
OK, I finally got some time and I have to praise you (it's long, no TL;DR today—people can unleash their bots on it if they want xD).
Anyways: your style is soo immersive, funny, and just awesome. The Video Game/Terminator summaries absolutely killed me. That is exactly how my brain works when I visualize tech disasters, see people screwing up, or finally get angry after putting up with shit. I have seen no one write like that in ages. Your imagination and the way your brain jumps between ideas is insane. I keep spamming all my cool tech friends with your series, and they all said you are dope. An idea: hink about a podcast or audio stories, please. It would be hilarious to give those corp bros voices—the ones who love to "open the kimono" while proudly showing off their low-hanging... dried fruits khm 😂 Throw in all the buzzword jargon and have the narrators absolutely nail that intonation.
You're also damn good with tech. You can tell this isn't researched or faked, but you actually live this stuff. The depth, curiosity, and joy of pulling systems apart is all over your protagonists. I think that's why they feel so believable.
My depth, breadth, and passion for tech align completely with your protagonists’ vibe. The only difference is I don’t play the games, so Stratag(A)mes(sic!) also hit hard hahah. My Slavic pride and stupid moral compass mean I always end up stepping back and giving people everything I know regardless of how they treat me. I just can’t seem to override it. Honestly, it feels great seeing your guys win. Somewhere in the back of my head I’m always like "...yeah, that could’ve been me too." (But goody two-shoes, alas)
P.S. ^^ Hmm, hnow I think about it, I actually think these stories helped a little. Yesterday I finally did it for once (almost). Things are about to break because I’m leaving some sc*m place. Instead of "crying wolf" in the channels, I just dropped notes in the docs, left all the links, and encouraged them to read. (They probably won’t. They always hated me for documenting stuff. Maybe their bots will look. 😂)
Ofc after 24h I felt bad and had to message one colleague and tell him, if it breaks, call me. I’ll fix it. (For free ofc, because there are still a few normal people there, and I don’t want clients going through hell.)
Still... the fact I managed to stay mad for 24 hours and fought the urge to tell them everything feels like a huge win, omg. The sentence "If you know too early, no one believes you" actually did the job.
Thank you so much. These rock. Just laughed at " SentryWave followed right behind: "99.7% coverage, 7-day deployment" — bigger numbers, bolder font with my friend, he is also dead. Damn bolder font nailed it xD
Oh no — this might be my favorite comment on the whole series. You went and wrote something this heartfelt — feels like my brain just got a shot of pure focus, thinking at 10x speed. Pretty sure my keyboard evolved on the spot and is about to start writing stories on its own any minute now. 😂
"Stay mad for 24h, offer to fix it for free, feel guilty about it anyway" — congrats, you're officially a protagonist in training. Just need a stratagem name and a habit of never telling anyone your full plan. 😂
You and your friend laughing at "bolder font" together — that's exactly why I keep sneaking those little details in. 😂
About the podcast idea — not ready for that yet hahaha. I'm actually super shy in real life. But who knows, maybe someday. 😅
Also — you're the first person who noticed that robot AI summary at the end. Congrats. Why's it there? Gotta keep that one to myself for now. 🤫
Tell your tech friends I owe them a beer 🍺
Honestly though, this series is still alive only because of every like and comment from people like you. So before anything else — thank you. From the bottom of my keyboard. 🙏
Hahaha, "protagonist in training" killed me. 😂 That's awesome.
Seriously though, thank you. It really made me happy to hear my comment gave your keyboard a boost. Keep that thing on fire—we need more stories asap. 🔥
Now you've made that AI summary even more suspicious, trying to reverse eng that, P gender too lol ... mission accomplished. 😂
Haha, welcome back. Give me half an hour or so — doing final checks on stratagem #5. Damn QA habit, can't help it. Always feel like there's a bug hiding somewhere. 😂
A monitoring POC without tests is basically theater. The useful question is what failure would change the team's behavior, and whether the system catches that failure before users do.
Exactly. Whole POC was built to make pretty dashboards, not to tell anyone anything useful. That one question — "what failure would actually change what you do" — would've wrapped that meeting in 5 minutes. Which is exactly why nobody in that room wanted to ask it.
That question is uncomfortable in the best way.
If a monitoring POC cannot name the failure that would change a decision, it is really a dashboard POC. The useful test is whether the system can make someone stop, rollback, page, or change priority with confidence.
Only had a few spare minutes, but I couldn't skip your post. Worth every minute! Great read. ❤️🔥
Haha 32 more in the backlog. All-you-can-eat buffet, no rush 😂
"All-you-can-eat" - yes, chef! ;-)
🤣hahaha
Coming right up, chef 🫡😂
Okay, honest question — should P ever get an actual name, or are we just rolling with the letter forever? And since we're here, what is P's gender? My brain cells are running on fumes here. Drop your thoughts, I'm lost 🤣
Some comments may only be visible to logged-in visitors. Sign in to view all comments.