The library · shelf 1 of 8
Operating model
How the 26 disciplines work as one accountable system: routing, handoffs, acceptance, integration, decision ownership.
Answers: Which documents are on the “Operating model” shelf of the SEO / AIO library?
- 01Instructions for AI-assisted use of this libraryUse the current project facts and explicit client authorization first. For library guidance, use the new researched modules and rewritten core guides before…
- 02Change logAdded all 26 user-requested roles with source-linked charters, standalone prompts and distinct publication briefs; a master routing/ownership model; eight…
- 03Operating model — separate expertise, one accountable systemA website problem is not automatically an SEO task. A server may be unavailable, a public hostname may resolve incorrectly, a browser may fail to submit a…
- 04Master routing protocol — choose the right specialist before actingThe purpose is to classify work, load appropriate instructions and enforce interfaces. Telling a model it is “the world's best” in 26 jobs does not supply…
- 05Handoff contracts — preserve evidence across specialtiesA handoff carries a question to be resolved , not merely a conclusion. Include task/finding IDs, sender and receiving role, current accountable owner,…
- 06Acceptance and independence — what a pass actually meansAcceptance tests the stated requirement on the stated build and environment. A builder cannot redefine a failed requirement after seeing the result. Freeze…
- 07Build public expertise from the internal discipline libraryThe private operating layer teaches an AI assistant how to route work, gather evidence and avoid conflicting fixes. It includes site facts, prompts,…
- 08Integrate the discipline library into an actual AI coding projectThe downloaded package contains role charters, standalone prompts, an advisory router and evidence-record checks. It does not install itself into a live…
- 09Decision ownership and conflicting-repair matrix“Exclusive” means one accountable decision owner, not an isolated silo. Implementation may be carried out by another authorized operator. Each row states…
- 10Full-audit coverage without launching 26 uncontrolled agentsA scoped task activates only the necessary specialists. A comprehensive website audit accounts for all 26 roles by marking each active, review-only, not…
- 11The 26-discipline operating libraryVersion 2026.09.09-d26 · Prepared for Joseph · 9 September
- 12SEO / AIO Library — 26-Discipline EditionRelease: 2026.09.09-d26 · Prepared for: Joseph · Date: 9 September
- 1326-discipline validation — actual local resultsRelease: 2026.09.09-d26. These are artifact/tool validation results, not production-site acceptance or an independent external
- 1426-Discipline Expansion — Research and Delivery ReportRelease: 2026.09.09-d26 · Date: 9 September 2026 · Prepared for:
- 15Discipline gap mapThis maps the operational coverage added in this edition. It does not claim that every related concept was absent from the million-word baseline or that…
- 16Discipline expansion — primary-source registerReviewed 9 September 2026. These 49 source records supplement, not replace, the baseline S01–S52 register. Some sources overlap intentionally so each…
- 17Discipline-library integration snippetMerge into the actual project's existing AGENTS.md only with authorization. Replace LIBRARY_ROOT with the verified project-relative library path; do not…
- 18Discipline templatesAll templates start unverified, unassessed or BLOCKED. Null means unknown, not zero. Replace planning placeholders only with verified project facts and…
- 19Discipline utilities — executable scope and limitationsPython 3.10+; standard library only. The existing four baseline utilities remain in place. The two additions are local decision-support tools, not an agent…