When you build a methodology for digital architecture, the hardest test isn't applying it to a client — it's applying it to yourself.
Siosi Samuels, creator of Conscious Stack Design™, recently ran a full CSD audit on his own personal brand website (georgesiosi.com). The results were illuminating: inconsistent anchor expressions, clever-over-clear navigation, missing audience segmentation, buried social proof, and an AI-invisible infrastructure layer.
What the Audit Found
Using the 5:3:1 Protocol as the diagnostic framework, the audit mapped the website's 9 Functional Slots — from the Anchor Function (converting visitors into Stack Reading clients) down to the Supporting Infrastructure (AI signaling, newsletter nurture, social links).
Key findings:
- Three different CTAs were competing for the same cognitive slot — "Book a Reading," "Book a consultation," and "Book a Stack Reading" all appeared on the same page
- Navigation used "Transmissions" instead of "Blog" — clever, but creating unnecessary friction in the Control Plane
- No audience segmentation — a venture fund CTO and a solopreneur landed on the same undifferentiated page
- Social proof buried in running paragraph text instead of occupying a dedicated functional slot
- AI identity limited to a 40-line
llms.txtwith no service taxonomy
The Fix: Architecture, Not Decoration
The redesign wasn't cosmetic — it was architectural:
- Single Anchor Expression: "Book a Stack Reading" — everywhere, consistently
- Clear > Clever: "Transmissions" → "Blog" in navigation
- Audience Segmentation: Three explicit cards mapping visitors to service tiers
- Social Proof Slot: A dedicated "Featured In" section with architectural positioning
- AI Readiness: Expanded
llms.txt(110 lines), newllms-full.txt(200+ lines), enhanced JSON-LD schema
Read the Full Case Study
The complete case study — including the 5:3:1 website audit framework, section-by-section redesign breakdown, the SEO → AEO shift, and a self-audit checklist — lives on Siosi's personal site:
→ I Applied CSD to My Own Website. Here's What It Found.
Your stack is your first client. If the methodology can't govern its own creator's digital ecosystem, it can't govern yours. Take the Stack Type Quiz to see where your own stack stands.
