EXPANSION · source-linked operating design
The 26-discipline operating library
Version 2026.09.09-d26 · Prepared for Joseph · 9 September 2026.
This expansion treats website reliability, networking, engineering, accessibility, SEO, AI-search visibility, content, measurement and release assurance as distinct responsibilities within one coherent delivery process. The numbering preserves the user's exact 26 roles. These are accountabilities and review lenses, not an assertion that 26 separate employees or professional credentials exist.
Google describes AEO/GEO work for its own generative Search as part of core SEO, not a completely isolated replacement discipline. Other providers have their own crawler and reporting controls. This operating model separates specialist work where that prevents mistakes while preserving shared foundations. Google's AI optimization guidance.
Start here
- Read the operating model and routing protocol.
- Fill the site facts template with verified facts; unknowns remain null.
- Select one lead and the necessary consulted roles. Read their charters and the linked current framework modules.
- Diagnose read-only, record evidence and route ownership conflicts to R24. Use the handoff contract.
- Apply the acceptance and independence rules before any production or publication claim.
- Build public expertise from the publishing model, not from internal role titles.
The integration guide explains how to put these instructions in the actual project used by Codex. Downloading this package alone changes no external repository, site or account.
Exact role directory
Boundary and compatibility
Existing commercial SEO tiers, pricing and names are unchanged. Tier 13 remains retired; R13 is an editorial role, not a tier. All 146 unique historical originals remain intact. Baseline legacy documents remain labeled as not fully fact-checked. New source-linked procedures do not certify every inherited sentence or code example.
See the expansion report, source register and tools guide for exact changes, provenance and validation boundaries.