Realm I
Operating model
How the disciplines work as one accountable system: routing, handoffs, acceptance, integration and decision ownership.
19 volumes · 10,681 words · Reviewed 9 Sep 2026 · Whole realm as Markdown
The core sequence
-
Operating modelSeparate expertise, one accountable system
A website problem is not automatically an SEO task.
Expansion740 words.mdCharted
-
Master routing protocolChoose the right specialist before acting
The 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 tools, credentials, access, current documentation or independent verification.
Expansion660 words.mdCharted
-
Handoff contractsPreserve evidence across specialties
A handoff carries a question to be resolved, not merely a conclusion.
Expansion483 words.mdCharted
-
Acceptance and independenceWhat a pass actually means
Acceptance tests the stated requirement on the stated build and environment. A builder cannot redefine a failed requirement after seeing the result.
Expansion579 words.mdCharted
-
Build public expertise from the internal discipline library
The private operating layer teaches an AI assistant how to route work, gather evidence and avoid conflicting fixes.
Expansion749 words.mdCharted
-
Integrate the discipline library into an actual AI coding project
The downloaded package contains role charters, standalone prompts, an advisory router and evidence record checks.
Expansion553 words.mdCharted
-
Decision ownership and conflicting repair matrix
“Exclusive” means one accountable decision owner, not an isolated silo. Implementation may be carried out by another authorized operator.
Expansion530 words.mdCharted
-
Full audit coverage without launching 26 uncontrolled agents
A scoped task activates only the necessary specialists. A comprehensive website audit accounts for all 26 roles by marking each active, review only, not applicable with a reason, or blocked.
Expansion347 words.mdCharted
The 26 disciplines
-
The 26 discipline operating library
09-d26 · 9 September 2026.
Expansion461 words.mdCharted
-
26 discipline validationActual local results
09-d26. These are artifact/tool validation results, not production site acceptance or an independent external audit.
Expansion452 words.mdCharted
-
26-Discipline ExpansionResearch and Delivery Report
The updated SEO library now contains all 26 user requested professional responsibilities, with the original numbering preserved.
Expansion946 words.mdCharted
-
Discipline gap map
This 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 every inherited assertion has been verified.
Expansion316 words.mdCharted
-
Discipline expansionPrimary source register
Reviewed 9 September 2026. These 49 source records supplement, not replace, the baseline S01 to S52 register. Some sources overlap intentionally so each expansion role has a self contained authority trail.
Expansion1,385 wordsReviewed 9 Sep 2026.mdCharted
Working with AI agents
-
Instructions for AI assisted use of this library
Use the current project facts and explicit client authorization first. For library guidance, use the new researched modules and rewritten core guides before legacy material.
Expansion607 words.mdCharted
-
SEO /
AIO Library 26-Discipline Editionhtml for the integrated offline browser. It now includes all 26 professional role charters, their operating model, cross discipline playbooks, public content workbench and the prior current/legacy library.
Expansion365 words.mdCharted
-
Discipline library integration snippet
md only with authorization. Replace LIBRARY_ROOT with the verified project relative library path; do not delete existing instructions.
Expansion217 words.mdCharted
-
Discipline templates
All templates start unverified, unassessed or BLOCKED. Null means unknown, not zero. Replace planning placeholders only with verified project facts and actual authorization; never fill them with plausible inventions.
Expansion137 words.mdCharted
-
Discipline utilitiesExecutable scope and limitations
10+; standard library only. The existing four baseline utilities remain in place. The two additions are local decision support tools, not an agent runtime, credential system or deployment service.
Expansion684 words.mdCharted
Records
-
Change log
Added all 26 user requested roles with source linked charters, standalone prompts and distinct publication briefs; a master routing/ownership model; eight cross discipline playbooks; six unapproved methodology drafts; private evidence/coverage/acceptance…
Expansion470 words.mdCharted