Dual-Repository Architecture — Executive Cut

What it is
Separation of concerns: SkillSystem = Truth; docs site = Authority. Hydration + validation bridge them without duplication.

Why it matters

• Keeps specs clean (truth) while publishing AEO/SEO authority (docs).
• Prevents drift: UI always hydrated from truth, build fails on broken links.
• Clear CTAs for services without polluting the truth layer.

How to use

1. Specs live in SkillSystem; hydrate via scripts (hydrate_content_from_specs.js, hydrate_suites_and_flows.js).
2. Validators (verify:links, docs:build) block broken refs; sitemaps/SEO stay fresh.
3. Publish authority pages with schema, breadcrumbs, and CTAs.
4. CTA: Book an AAA audit.

Full PDF Download