Internal entity and topic relationship map for AI Execution Lab. Covers track-to-lesson relationships, cross-section bridges, authority pathways, recommendation logic, and GEO optimization strategy.
This document defines the internal knowledge graph for AI Execution Lab — the entity and topic relationships that drive recommendation logic, GEO citation probability, and the platform's authority architecture.
The knowledge graph is not a database schema. It is the conceptual map that governs: how content links to other content, which topics cluster into authority zones, how AI search engines should perceive topical depth, and what recommendation logic looks like as the platform scales.
The platform has 9 content entity types. Each has different relationship properties:
| Entity Type | Primary Role | Relationship Density | GEO Priority |
|---|---|---|---|
| Lesson | Primary learning unit | High — links to failures, playbooks, related lessons | Medium |
| Failure | Production incident record | High — links to causative tools, preventive lessons | Very High |
| Playbook | Operational procedure | High — links to lessons (context), failures (what happens without it) | High |
| Lab | Interactive execution environment | Medium — links to lessons (context), case studies (outcome) | Medium |
| Case Study | Specific problem + solution | High — links to failures, tools, systems, playbooks | High |
| Log | Dated work record | Medium — links to lessons and systems built during session | Low |
| System Doc | Reference architecture | Medium — links to lessons, playbooks, case studies | Medium |
| Doc | Reference + operational resource | Low-Medium — supporting documentation | Medium |
| Track | Structured learning pathway | High — aggregates lessons, defines progression | High |
The platform's content organizes into 8 authority clusters. Each cluster contains content from multiple sections — lessons, failures, playbooks, case studies — that collectively build topical authority.
Center entity: Claude Code Operator track
Authority target: Become the definitive operational reference for Claude Code in production
Core content:
Key entity relationships:
GEO target queries:
Center entity: WordPress REST API module (Claude Code Operator) + WP REST API Playbook
Authority target: Most detailed operational reference for WordPress + AI automation
Core content:
Key entity relationships:
GEO target queries:
Center entity: Vercel Deployment module (Claude Code Operator)
Authority target: Best operational reference for Next.js + Vercel production issues
Core content:
Key entity relationships:
GEO target queries:
Center entity: GEO + AI Search track
Authority target: Definitive operational reference for content visibility in AI search
Core content:
Key entity relationships:
GEO target queries:
Center entity: AI Business Zero Budget track
Authority target: Most actionable reference for launching AI businesses without funding
Core content:
Key entity relationships:
GEO target queries:
Center entity: AI Automation Systems track
Authority target: Production-grade reference for AI automation pipeline engineering
Core content:
Key entity relationships:
GEO target queries:
Center entity: AI Content + Distribution track
Authority target: Operational reference for AI-augmented content operations
Core content:
Key entity relationships:
GEO target queries:
Center entity: AI Research Operations track (planned)
Authority target: Reference for AI-assisted research workflows in academic + professional contexts
Core content:
Key entity relationships:
Authority pathways are sequences of content items that build expertise progressively. They differ from tracks in that they cross section boundaries.
Goal: Full Claude Code production capability
Length: ~40 content items
Sequence:
Authority signal: Completing this pathway demonstrates more operational knowledge than any formal AI engineering course.
Goal: Revenue-generating AI business from zero
Length: ~25 content items
Sequence:
Goal: Full WP automation capability using AI
Length: ~15 content items
Sequence:
Goal: Operational GEO implementation capability
Length: ~20 content items
Sequence:
The most valuable cross-section relationships — failure reports that teach what lessons warn about:
| Failure | Teaches | Connects To |
|---|---|---|
edge-runtime-deployment-failure | Crypto API unavailable in edge runtime | deployment-pipeline, build-failure-diagnosis, env-vars-secrets |
next-mdx-remote-v6-blockjs | MDX v6 breaking change — blockJS rendering | dev-environment, reading-build-errors, content-renderer system doc |
server-module-client-bundle | Server-only imports in client components | reading-build-errors, debugging-methodology, Next.js architecture |
| Playbook | Implements | Teaches context in |
|---|---|---|
| WP REST API Automation | Read→Transform→Check→Apply→Verify | content-patching-system, pipeline-design, wp-auth-patterns |
| Case Study | Demonstrates | Referenced by |
|---|---|---|
| LiteSpeed UCSS Typography Repair | Cache layer CSS stripping diagnosis | deployment-pipeline, debugging-methodology, WordPress system doc |
Every piece of content should explicitly name:
This entity density is what makes the Lab citable in AI-generated answers. AI search systems summarize content that contains specific, verifiable entities.
Content entities map to schema.org types:
Course or HowToTechArticle with about: [specific tool]HowTo with step arrayArticle with mentions: [tools]Course with hasCourseInstanceThe sameAs property on the Organization schema should reference all content that mentions A Square Solutions, creating entity coherence across the ecosystem.
AI search systems assess topical authority by:
The knowledge graph ensures that each new piece of content adds to an existing cluster rather than creating isolated articles. Isolated articles have no topical authority benefit. Cluster-building articles multiply the authority of everything already in the cluster.
When a user finishes a lesson, the recommendation system should return items from:
The lib/related-content.ts file implements this at lesson level. At scale, this needs to be:
The knowledge graph extends to all four A Square Solutions properties:
WordPress content links to Lab content when topic overlap exists. This creates inbound authority signals for the Lab from an established domain. Every WordPress post in AI/SEO/development categories should have one outbound link to the relevant Lab cluster.
Lab content references asquaresolution.com as the parent entity. Every track and the homepage explicitly identifies A Square Solutions as the builder. This establishes entity coherence for AI search.
Product pages link to Lab execution logs documenting their build. This creates bidirectional authority — Lab gains product credibility, products gain engineering transparency. For AI search, products with documented engineering decisions are more citable than black-box tools.
Contextual mentions in relevant lessons and case studies. "The Firebase + Gemini architecture described in TrustSeal's execution log" creates cross-property entity links.
lib/related-content.ts maintains manual lesson-to-content mappings. Updated when new content is published.
Limitation: Doesn't scale past ~200 lessons without significant maintenance overhead.
When content volume exceeds 200 lessons, augment manual mappings with automatic tag-based recommendations. Two content items sharing 3+ tags have a high probability of relevance.
Implementation: getRelatedByTags(lessonId, limit) function that queries all content metadata and returns items sorted by tag intersection count.
When content volume exceeds 500 items, add explicit cluster membership to frontmatter. Recommendation logic filters by cluster first, then by tags.
---
cluster: "claude-code-engineering"
related-clusters: ["wordpress-operations", "deployment-infrastructure"]
---
When user authentication exists, incorporate completion history. Weight items from incomplete pathways higher than items from completed sections.
Last updated: 2026-05-18. Update when major new content clusters are established or relationship patterns change.