Adom Wiki Skill Pack

@@ -1,7 +1,7 @@ {   "slug": "adom-wiki-skillpack",   "title": "Adom Wiki Skill Pack",-  "version": "0.8.45",+  "version": "0.8.46",   "type": "skill",   "hero": {     "path": "screenshots/hero.png"@@ -161,4 +161,4 @@     }   ],   "discovery_pitch": "Anything touching wiki.adom.inc: publishing, page archetypes, readmes, heroes, discovery, and the wiki-bloat rule (find where a thing already lives before creating any page)."-}+}\ No newline at end of file

@@ -176,7 +176,15 @@     "workspace apply",     "workspace export",     "ship my hydrogen layout",-    "open in hydrogen"+    "open in hydrogen",+    "::adom-video",+    "adom-video wiki widget",+    "video in README",+    "generate captions",+    "closed captions",+    "VTT subtitles",+    "no dead air",+    "voiceover gaps"   ],   "discovery_pitch": "Anything touching wiki.adom.inc: publishing, page archetypes, readmes, heroes, discovery, and the wiki-bloat rule (find where a thing already lives before creating any page).",   "sample_prompts": [@@ -193,8 +201,8 @@       "prompt": "Before I create this wiki page, check whether the thing already has a home."     }   ],-  "version": "0.8.45",-  "description": "The Adom Wiki Skill Pack : one main skill plus the focused sub-skills that teach the AI to publish to wiki.adom.inc without breaking pages, name the wiki repo archetypes (Page, Skillpack, Family), and publish rich component pages (chips, molecules, boards). The wiki is six tools in one: git, package manager, releases, discussions, pull requests, and discovery. One package manager install drops the whole set onto your container. Includes reviewed Z-up component artwork, surface-selected MPN marking, reusable thumbnail caches and component-page widgets.",+  "version": "0.8.46",+  "description": "The Adom Wiki Skill Pack : one main skill plus the focused sub-skills that teach the AI to publish to wiki.adom.inc without breaking pages, name the wiki repo archetypes (Page, Skillpack, Family), and publish rich component pages (chips, molecules, boards). The wiki is six tools in one: git, package manager, releases, discussions, pull requests, and discovery. One package manager install drops the whole set onto your container. Includes reviewed Z-up component artwork, surface-selected MPN marking, reusable thumbnail caches and component-page widgets. Includes canonical video widgets, synchronized captions and chapters, and voiceover pacing checks.",   "dependencies": {     "adom/adom-wiki-hero-image": "^0.2.2",     "adom/component-widgets": "^1.1.12"@@ -235,7 +243,8 @@     "skills/wiki-component-lod/references/runtime.md",     "skills/wiki-workspaces/SKILL.md",     "skills/wiki-brand/SKILL.md",-    "skills/wiki-hero-glb/SKILL.md"+    "skills/wiki-hero-glb/SKILL.md",+    "skills/wiki-video-captions/SKILL.md"   ],   "scripts": {     "install": "./install.sh",@@ -257,4 +266,4 @@     "email": "[email protected]"   },   "org": "adom"-}+}\ No newline at end of file

@@ -4,13 +4,16 @@ description: >-   How visibility and licensing work on the Adom Wiki (wiki.adom.inc): a page can   keep its git source PRIVATE while its releases / wiki package stay PUBLIC, so   people install the compiled app but can't read the code, the pattern for-  proprietary apps. Covers public vs private source, the private readme, and the+  proprietary apps. Covers who can read a PRIVATE page (org pages like adom/x:+  every org member; personal pages like ray/x: only the owner plus explicit+  share grants), public vs private source, the private readme, and the   open-source vs closed-source Page variants. Read this when deciding how much of   a page to expose, or shipping a proprietary tool. Trigger words: private wiki   source, public app private source, proprietary wiki page, closed source app,   private readme, hide source code wiki, install compiled app no source, open   source wiki repo, license a wiki repo, visibility settings wiki, who can see my-  source.+  source, who can see my private page, can employees see my private page,+  share a private page with my team, page share, org private vs personal private. ---  Parent skill: **adom-wiki-skillpack**@@ -29,6 +32,23 @@ repo serve both open-source and proprietary models. | **Releases / wiki package** | Anyone can `adom-wiki pkg install` / download the binary | Restricted install | | **Readme** | Public README shown | A separate **private readme** can document a private-source page | +## Who can read a PRIVATE page: it depends on the namespace++`private` means different things depending on who owns the page. Check the part before the slash.++| Page | Who can read it while private |+|---|---|+| **Org page**, `adom/<slug>` | Every signed-in member of that org, which for `adom/` means every Adom employee. Share it by sending the link. |+| **Personal page**, `<user>/<slug>` (e.g. `ray/molecule-...`) | **Only the owner**, plus anyone explicitly granted with `adom-wiki page share <ref> --user <handle>`. A signed-in colleague with no grant gets the same 404 as the public. |++The tempting mistake is to say a private page under a person's name "can be opened by any signed-in employee". It can't: the org-wide rule only applies to pages the org owns. (Corrected 2026-10-14 after an agent told Ray's team they could open `ray/...` pages and Colby, signed in, could not.)++To share a personal private page with the team, do one of these:+- grant each person: `adom-wiki page share ray/<slug> --user <handle>`; list grants with `adom-wiki page shares ray/<slug>`;+- move it under the org: `adom-wiki repo transfer ray/<slug> --help` (it then follows the org rule). Ask the owner first, because a transfer changes the page's URL.++Verify access from **someone else's** login. The owner always sees their own page, and anonymous and no-access requests both return the same 404 on purpose, so your own session can't prove a colleague can read it.+ ## The proprietary pattern (closed-source Page)  The combination that makes proprietary apps work on the wiki: