feat(ai-workspace): support SEO codex provider bridge

services/ontology-core/README.md

@@ -36,6 +36,7 @@ catalog/context-bindings.json
 catalog/assistant-access-policy.json
 catalog/assistant-actions.json
 catalog/assistant-risk-policy.json
+catalog/domain-packages/*/*.json
 examples/*.json
 docs/baseline/*.md
 docs/CONTEXT_BINDINGS.md
@@ -43,6 +44,8 @@ docs/ASSISTANT_ACCESS_POLICY.md
 docs/ASSISTANT_ACTION_REGISTRY.md
 docs/ASSISTANT_CALLER_CONTRACT.md
 docs/ASSISTANT_EXECUTION_GATEWAY.md
+docs/SEO_DOMAIN_ONTOLOGY.md
+docs/PROJECT_ONTOLOGY_INSTANCE_SCHEMA.md
 src/catalog.mjs
 src/registry.mjs
 src/validate.mjs
@@ -144,6 +147,22 @@ The resolver returns:
 - existing context bindings;
 - missing binding types required for the selected route.
 
+## Domain Packages
+
+Ontology Core can load domain packages from:
+
+```text
+catalog/domain-packages/*
+```
+
+Each package may contribute entities, relations, aliases, guardrails, evidence, resolver rules, context binding types, assistant access policy entries, assistant actions, and risk policy entries.
+
+Current package:
+
+- `seo` - NDC SEO mod domain ontology for site scans, project ontology instances, scope contracts, semantic analysis, market evidence, optimization planning, validation, changesets, and future app-owned SEO assistant actions.
+
+The package loader merges domain packages into the base catalog before validation. Domain packages extend core meanings; they do not own app data or execute mutations.
+
 ## First Implementation Target
 
 The first useful resolver flows are: