diff --git a/.changeset/27209-pages-embed-scope.md b/.changeset/27209-pages-embed-scope.md
new file mode 100644
index 00000000000..4eeaed829bd
--- /dev/null
+++ b/.changeset/27209-pages-embed-scope.md
@@ -0,0 +1,10 @@
+---
+'@objectstack/skills': patch
+---
+
+docs(skills/objectstack-ui): `pages.md` 〈Inline metadata views〉 states the embed scope `os build` enforces — this package or a package of the same artifact it declares in `manifest.dependencies`
+
+Clause-②: no
+Metadata-protocol: none
+
+The build-lint sentence said a `metadata` fence's referenced object-rule / flow / permission set "must exist in this package". `docs/metadata-embed-ref` judges an embed against the package that ships the doc plus the packages of the same artifact that it declares in `manifest.dependencies` (direct only; one-way), so the rule the skill teaches now matches: an embed may name such a declared package's item, and anything else fails the build. No platform behaviour changes.
diff --git a/skills/objectstack-ui/rules/pages.md b/skills/objectstack-ui/rules/pages.md
index 82e48a3347a..e5f2f9a7469 100644
--- a/skills/objectstack-ui/rules/pages.md
+++ b/skills/objectstack-ui/rules/pages.md
@@ -395,9 +395,10 @@ name: crm_task_status_flow
 `os build` lints every fence: `type` must be one of the three (typo →
 did-you-mean), `name` is required, `state_machine` also needs `object`, and
 the referenced object-rule / flow / permission set **must exist in this
-package** — a dead same-package reference fails the build (same posture as
-a broken link). At render time a missing or forbidden reference degrades to
-a placeholder, never a crash.
+package or in a package of the same artifact that it declares in
+`manifest.dependencies`** (direct only; one-way) — anything else fails the
+build (same posture as a broken link). At render time a missing or forbidden
+reference degrades to a placeholder, never a crash.
 
 Embedding an `object` (data model) or an arbitrary SDUI
 component is **not** supported. **`permission` caveat:** the matrix is not