I Applied CSD to My Own Website. Here's What It Found.

When you preach a methodology, the first stress test is always the same: can you apply it to yourself?

This is the story of how I applied Conscious Stack Design™ to my own website — georgesiosi.com — and what it revealed about the gap between what I was saying and what I was structuring.

The site was functional. It looked good. But like most personal sites — and most digital ecosystems — it had evolved organically. Good decisions, made at different times, for different reasons, that had never been unified under a single architectural intent. That's not failure. That's the starting condition for almost everyone.

The Starting Condition: Evolved, Not Architected

Before running CSD, the site had the patterns I see in almost every personal brand website — and most enterprise stacks too:

1. No Clear Anchor Function

The homepage had a hero section, pain points, modalities, a personal story, blog posts, and a call-to-action. All good content. But the CTA language was inconsistent — "Book a Reading" in the nav, "Book a consultation" on the hero, and different phrasing on the final section.

In CSD terms: the Anchor Function (the site's primary job-to-be-done — converting visitors into Stack Reading clients) had no single anchor expression. Three different phrasings were competing for the same cognitive slot.

2. Clever Over Clear

The blog section was called "Transmissions." On brand? Sure. Immediately understandable to a first-time visitor? No. When someone lands on your navigation and sees "About," "Transmissions," "Tools" — which one is the blog? They have to guess.

Joey Yap — one of the world's most successful metaphysical practitioners — calls his blog "Blog." It's in the footer, clearly categorized, and immediately parseable. When your topic is already esoteric, your navigation must be crystalline.

CSD principle: clarity > cleverness in the Control Plane. The navigation bar is the Control Plane of a website. It must reduce switching cost, not increase it.

3. No Audience Segmentation

The site presented two modalities (Digital Wayfinding and Dream Wayfinding) but never answered the question: "Is this for me?"

A venture fund CTO and a solopreneur building with AI agents both land on the same page. One needs enterprise advisory; the other needs the 5:3:1 Protocol. Without explicit segmentation, neither self-selects efficiently — and neither does an AI agent trying to match the site to a query.

4. Missing Social Proof Layer

The credentials existed in the story section, buried in running text. Forbes, Wired, VentureBeat, nChain — all legitimate signals of credibility. But they weren't architecturally positioned. In CSD terms, they were data without a functional slot.

5. AI-Invisible

The site had a basic llms.txt file (~40 lines), a Person schema in JSON-LD, and a sitemap. Functional, but not designed for the emerging reality: AI agents will increasingly mediate discovery.

When a ChatGPT user asks "Who can help me with a stack audit for my organization?", the AI needs to parse the site's structured data, read its llms.txt, and match the query to a service. A 40-line summary with no service taxonomy is like having a business card with no phone number.

The Diagnosis: Running a Stack Audit on Myself

I treated the website the same way I'd treat any client's digital ecosystem:

Map the functional slots: What are the 9 jobs this website needs to do?
Identify the Anchor: What is the single most important conversion action?
Check for cognitive civil war: Are any pages or sections competing for the same function?
Test AI readability: Can a language model accurately describe what I do and who I serve, based solely on the site's machine-readable layer?

The 9 Functional Slots of a Personal Brand Website

Using the 5:3:1 Protocol, here's how I mapped the site:

1 Anchor Function:

Convert → Get qualified visitors to book a Stack Reading

3 Active Functions:

Establish Authority → Credentials, social proof, story
Educate → Blog posts, frameworks, concepts
Segment → Help visitors self-select into the right service tier

5 Supporting Functions:

Navigate → Clear site navigation and wayfinding
Search → Internal search for returning visitors
Signal AI → Structured data, llms.txt, schema markup
Nurture → Newsletter subscription in footer
Connect → Social links, contact page, calendar links

The original site had the Anchor Function and most Active Functions — the raw material was there. But they were unanchored — distributed across the page without clear hierarchy. And three of the five Supporting Functions (AI signaling, segmentation, social proof) were either undeveloped or buried. This is the most common pattern I see: the pieces exist, the architecture doesn't.

The Redesign: Applying CSD Section by Section

Hero → Single, Consistent CTA

Before: "Book a Reading" (nav), "Book a consultation" (hero) After: "Book a Stack Reading" — everywhere

The term "Stack Reading" is specific, ownable, and creates curiosity. It's also the Anchor Function expressed with a single, unambiguous token. When an AI agent parses the site, "Stack Reading" appears as a consistent entity across nav, hero, and footer — reinforcing the signal.

Navigation → Clear > Clever

One word changed. "Transmissions" → "Blog." The internal metaphor is preserved on the blog page itself ("Transmissions from the field"), but the navigation uses the universal label. Clear > clever in the Control Plane.

New Section: "Who This Is For" (Audience Segmentation)

Added three audience cards directly after the Systems section:

Card	Audience	Services
🧭 The Conscious Technologist	Individuals	Stack Readings, Siomancy, Dream Wayfinding
🏛️ The Sovereign Enterprise	Organisations	Advisory, Stack Audits, Pattern Retainers
⚡ The Solo Vaka Captain	Founders & Solopreneurs	CSD™, 5:3:1 Protocol

This serves two purposes:

Human self-selection: Visitors immediately know which path is theirs
AI matching: An agent can now match "I need a stack audit for my company" → The Sovereign Enterprise → Advisory page

New Section: "Featured In & Trusted By"

Pulled the social proof out of running text and gave it a dedicated architectural slot:

Forbes · Wired · VentureBeat · CoinDesk · nChain

This is the credibility checkpoint — positioned after the story (origin + credentials) and before the blog (thought leadership). The visitor has now seen: what you do → who you help → why you're credible → what you think. That's a conversion funnel designed as a narrative arc.

Blog Preview → Constrained to 3

Before: 5 blog posts on the homepage After: 3 blog posts + "View All Posts" link

Why? The homepage's job isn't to be a blog index. Showing 5 posts dilutes the Anchor Function. Three is enough to signal "this person thinks deeply" without turning the homepage into a content feed. This follows the principle that every section on the homepage is a functional slot, and slots should be constrained.

The Invitation → Dual CTA

Before: Single CTA with inconsistent language After: Two CTAs: "Book a Stack Reading" (primary, high intent) + "Start a Conversation" (secondary, lower friction)

This respects the visitor's stage. Some are ready to book; others want to explore. Both paths lead to conversion, but with different friction levels.

The AI Layer: Designing for the Agent Era

This was the piece that moved the site from "good" to future-proof.

`llms.txt` → Comprehensive Identity Document

Expanded from ~40 lines to a full-spectrum identity document covering:

Core identity and positioning
Key concepts with definitions
Complete service taxonomy (Individuals / Organisations / Tools)
Audience segments with descriptions
Full sitemap with page descriptions
Every blog post with slug and category

When an AI agent reads georgesiosi.com/llms.txt, it can now accurately answer: "Who is Siosi Samuels?", "What services does he offer?", "Who should work with him?", and "What's his body of work?"

`llms-full.txt` → Deep Reference for AI Systems

Created a new 200+ line document structured for AI comprehension:

Pacific Metaphysics as a theory (core thesis, key principles)
All wayfinding modalities with sub-tools
The SiO Family (Siomancy, Siocracy, Siosism) — with etymologies
CLM framework — the Cultural Language Model distinction
Brand voice rules — so an AI can represent the voice accurately
Complete blog table — with dates, categories, and slugs

This is the document that enables an AI to cite accurately. Not "he does some kind of tech-metaphysics thing" but "Siosi Samuels is the creator of Conscious Stack Design™, a constraint-based architectural pattern for digital sovereignty, and the practitioner of Pacific Metaphysics — a unified theory connecting Polynesian navigation wisdom, SiO₂ crystalline science, and modern technology governance."

JSON-LD Structured Data → Expanded

The Person schema in layout.tsx was updated to include:

knowsAbout: Pacific Metaphysics, Digital Wayfinding, Dream Wayfinding, Conscious Stack Design, Siomancy, Siocracy, Siosism, Digital Feng Shui, AI Governance
sameAs: Twitter, LinkedIn, Substack
Comprehensive description field

Semantic Section IDs

Every section on the homepage now has a clear, machine-readable id:

<section id="signal">      <!-- Pain points -->
<section id="systems">      <!-- Wayfinding modalities -->
<section id="audience">     <!-- Who this is for -->
<section id="story">        <!-- Origin narrative -->
<section id="featured">     <!-- Social proof -->
<section id="transmissions"> <!-- Blog preview -->
<section id="invitation">   <!-- Final CTA -->

An AI agent (or a future browser that navigates by section) can now jump directly to the relevant part of the page.

The Meta-Lesson: Your Website Is Your Stack

Here's what applying CSD to my own site taught me that I couldn't have learned from auditing someone else's:

1. Evolved ≠ Designed

Every element on the original site was a good decision. The problem was that good decisions made over time don't automatically sum to good architecture. A hundred well-chosen bricks is still a pile until you impose structure. This isn't a personal failing — it's the natural state of any system that grew organically.

2. The Anchor Test

If you can't name your site's Anchor Function in one sentence, you don't have one. Mine was: "Convert qualified visitors into Stack Reading clients." Everything else on the homepage either supports that conversion or should be moved.

3. AI Readiness Is a Stack Decision

Most people think about SEO. Few think about AEO (AI Engine Optimization). The difference:

	SEO	AEO
Audience	Search engine crawlers	AI agents acting on behalf of humans
Format	Meta tags, keywords, backlinks	`llms.txt`, structured data, clean semantic HTML
Goal	Rank on a results page	Be accurately cited in a conversation
Unit of success	Click-through rate	Recommendation accuracy

Your website isn't just a brochure anymore. It's an API for AI agents. If an AI can't accurately describe what you do, you're invisible to the next generation of discovery.

4. The Website Is the First Stack Audit

If you're building a methodology around digital architecture, your own website is the most honest diagnostic you'll ever run. Every misalignment you find there is a version of the same misalignment your clients face — just at a different scale.

Before & After: The Architectural Diff

Dimension	Before	After
Primary CTA	Inconsistent ("Book a Reading" / "Book a consultation")	"Book a Stack Reading" — everywhere
Navigation label	"Transmissions" (clever)	"Blog" (clear)
Audience segmentation	None	3 explicit audience cards with service mapping
Social proof	Buried in paragraph text	Dedicated "Featured In" section
Blog preview	5 posts	3 posts + "View All Posts"
AI identity	40-line `llms.txt`	110-line `llms.txt` + 200-line `llms-full.txt`
Structured data	Basic `Person` schema	Expanded with `knowsAbout`, `sameAs`
Section IDs	Partial	Full semantic IDs on every section
Homepage sections	5	7 (added Audience + Featured In)

Try It Yourself: The CSD Website Audit Checklist

If you want to apply the same process to your own site, start with these questions:

Level 1: The Anchor

Can you name your site's single most important conversion action?
Does that action appear in the nav, hero, AND final section with identical language?
If an AI agent read your homepage, would it know what to recommend?

Level 2: The Active Layer

Does your homepage answer "Why should I trust this person?"
Does it answer "Is this for me?"
Does your navigation prioritize clarity over cleverness?

Level 3: The Supporting Infrastructure

Do you have an llms.txt at your domain root?
Does it include your service taxonomy, not just a bio?
Is your JSON-LD comprehensive (not just name and url)?
Do all homepage sections have semantic, machine-readable IDs?

Conclusion

Conscious Stack Design™ is a methodology for navigating digital complexity. But a methodology is only as credible as its application. By running a full CSD audit on my own website, I caught the exact patterns I see in every client engagement: organically evolved elements without architectural intent, inconsistent anchor expressions, undeveloped functional slots, and AI-invisible infrastructure. These aren't signs of neglect — they're the natural result of building iteratively without a governing framework.

The result isn't just a prettier homepage. It's a coherent system — designed for humans to navigate and AI agents to parse — where every section occupies a defined functional slot and the Anchor Function is expressed with singular clarity.

Your website is your first stack. Design it like one.

Want to see what a CSD audit reveals about your own digital ecosystem? Book a Stack Reading or run your own diagnostic with CSTACK.