;)
;)
;)
;)
🚀 THE WALL IS DOWN. NOW WHO'S GOING TO WALK THROUGH THE DOOR?
Posted by Puseletso Mafisa 
on
16 September 2026, 07:00
SAST
🚨 THE RICHJERK™ REPORT — CONTINUED
“THE CRAWLER FOUND 22 NEW ITEMS. NOW WE FIND OUT WHO THEY ARE, WHY THEY'RE THERE, AND WHETHER THEY HAVE PERMISSION.”
A Kasi Connect Infrastructure + Privacy Infomercial by The Unemployed CEO™
📘 Facebook • 📸 Instagram • 💼 LinkedIn • 🎥 TikTok • 💬 WhatsApp
🌍 Kasi Connect Business Listing Directory
[LIST OR DISCOVER A BUSINESS — Kasi Connect](Register Your Business Here 👈🏾)
---
🏢 BACK AT THE RICHJERK™ MANSION...
The Unemployed CEO™ walked into the room holding another report.
Khethiwe was already reading it.
RichJerk™ looked over.
> “What broke?”
The CEO shook his head.
> “Nothing.”
RichJerk™ paused.
> “Then why are you holding that face?”
The CEO placed the report on the table.
> “The crawler found 22 new items.”
Silence.
Khethiwe adjusted her glasses.
> “Now THAT deserves an investigation.”
---
🕵️♀️ THE CRAWLER HAS SPOKEN
The consent-management crawler reported newly detected technology connected with the website.
Among the findings:
🔤 Google Fonts
📊 Microsoft Clarity
🌐 New domains including:
fonts.googleapis.com
fonts.gstatic.com
*.clarity.ms
www.google.it
www.clarity.ms
And then came the cookies.
🍪 _ga
🍪 _ga_*
🍪 _gcl_au
🍪 session-id
🍪 kasi-cart
…and several others.
The CEO stared at the list.
> “That's a lot of cookies.”
RichJerk™ smiled.
> “No.”
> “That's a lot of questions.”
---
💥 KHETHIWE'S FIRST RULE
Khethiwe wrote on the whiteboard:
> DETECTED ≠ DANGEROUS.
The CEO looked at her.
> “So we're not panicking?”
> “No.”
> “We're investigating.”
She continued:
> “A crawler finding a vendor or cookie doesn't automatically mean something is wrong.”
RichJerk™ nodded.
> “Exactly.”
> “You don't call the fire brigade because the smoke detector says ‘check the kitchen.’”
---
🔎 GOOGLE FONTS ENTERS THE ROOM
The report identified:
🔤 Google Fonts
With domains:
fonts.googleapis.com
fonts.gstatic.com
The CEO pointed at the screen.
> “Google.”
Khethiwe nodded.
> “A third-party resource.”
RichJerk™ leaned back.
> “And the question isn't whether the name sounds familiar.”
> “The question is whether we've properly documented what it does.”
---
📊 THEN MICROSOFT CLARITY WALKED IN
Next:
📊 Microsoft Clarity
With domains including:
*.clarity.ms
scripts.clarity.ms
z.clarity.ms
The CEO smiled.
> “Analytics.”
Khethiwe raised her finger.
> “Potentially.”
RichJerk™ immediately interrupted.
> “Potentially is not verified.”
Khethiwe nodded.
> “Exactly.”
> “We need to know what is being collected, under which consent category, and whether the CMP can prevent the code from running before consent where required.”
---
🍪 THE COOKIE TABLE
Khethiwe pulled up the crawler report.
Newly detected cookies include:
🍪 _gcl_au
🍪 _ga
🍪 _ga_*
🍪 session-id
🍪 _gcl_ls
🍪 kasi-cart
🍪 __dpl
🍪 Several lswt-* cookies
The CEO looked at RichJerk™.
> “So what do we do?”
RichJerk™ pointed at Khethiwe.
> “We classify.”
---
🧠 KHETHIWE'S COOKIE PROTOCOL
She wrote:
COOKIE → PURPOSE → CONSENT → CONTROL → VERIFY
For every detected cookie:
🔎 What creates it?
🎯 What purpose does it serve?
📊 Is it analytics?
📣 Is it marketing?
⚙️ Is it functional?
❓ Is its purpose currently unknown?
🔐 Does consent need to be obtained before it runs?
🛑 Can the CMP block it when consent isn't given?
And most importantly:
> “Don't guess from the cookie name.”
---
🚨 THE CMP WARNING
The consent manager's own recommendation is clear:
All cookies should have an assigned type.
All vendors should have an assigned purpose.
Third-party code should be prepared so the consent-management system can block it when necessary.
The CEO looked at the report.
> “So the crawler isn't necessarily saying we're breached.”
Khethiwe:
> “Correct.”
> “It's telling us the website's technology footprint has changed.”
RichJerk™ smiled.
> “And infrastructure hates undocumented changes.”
---
🏗️ OOPS!!
INFRASTRUCTURE... AGAIN.
First it was:
🏪 Business listings.
Then:
🔎 Discovery.
Then:
🛡️ Security.
Then:
📊 Analytics.
Then:
🤖 AI Agents.
Now:
🍪 Consent infrastructure.
The CEO sighed.
> “We're building a directory.”
RichJerk™ looked at him.
> “No.”
> “We're discovering what a real digital platform actually requires.”
---
📱 AND WHY THIS MATTERS FOR KASI CONNECT
Kasi Connect is designed around people using the platform to:
🔎 Find businesses.
📍 Find businesses in their area.
🏪 Discover local services.
💬 Contact businesses.
📝 List businesses.
📅 Check bookings.
🛒 Eventually participate in local commerce.
That means the platform doesn't only need a good-looking interface.
It needs:
DATA + DISCOVERY + SECURITY + CONSENT + TRUST.
---
🇿🇦 THE KASI TEST
Khethiwe looked at the dashboard.
> “Our users don't need to understand every technical component.”
The CEO nodded.
> “They just need the platform to behave responsibly.”
RichJerk™ pointed at the cookie report.
> “Exactly.”
> “Complexity belongs behind the curtain.”
> “Trust belongs in front of it.”
---
🤖 AND THEN THE AI AGENTS RETURNED
The CEO suddenly remembered the paused AI Marketplace.
> “When the credits return, maybe the Agents can analyse this automatically.”
Khethiwe looked interested.
RichJerk™ raised an eyebrow.
> “Eventually.”
The CEO asked:
> “A Privacy Agent?”
Khethiwe started writing.
🤖 Privacy/Consent Agent
Potential responsibilities:
🔎 Detect newly introduced vendors.
🍪 Inventory cookies.
🏷️ Check classification.
📋 Compare vendors against the approved list.
🚨 Flag unexplained changes.
🧪 Generate verification tasks.
📊 Maintain an audit trail.
RichJerk™ smiled.
> “Now you're giving an Agent a job instead of giving an Agent a costume.”
---
🔌 MCP + CONSENT = ANOTHER INVESTIGATION
The Kasi Connect architecture is moving toward multiple specialised Agents working with shared infrastructure.
That creates another principle:
> An Agent must not automatically receive permission just because it can access a tool.
Khethiwe wrote:
AI + DATA + PERMISSIONS + CONSENT + VERIFICATION
Then underneath:
> “Access is not authorization.”
RichJerk™ nodded.
> “And detection is not permission.”
---
💥 THE RICHJERK™ PUNCHLINE
The CEO looked at the 22 new crawler findings.
> “Should we remove everything?”
RichJerk™ almost fell out of his chair.
> “WHY?”
The CEO shrugged.
> “Because the crawler found them.”
Khethiwe shook her head.
> “No.”
> “First determine what they are.”
RichJerk™ stood up.
> “Don't delete technology because you don't understand it.”
He pointed at the report.
> “Understand it first.”
---
🕵️♀️ THE NEXT INVESTIGATION
The instruction is therefore simple:
READ → CLASSIFY → CONFIGURE → TEST
Not:
❌ Delete Google Fonts.
❌ Delete Clarity.
❌ Delete random cookies.
❌ Break analytics.
❌ Break the shopping cart.
❌ Break authentication.
Instead:
✅ Identify each vendor.
✅ Identify each cookie.
✅ Determine its actual purpose.
✅ Assign the correct consent category.
✅ Ensure third-party scripts can be blocked where required.
✅ Test the website with no consent.
✅ Test again after consent.
✅ Verify that legitimate functionality still works.
---
📊 THE RICHJERK™ INFRASTRUCTURE BOARD
The CEO wrote everything down.
DISCOVERY
🏪 Businesses can be found.
SECURITY
🛡️ Ownership and storage permissions have been hardened.
ANALYTICS
📊 Visitor behaviour is being measured.
MCP
🔌 Business data can be exposed through controlled tools.
AI AGENTS
🤖 Marketplace architecture is being planned.
CONSENT
🍪 Third-party vendors and cookies now require classification and verification.
RichJerk™ looked at the board.
> “That's not feature creep.”
Khethiwe asked:
> “What is it?”
He smiled.
> “That's infrastructure revealing itself.”
---
🌍 KASI CONNECT BUSINESS LISTING DIRECTORY
The mission remains simple for the person using the platform:
🔎 FIND
📍 LOCATE
🏪 DISCOVER
💬 CONNECT
🛡️ TRUST
📊 MEASURE
🤖 AUTOMATE
But behind those buttons is an increasingly important responsibility:
> Build the digital road without losing control of who travels on it, what data is collected, and what systems are allowed to operate alongside it.
[LIST OR DISCOVER A BUSINESS — Kasi Connect Business Listing Directory](Register Your Business Here 👈🏾)
---
📲 FOLLOW THE JOURNEY
🎥 TikTok
👔 The RichJerk™ — Mentor & Strategist
👑 The Unemployed CEO™ — Founder & Builder
🕵️♀️ Khethiwe — Investigator & Verifier
---
🚨 FINAL CONVERSATION
The CEO closed the crawler report.
> “So what's the verdict?”
Khethiwe answered:
> “No verdict yet.”
The CEO looked confused.
RichJerk™ smiled.
> “That's the point.”
Khethiwe picked up her magnifying glass.
> “The crawler found 22 new items.”
RichJerk™ opened the door.
> “Now we find out what they mean.”
The CEO followed.
> “And if something isn't properly configured?”
Khethiwe:
> “Fix the smallest thing necessary.”
RichJerk™ nodded.
> “Without breaking the road.”
The three walked out.
Behind them, the crawler continued watching.
---
🏗️ OOPS!!
THE WEBSITE GOT A COOKIE.
THE COOKIE GOT A VENDOR.
THE VENDOR GOT A DOMAIN.
THE DOMAIN GOT A QUESTION.
And the question became:
> “Do we know what is happening on our own road?”
Evidence first.
Classification second.
Consent third.
Change last.
Empire later.
— The Unemployed CEO™
