@awebai/oats 0.24.1 → 0.24.2

package/docs/design/2026-09-20-redesign-program-board.md

@@ -2,7 +2,7 @@
 
 **Purpose:** the one accurate view of every work stream in the redesign, what is on main, what is in flight, who owns it, and what blocks it. Lead: `oats-expert` (redesign lead). Updated whenever anything merges, is returned, or reality changes. Older per-lane boards are superseded by this file.
 
-**Last update:** 2026-09-20 17:40Z · main `87292f40` · OKF `v2.1.1`
+**Last update:** 2026-09-21 04:10Z · main `feef2a2f`+ · **OATS v0.24.2 tagged (CI)** · OKF v2.1.1 · oats-framework/v1.1.1 · aweb v1.11.0 · oats-knowledge 8d67eab4
 
 Legend: ✅ on main/published · 🔄 in flight (PR/branch) · 🟡 preserved, not adopted · ⬜ not started · ⛔ blocked
 
@@ -10,14 +10,14 @@ Legend: ✅ on main/published · 🔄 in flight (PR/branch) · 🟡 preserved, n
 
 | # | Stream | State | Owner | Next action |
 |---|---|---|---|---|
-| S1 | Knowledge capability contract rework (kernel↔provider boundary, OKF 2.x) | ✅ shipped 0.24 / **OKF 2.1.1 released** (PR4 merged; mirror, catalog ref, soul source bumped) | P | done for this phase; OATS 0.24.1 cut after L's custody fix |
-| S2 | Workspace/Portable Souls adoption of the OATS repos | ✅ PR23 + PR24 merged · ✅ member `oats.yaml` on main in oats-okf/aweb/authoring/jira · ⛔ oats-dev, oats-linear (no push access, human) | M, L, lead | human grants access → push 0434f4ef/8c183c37; then pin imports; then fresh deployment gate |
-| S3 | Messaging capability readiness on the new infrastructure (aweb) | 🔄 codec PR2 + custody WIP · needs profile pin | P | lead pins pilot profile + answers authority question |
-| S4 | Official capabilities `oats.core` / `oats.setup` + explicit default + onboarding `oats-setup-expert` | 🔄 D1 in progress (P, `feat/d1-oats-core-setup`, package → `oats.framework` 1.1.0) · 🔄 D2 in progress (L) · ⬜ D3 | P (D1), L (D2, D3) | review D1/D2 PRs; assign D3 after D2 |
-| S5 | Official marketplace = reviewed list in oats repo | ✅ D4 merged PR26 (`docs/official-marketplace.md`, policy pointer) · ⬜ `oats.core`/`oats.setup` entries after D1 release | M | add entries at D1 release |
-| S6 | Five expert souls created in the oats repo (`souls/<name>/`) | 🔄 assigned to M (`feat/s6-expert-soul-editions`) from the reviewed candidate; `souls/oats-expert` on main | M | review PR; `oats.core` follow-up after D1 |
-| S7 | Centralised per-soul knowledge in `oats-knowledge` (migration + PR-only learning) | 🟡 35 curated concepts uncommitted on local `curation/expert-knowledge`; bootstrap proven on personal repo; `awebai/oats-knowledge` EMPTY, private | lead + human (visibility) | decide visibility; publish curation as PR; point souls' `stores.oats` at it |
-| S8 | Desktop parity (marketplace view, soul creation with `oats.core`, onboarding flow) | ⬜ after S4/S5 | fresh Desktop engineer (blocked: `claude` absent) | pick runtime; spawn |
+| S1 | Knowledge capability contract rework (kernel↔provider boundary, OKF 2.x) | ✅ OATS 0.24.1 / OKF 2.1.1 published | P | done for this phase |
+| S2 | Workspace/Portable Souls adoption of the OATS repos | ✅ workspace + seven indexes + **six imports** (five experts @caa341f3, setup expert @0aad753c) · ✅ second-operator gate run · 🔄 five seams → L, target 0.24.3 | lead, L, Antares | seams PR; Antares re-run on 0.24.2 (aweb 1.11.0) |
+| S3 | Messaging capability readiness on the new infrastructure (aweb) | ✅ aweb 1.11.0 released · ✅ **catalog + six editions pin v1.11.0 (0.24.2)** · ⬜ second-operator re-run | P, lead | Antares re-run |
+| S4 | Official capabilities `oats.core` / `oats.setup` + explicit default + onboarding `oats-setup-expert` | ✅ D1, D2, **D3 merged (PR35)**: `oats onboard` verified live (acquire 1.1.1 → setup expert with both caps → scaffold composes the five capability skills, no legacy) · `oats.framework` 1.1.1 tagged | P, L | done; Desktop surfaces → S8 |
+| S5 | Official marketplace = reviewed list in oats repo | ✅ D4 merged · ✅ `oats.framework` 1.1.1 listed (`oats.core`, `oats.setup`, `oats.knowledge-theory` aliases) | M | Desktop view → S8 |
+| S6 | Five expert souls created in the oats repo (`souls/<name>/`) | ✅ five + `oats-setup-expert` on main, all declaring `oats.core`, exported + imported | M, L, lead | legacy `agents/` cutover after S7 proof |
+| S7 | Centralised per-soul knowledge in `oats-knowledge` (migration + PR-only learning) | ✅ **repo PUBLIC; PR #1 merged → main 8d67eab4, 25 accepted concepts**, owners = published souls, validator pinned OKF 2.1.1 · 🔄 fresh-reader proof assigned to Juan's side · ⬜ legacy in-soul knowledge decommission | lead, Antares/Juan | fresh-reader + PR-learning proof; then retire `agents/*/soul/knowledge` |
+| S8 | Desktop parity (marketplace view, soul creation with `oats.core`, onboarding flow) | ⬜ after D3 · **host offered: Juan's machine (has `claude`)** — accepted | fresh Desktop engineer on Juan's host | brief + spawn params after D3 |
 
 ## S1 — Knowledge capability contract rework
 - ✅ Provider-neutral contract, binding wire v1, helper/input contract, retained execution: OATS 0.24.0 + OKF 2.1.0 (f20f8e57) published.
@@ -28,21 +28,32 @@ Legend: ✅ on main/published · 🔄 in flight (PR/branch) · 🟡 preserved, n
 - ✅ **PR23 merged f6d5a89b**: `oats-workspace.yaml` (7 members, `imports: []`), `oats.yaml` (exports souls/oats-expert, oats-package, capabilities/oats-authoring), transitional `souls/oats-expert/` edition, `docs/workspace-adoption.md`, layout tests.
 - ✅ **PR24 merged da38e5a9**: deletion of `skills/oats-portable-setup` + `oats inspect --request` read-only seam (ACCEPTED as the public inspection route); full gate 1621/0.
 - ✅ Member `oats.yaml` merged to main: oats-okf #3 (fec78a20), oats-aweb #1 (069ea2f6), oats-authoring #1 (54183a6a), oats-jira #1 (2f855daf).
-- ⛔ oats-dev (0434f4ef) and oats-linear (8c183c37): neither M nor the lead's GitHub account has push — **human must grant access or push**.
+- ✅ oats-dev#1 (main 6e164ee3) and oats-linear#1 (main a2121e48) merged after Juan granted write access — M's exact commits 0434f4ef / 8c183c37.
 - ⬜ `imports:` pin of `souls/oats-expert` at its published revision (after member indexes).
 - ⬜ Fresh local deployment from the shared definition (P1.5) — the real acceptance gate.
 
+## S2 — second-operator gate report (Antares, Juan's machine, 2026-09-20)
+Fresh dir, local `@awebai/oats@0.24.1`, no prior state. `inspect --request` → ready-for-preparation, membership eligible, source `souls/oats-kernel-expert@caa341f3`. `prepare` resolved and materialized `oats-package@caa341f3`, `oats.okf@v2.1.1`, `oats.aweb@v1.10.3`, `oats.core`, `oats.setup`, `oats.knowledge-theory` + soul; artifact-set approvals worked. Terminal: `needs-configuration` + `provider-not-qualified` (aweb 1.10.3 has no binding interface) — expected. Seams (assigned to L, one PR, priority):
+1. `inspect --request` requires `workTarget`; `prepare --request` refuses it (`buildFreshPreparationRequest` exists but the CLI never uses it).
+2. `prepare` on the absent deployment inspect blessed → raw `ENOENT` + host path through the JSON envelope.
+3. `prepare` writes lock v3; `oats trust <cap> --dir` rejects it (`unsupported lockfileVersion 3`) → dead end from `--help`.
+4. The working `trust --deployment --artifact-set <sha256>` route is absent from `--help`.
+5. Problems carry `origins: []` and no slot/capability; aweb's missing interface masks OKF diagnostics — a valid and a bogus `stores.oats` binding produce byte-identical output. **Fix first.**
+
 ## S3 — Messaging (aweb) on the new infrastructure
+- ✅ **aweb PR3 merged → v1.11.0 (93f8ab96)**: `binding {normalize,bind,check}` on the existing wire; `check` = HOME-route operational custody only (explicit private team, `delivery: session`, kernel ≥0.24.2 via caller-owned `OATS_CLI_BIN`, retained `launchSelection` must be input-capable Claude/Codex; strict-Pi print → `needs-configuration`, never downgraded). Native adapter over existing `aw` commands with physical identity-dir custody and redacted tokens. Standalone 30/0; coupling 14/0 vs kernel b92f0d07. PR33 (launchSelection projection, OATS_CLI_BIN in codec env) merged b92f0d07.
 - Facts: released aweb 1.10.3 has no binding interface; broker refuses. aw 1.36.1 broker calls `oats session inspect/input --home H`; never restarts stopped runtime; strict-Pi print mode can't take session input.
 - 🔄 oats-aweb **PR2** codec (165b20e) + uncommitted `lib/captured-execution.mjs` (6/6).
 - ✅ Lead answered (d9d912a4): pilot primary = Pi strict print host explicit model; helper = Pi sole-OKF (Claude/Codex allowed by 2.1.1); authority = existing HOME route + L's custody fix, gated on `oats >=0.24.1`; no new grant mechanism. P delivers aweb 1.11.0 PR. 
-- 🔄 L finding c21e36ff accepted; fix assigned (L, `fix/home-route-captured-custody`): reuse `readCapturedInstanceAuthority` on the HOME-only route, refuse before transport.
+- ✅ **PR27 merged (5af848fc)**: HOME-only session route applies existing captured custody; refuses before transport on drift. Full gate 1626/1632 (2 pre-existing env failures reproduced on main). Ships in **v0.24.1** — the kernel floor the aweb adapter gates on.
 
 ## S4 — `oats.core` / `oats.setup` / onboarding
+- ✅ **D3 merged PR35 (37c5c012)**: `oats onboard` classic local bootstrap; edition `souls/oats-setup-expert` (core+setup, provider defaults `none`, no knowledge owner). Full gate 1639/0. Live: onboard → acquire `oats.framework` 1.1.1 @0aad753c → soul declares both caps at that commit → scaffold-only spawn composes exactly `oats-operate, oats-souls, oats-config, oats-packages, oats-workspace-setup` + the `oats.core` injection, no legacy kernel skills. Baseline hygiene fixed on main (a96f24df).
+- ✅ **D1 merged PR28 (70b10822)**, distribution tag `oats-framework/v1.1.0` on 9930dcfb; **D2 merged PR29 (9930dcfb)** full gate 1634/0. Verified live: `oats create` writes `requires.capabilities.oats.core` with the catalog source; `oats install oats.framework` acquires all three capabilities from the tag.
 - ✅ Decision + plan D1–D4 on main 18af53be; docs reference as accepted-not-shipped.
 - 🔄 **D1** (P, started 16:29Z; package identity confirmed: rename distribution package to `oats.framework` 1.1.0, capabilities 1.0.0, `oats.knowledge-theory` unchanged) package `oats.core` (`oats-operate`, `oats-souls`, oats.md injection) and `oats.setup` (oats-config, oats-packages, adoption guidance) under `oats-package/capabilities/`. Owner P.
 - 🔄 **D2** (L, after custody fix) soul creation writes explicit `requires.capabilities.oats.core`; kernel skill list de-ambiented (one-release coexistence); checked-in souls updated. Owner L.
-- ⬜ **D3** onboarding creates + instantiates `oats-setup-expert` (edition in `souls/`). Owner L (+M edition).
+- 🔄 **D3** (L, in progress) onboarding creates `oats-setup-expert` (edition in `souls/`); CLI verb **`oats onboard`** — `oats setup` is already the record capture-setup command and stays untouched.
 - Exit: fresh onboarding → running setup expert; created soul shows `oats.core`; kernel ships no ambient operational skill.
 
 ## S5 — Official marketplace
@@ -50,21 +61,23 @@ Legend: ✅ on main/published · 🔄 in flight (PR/branch) · 🟡 preserved, n
 - ✅ **D4 merged PR26 (786490ae)**: `docs/official-marketplace.md`, `package-catalog.json` policy pointer (inert to the reader), README/packages/capabilities links, D3 sketch in adoption guide. ⬜ entries for `oats.core`/`oats.setup` at D1 release. Desktop view → S8.
 
 ## S6 — Five expert souls in the oats repo
+- ✅ **PR30 merged (40a579dc)** + maintainer follow-up **caa341f3**: all five declare `oats.core: {source: repo:oats-package}`, oats.okf@v2.1.1; `oats.yaml` exports all five; `oats-workspace.yaml` imports all five at caa341f3 (375b9f42). Live inspection against published main resolves them.
 - Roster (decided): `oats-expert`, `oats-kernel-expert`, `oats-desktop-expert`, `market-research-expert`, `oats-assistant`.
 - 🟡 Candidate: `expert-roster` worktree (b5e233b9 + 519 uncommitted changes: five `agents/<name>/soul/` + legacy roster deletions). Reviewed earlier; NOT committed.
 - ✅ `souls/oats-expert` transitional edition on main already declares owns/reads for the five nodes.
 - 🔄 Assigned to M (17:05Z): create `souls/<name>/` editions for the other four from the candidate; each declares `oats.core` explicitly (S4 rule) + `oats.okf`/`oats.aweb` sources; export in `oats.yaml`. Legacy `agents/` roster retirement is a separate, later cutover.
 
 ## S7 — Centralised knowledge in `oats-knowledge`
+- ✅ Juan made the repo PUBLIC (2026-09-20). Bootstrap history pushed to main; **PR #1 merged (8d67eab4)**: 25 curated concepts, roadmap re-verified to the 0.24.1 baseline and 2026-09-20 decisions, validator pinned to OKF v2.1.1, strict OKF 25/0/0, ownership tests 24/24.
 - 🟡 Curated corpus: 35 concepts (five nodes) on local `curation/expert-knowledge` in `/Users/pepe-reyero/OATS-workspace/oats-knowledge`, **uncommitted**. Bootstrap + one PR-only harvest already proven on `josep-reyero/oats-knowledge` (3 commits).
 - ⛔ Target `awebai/oats-knowledge` is EMPTY and PRIVATE; **visibility undecided** (stated requirement: public). Human decision needed before publishing.
 - ⬜ Then: push bootstrap + curation as PR to awebai; bind `stores.oats` in the pilot deployment; prove fresh-reader + Git-PR learning with the new souls; retire old in-soul knowledge (`agents/*/soul/knowledge`) as a final cutover.
 
 ## S8 — Desktop parity
+- Finding (L, D2 audit): the Desktop server has **no soul-creation endpoint** today (roster reads, existing-soul edits/capability operations, instance spawn only). Soul creation with explicit `oats.core`, the marketplace view and the onboarding flow are new Desktop features, not wiring.
 - ⬜ After S4/S5: official marketplace view/search; soul creation showing `oats.core`; onboarding flow; redesign parity vs `Oats UX Redesign and Desktop Discovery (1)`.
 - ⛔ Fresh `oats-desktop-engineer` not spawned: `claude` not on PATH → choose Pi/Codex or install (human).
 
 ## Blockers needing the human
-1. `awebai/oats-knowledge` visibility (public vs private) — gates S7 publication.
-2. Push access to `awebai/oats-dev` and `awebai/oats-linear` for `josep-reyero` (or human pushes M's exact commits 0434f4ef / 8c183c37 as `oats.yaml`) — gates S2 completion.
-3. Desktop engineer runtime (Claude absent) — gates S8.
+- ~~oats-knowledge visibility~~ → PUBLIC (Juan). ~~oats-dev/oats-linear access~~ → granted, indexes merged. ~~Desktop runtime~~ → Juan's machine hosts the Desktop lane (has `claude`).
+- None open at 23:10Z. Juan's side (Antares) takes: (a) fresh-deployment gate P1.5, (c) fresh-reader proof, (b) Desktop host after D3.

package/docs/first-team.md

@@ -42,6 +42,48 @@ For several repositories initialize their common workspace, then select the
 repository owning the soul with `--dir /path/to/workspace/project` for
 create/spawn/retire. A team roster does not select a work repository for spawn.
 
+## Onboarding with the setup expert
+
+For a kernel build that includes `oats onboard` (check `oats onboard --help`),
+start in an explicit empty deployment:
+
+```bash
+oats onboard --dir /absolute/new-deployment --json
+```
+
+This command is **not present in the published 0.24.0/0.24.1 kernels**. It is a
+classic local bootstrap, not captured preparation or workspace enrollment. It
+acquires `oats.framework` from the official catalog, exact-locks its artifacts,
+selects only `oats.core` and `oats.setup` for the new local `oats-setup-expert`,
+and prints the exact next spawn command. Review and run the returned
+`result.next.command` when ready; it addresses this same kernel and deployment.
+Onboarding itself never launches a model, changes native authentication or
+installs capture hooks/services. **`oats setup` remains the separate record
+capture-setup command**, not an alias for onboarding.
+
+The expert receives `oats-operate`, `oats-souls`, `oats-config`, `oats-packages`
+and `oats-workspace-setup`, without duplicate legacy kernel skill copies. It has
+no hard knowledge/messaging dependency, so it can help select and configure those
+providers afterward. Catalog identity grants no executable trust: the bootstrap
+uses resource-only core/setup capabilities and refuses unexpected executable
+surfaces instead of auto-approving them.
+
+An existing roster is refused unless `--force-existing` is explicit. That flag
+permits adding the new soul, not overwriting an existing setup expert or disabling
+providers for other souls. Failures report partial acquisition/creation rather
+than claiming atomic captured preparation. Preserve that evidence before retrying.
+
+Optional `--workspace git:host/org/repository[@revision]` reads the selected
+repository through ordinary discovery: use its pinned `oats-setup-expert` import
+when present, otherwise its own advertised `souls/oats-setup-expert` edition at
+the observed revision. Missing or incompatible explicit sources refuse; they do
+not fall back to the packaged default. The copied edition's package must match
+the official acquisition; workspace policy, teams and provider adoption values
+are not silently adopted. Without this option, only the packaged definition and
+instruction text are used—no knowledge corpus is bundled.
+
+The manual path below retains its stated older integration/version scope.
+
 ## Configure explicit knowledge and optional messaging
 
 Edit the existing entries in `oats-config.yaml`; do not append a second

package/docs/layers.md

@@ -80,7 +80,7 @@ Messaging is conversation, not automatically task state. Accepted knowledge may
 
 The current slot name is **`messaging`**. The capability owns native identity, addressing, team membership, transport, wake delivery and qualification. A team alias in a workspace is a declaration, not proof that an actor is enrolled or a privacy property is enforced.
 
-The released aweb1.10.3 integration supports its legacy setup/lifecycle path but lacks the captured provider-binding interface required for a new portable profile. That capability needs adaptation and real qualification; a codec that always refuses readiness is not completed messaging support.
+aweb 1.10.3 supports its legacy setup/lifecycle path but lacks the captured provider-binding interface. **aweb 1.11.0** (OATS >=0.24.2) adds it: `check` qualifies HOME-route operational custody for an input-capable Claude/Codex primary with an explicit private team and `delivery: session`; a strict-Pi print primary reports `needs-configuration` rather than dropping the requirement. Qualification is not account delegation, broker delivery or model consumption.
 
 The earlier proposed `reach` ladder is **not an enforced universal field**. In particular, aweb's `team_and_contacts` includes verified same-team senders; the compatibility spellings `contacts-only` and `contacts_only` do not establish owner-only admission. A config command succeeding proves neither inbound/outbound restrictions nor knowledge visibility. See the [identity/membership amendment](design/2026-09-08-expert-assisted-deployment-proposal.md#membership-reach-and-visibility-are-separate) and [messaging boundary](design/2026-09-16-messaging-capability-contract.md).
 

package/docs/official-marketplace.md

@@ -58,17 +58,22 @@ or workspace membership alone does not make a package official.
 Contact and license evidence may live in the package/repository documentation;
 this policy does not invent new catalog or manifest fields.
 
-## Planned first set
+## Listed first set
 
-- Already listed: `oats.okf`, `oats.aweb`, `oats.authoring`, `oats.jira`,
-  `oats.linear`, `oats.dev` and `oats.knowledge-theory`.
-- **Planned, not yet listed:** `oats.core` for OATS operation/soul guidance, and
-  `oats.setup` for OATS Soul Setup, configuration and package guidance. Add their
-  catalog entries only after their actual D1 package releases exist and pass
-  review. They are not available merely because this document names them.
+- Listed capabilities: `oats.okf`, `oats.aweb`, `oats.authoring`, `oats.jira`,
+  `oats.linear`, `oats.dev`, `oats.knowledge-theory`, `oats.core` and `oats.setup`.
+- **`oats.framework` 1.1.1** is listed at tag `oats-framework/v1.1.1` in
+  `awebai/oats`, payload root `oats-package`. The `oats.core`, `oats.setup` and
+  `oats.knowledge-theory` aliases select that distribution; package identity is
+  distinct from capability identity. Core supplies operation/soul guidance;
+  setup supplies OATS Soul Setup, configuration and package guidance.
 
-The [workspace adoption guide](workspace-adoption.md) describes the separate
-planned setup-expert flow. No package is silently added to an existing soul.
+These entries are in the current repository catalog. An older installed CLI keeps
+its bundled catalog; publication here does not update that installation or rewrite
+old source references, locks or tags. Follow that CLI's supported acquisition path.
+The [workspace adoption guide](workspace-adoption.md) distinguishes the published
+capabilities and five expert imports from the still-pending D3 setup-expert flow.
+No package is silently added to an existing soul.
 
 ## Updates, deprecation and removal
 

package/docs/packages.md

@@ -402,7 +402,7 @@ sources; installing a kernel does not advance existing package locks:
 {
   "packages": {
     "oats.okf": { "url": "https://github.com/awebai/oats-okf.git", "ref": "v2.0.0", "path": "oats-package" },
-    "oats.knowledge-theory": { "url": "https://github.com/awebai/oats.git", "ref": "v0.23.0", "path": "oats-package" },
+    "oats.framework": { "url": "https://github.com/awebai/oats.git", "ref": "oats-framework/v1.1.1", "path": "oats-package" },
     "oats.dev": { "url": "https://github.com/awebai/oats-dev.git", "ref": "v1.0.0", "path": "oats-package" }
   },
   "capabilities": { "oats.review": "oats.dev" }
@@ -427,13 +427,17 @@ npm drops the source worker soul's `CLAUDE.md -> AGENTS.md`. It must not be
 advertised as a complete local package or repaired after acquisition to evade
 integrity checks. Git transport preserves the canonical source alias.
 
-The optional `oats.knowledge-theory` package is a separate Git payload in this
+The `oats.framework` distribution package is a separate Git payload in this
 repository's `oats-package/`, excluded from the kernel npm tarball. The catalog
-entry selects published framework v0.23.0, which contains package 1.0.0.
-The source reference patch 1.0.1 is separately available through an explicit
-v0.23.1 Git source after that framework tag is published. It supplies an authoring skill and
-`knowledge-theory-expert`, not a default knowledge-layer binding, runtime judge
-or OKF dependency. Acquiring it does not activate it.
+entry selects the published `oats-framework/v1.1.1` tag, which exports three
+capabilities: `oats.core` (day-to-day operation: `oats-operate`, `oats-souls`
+and the "you run on OATS" briefing — declared explicitly on every soul by
+default at creation and removable), `oats.setup` (OATS Soul Setup: `oats-config`,
+`oats-packages`, `oats-workspace-setup`) and the optional `oats.knowledge-theory`
+(authoring skill and `knowledge-theory-expert`). Acquire it with
+`oats install oats.framework`; the capability ids also resolve through the
+catalog aliases. Acquiring it does not activate anything, bind a knowledge
+layer or add a runtime judge.
 
 Updating OKF v1 to v2 is a breaking capability change. Preserve existing
 knowledge and source state/cursors, explicitly bind/provision external owners,

package/docs/release-notes/v0.24.2.md

@@ -0,0 +1,21 @@
+# OATS v0.24.2 — `oats onboard`, official capabilities in a soul's definition, aweb 1.11.0 pairing
+
+Kernel/Pi/Desktop **0.24.2**. Publication is not deployment: every operator still installs, approves and qualifies locally.
+
+## What changed
+
+- **`oats onboard [--dir <deployment>] [--workspace <git:source[@rev]>] [--force-existing] [--json]`** — bootstrap a deployment with an **`oats-setup-expert`** soul that holds `oats.core` and `oats.setup`. Acquires the official `oats.framework` package through the existing engine (resources-only guard before commit, no catalog auto-trust), activates exactly those two capabilities for that soul, writes its definition with both pinned at the acquired immutable commit, and **prints** the spawn command — it never launches a model. Classic local bootstrap, not captured preparation. `oats setup` (record capture setup) is unchanged.
+- **Soul creation declares `oats.core` explicitly.** `oats create` and new local souls write `requires.capabilities.oats.core` resolved from the official catalog; `--no-oats-core` opts out; nothing is invented when the catalog has no entry. When a soul declares `oats.core` or `oats.setup`, the kernel composes **neither** the legacy kernel skills (`oats`, `oats-config`, `oats-packages`) nor the `kernel:oats` injection — the capability's skills are the operational curriculum. Souls without it keep legacy behavior; `oats doctor` prints an informational line.
+- **Official capabilities.** `oats.framework` **1.1.1** (tag `oats-framework/v1.1.1`) exports `oats.core` (`oats-operate`, `oats-souls`, "you run on OATS" briefing), `oats.setup` (`oats-config`, `oats-packages`, `oats-workspace-setup` — now documenting the operator request shape) and `oats.knowledge-theory`. Listed in the official catalog with capability aliases.
+- **Retained inspection projects `launchSelection`** (`{runtime, model}` or `null`) for the primary from the verified retained record; provider binding codecs receive the same-kernel `OATS_CLI_BIN` after the environment scrub. These are what a provider `check` needs to be truthful about the primary's profile.
+- **aweb 1.11.0 pairing.** The catalog and all framework soul editions pin `oats.aweb@v1.11.0`, which adds the portable binding interface (floor `>=0.24.2`). Its `check` qualifies HOME-route operational custody only: explicit private team, `delivery: session`, an input-capable Claude/Codex primary. A strict-Pi print primary reports `needs-configuration`; the requirement is never dropped.
+- **Six framework soul editions** exported and imported by `oats-workspace.yaml`: the five knowledge-owning experts (`oats-expert`, `oats-kernel-expert`, `oats-desktop-expert`, `market-research-expert`, `oats-assistant`) at `caa341f3` and `oats-setup-expert` at `0aad753c`. All six declare `oats.core` from the repository's own payload.
+- Baseline hygiene: golden fixtures use a genuinely empty catalog; the package check lazy-loads dev validators so syntax-only lanes work without `node_modules`.
+
+## Second-operator gate
+
+An independent operator on a fresh machine adopted the shared definition from public sources through `inspect` → `prepare` → approvals with 0.24.1: the whole graph (including `oats.core`/`oats.setup`) resolved and materialized; preparation stopped at aweb 1.10.3 as declared. Five usability seams were recorded (request-file mismatch between `inspect`/`prepare`, raw ENOENT on an absent deployment, `trust --dir` rejecting lock v3, `--artifact-set` missing from help, unattributed provider problems). **They are not fixed in this cut**; see the [program board](../design/2026-09-20-redesign-program-board.md).
+
+## Not in this cut
+
+Desktop marketplace view / soul creation UI, legacy `agents/` roster and in-soul knowledge decommission (after the fresh-reader proof against the public `oats-knowledge`), Pi session-input support.

package/docs/souls-and-instances.md

@@ -54,6 +54,31 @@ in a soul bundle; see [knowledge](knowledge.md) for its prepared version scope.
 Future integrations may add expert-specific artifacts such as rule files or
 runtime-specific guidance, while keeping `AGENTS.md` canonical.
 
+## OATS operational knowledge is a capability
+
+New souls declare `requires.capabilities.oats.core` with a Git source resolved
+from the official package catalog. `oats create` and new local-soul scaffolds
+write that requirement; `--no-oats-core` explicitly omits it. If the catalog has
+no published revision yet, creation reports `needs-configuration` (also in JSON
+`notes`) and leaves the requirement absent rather than inventing a source.
+Declaring a capability is not acquiring, activating or approving it: those remain
+normal deployment/preparation steps. The Desktop server currently has no
+soul-creation endpoint; `oats soul set` edits existing definitions only.
+
+The dependency is visible and removable in `soul.yaml`. Updating an existing
+local soul preserves its requirements—including a deliberate removal—rather
+than applying the creation default again. For the one-release transition,
+a declaration of **either `oats.core` or `oats.setup`** suppresses the entire
+legacy kernel operational skill list (`oats`, `oats-config`, `oats-packages`)
+and `kernel:oats` injection. This also prevents setup's moved skill names from
+colliding with the kernel copies; no skill override is needed for this case.
+Without either declaration, legacy composition is unchanged.
+`oats doctor --soul <name>` reports an absent `oats.core` as an informational
+deprecation notice, not an error. Instance-boundary, work-mode and
+configuration-declared briefings remain kernel-owned. Existing captured records
+keep their retained resources; this does not migrate them or retire the kernel
+skill files yet.
+
 ## Instance anatomy
 
 An instance has a lifecycle, but need not be short-lived. It is the identity of

package/docs/workspace-adoption.md

@@ -5,12 +5,30 @@ source-complete exports and declares its own reciprocal membership. `oats-dev`
 remains a development-capability repository, including `oats.review`; membership
 neither activates that package nor replaces its existing configuration templates.
 
-This is phase 1: a shared repository graph and a transitional portable edition of
-**the existing oats-expert**. It is not the five-role rebuild, the curated knowledge
-cutover, a shared live runtime, a private-team enrollment or Desktop feature parity.
+This guide covers the shared repository graph and portable expert source editions,
+beginning with **the existing oats-expert**. Source publication is not a live
+five-role roster or curated knowledge cutover, a shared runtime, private-team
+enrollment or Desktop feature parity.
 The [phase plan](design/2026-09-20-workspace-and-portable-adoption-plan.md) and
 [knowledge model](knowledge-theory.md) retain those separate boundaries.
 
+## The five framework experts
+
+The indexed source editions are `oats-expert`, `oats-kernel-expert`,
+`oats-desktop-expert`, `market-research-expert` and `oats-assistant`. Each declares
+`owns` for its own same-named node and `reads` for the other four through logical
+store `oats`, preserving the reviewed owner UUIDs. These are knowledge-routing and
+context declarations, not access grants or proof of accepted knowledge. The parallel
+`souls/` editions neither replace the legacy `agents/` roster nor adopt the curated
+KB or change live instances; actual adoption still needs compatible providers and
+explicit bindings. All five now explicitly declare `oats.core` under
+`requires.capabilities`, with `source: repo:oats-package`. This retains the complete
+package from the same reviewed source revision.
+
+The dependency is visible and removable in the authored definition, not a change
+to existing captured records. An edited edition needs its own reviewed publication
+and import update; changing today's source does not rewrite an older pinned import.
+
 ## Shared versus local
 
 | Git-shared declaration | Operator-local input or evidence |
@@ -22,17 +40,18 @@ The [phase plan](design/2026-09-20-workspace-and-portable-adoption-plan.md) and
 | A reviewed source revision | Exact executable approval, current readiness and deployment acceptance |
 
 No machine paths, credentials, private team identifiers, accepted-store locator or
-owner registry belongs in the public workspace. The uninitialized phase-2 knowledge
-repository is not advertised as a ready knowledge export. Preserve the parked
+owner registry belongs in the public workspace. Knowledge publication and acceptance
+(S7) remain separate; no ready knowledge export is advertised. Preserve the parked
 roster/curation and every old home, lock, source, pending job, history and worktree.
 
 ## Planned onboarding: OATS Soul Setup (D3)
 
-**Not shipped in OATS 0.24.** The planned onboarding flow creates and instantiates
+**The D3 onboarding flow remains pending.** It will create and instantiate
 `oats-setup-expert`, declaring both `oats.core` and `oats.setup` from the
-[official marketplace](official-marketplace.md). Their package releases and this
-onboarding flow are future work, not existing catalog entries or a new command
-introduced by this guide.
+[official marketplace](official-marketplace.md). Those capabilities are now
+published in `oats.framework` 1.1.0 and listed; the separate setup-expert edition
+and onboarding entry point do not become available merely by listing the package.
+This flow was not shipped in the 0.24.0 or 0.24.1 kernel releases.
 
 - The setup expert will help the operator adopt repositories, select capabilities
   and carry out the normal prepare/approve/scaffold/start steps. It bypasses no
@@ -41,27 +60,29 @@ introduced by this guide.
   and its source explicitly. The operator can remove or replace that dependency
   by editing the authored definition, not a captured record; the kernel will not
   silently reinsert an absent one.
-- The CLI/Desktop entry point remains separately implemented and reviewed. Do not
-  invent a workspace init/adopt command, create a setup soul from this sketch, or
-  treat a planned package as installed. Existing instances and retained resources
-  are not rewritten by the plan.
+- The CLI/Desktop entry point still requires separate implementation and review.
+  Do not invent a workspace init/adopt command, create a setup soul from this
+  sketch, or treat a listed package as installed. Existing instances and retained
+  resources are not rewritten by the plan.
 
-## What this first source commit establishes
+## Stage two: published experts and pinned imports
 
 - `oats-workspace.yaml` explicitly admits `oats` and the six intended capability
   repositories: `oats-dev`, `oats-okf`, `oats-aweb`, `oats-authoring`, `oats-jira`
   and `oats-linear`. It activates no additional capability; tasks default to none.
-- `oats.yaml` advertises `souls/oats-expert` and the actual framework package roots
-  `oats-package` and `capabilities/oats-authoring`, not the npm root as a fictitious
-  OATS distribution. Its workspace backlink names the same framework repository.
-- `souls/oats-expert/` is parallel to, not a replacement for, the live `agents/`
-  source. It contains canonical instructions, `CLAUDE.md -> AGENTS.md`, and the
-  existing reviewed PR/release procedure closure. No durable KB is copied into it.
-- The role preserves its knowledge owner, owned node and four cross-read interests.
+- `oats.yaml` exports all five `souls/<name>` editions above and the actual package
+  roots `oats-package` (`oats.framework`) and `capabilities/oats-authoring`, not
+  the npm root as a fictitious OATS distribution. Its workspace backlink names
+  the same framework repository.
+- The editions are parallel to, not replacements for, the live `agents/` roster.
+  Each contains canonical instructions, `CLAUDE.md -> AGENTS.md`, and its reviewed
+  private procedures where applicable. No durable KB is copied into them; legacy
+  roster cutover remains deferred until S7 knowledge publication.
+- Each edition preserves its knowledge owner, owned node and four cross-reads.
   Store `oats` requires the explicit `stores.oats` binding; no publisher writer,
   production store or grants are supplied. An acceptance fixture is parent-owned
   and cannot be counted as production knowledge adoption.
-- Knowledge **oats.okf@2.1.1** and messaging **oats.aweb@1.10.3** are explicit hard
+- Knowledge **oats.okf@2.1.1** and messaging **oats.aweb@1.11.0** are explicit hard
   requirements, not optional defaults. They are published starting revisions,
   **not proof that their combined bindings/runtime profile is ready**. The provider
   owner supplies that evidence and any subsequently reviewed compatible revision.
@@ -69,38 +90,41 @@ introduced by this guide.
 
 At these starting pins, the provider boundary is concrete:
 
-- Published OKF2.1.0 already supports `inherit: stores.oats`, normalized to
+- Published OKF2.1.1 supports `inherit: stores.oats`, normalized to
   `/bindings/knowledge/stores/oats`. The explicit `destination: oats` preserves
   routing; omitting it would instead require `write.default`. No new schema,
   owner or production locator is needed for this declaration.
-- Released aweb1.10.3 (`24efa6f9`) has **no mandatory portable binding interface**,
-  so it currently blocks this pilot's portable preparation. Candidate
-  [aweb PR2](https://github.com/awebai/oats-aweb/pull/2), `165b20e7`, adds codecs;
-  it is not a reviewed/published successor or native lifecycle qualification.
-  Human/native-principal, private-context, admin/grant and admitted-lifecycle
-  requirements remain provider/integration-owner work.
-- Published OKF2.1.0's captured worker profile retains its strict Pi,
-  explicit-model and sole-OKF limitation. Candidate
-  [OKF PR4](https://github.com/awebai/oats-okf/pull/4), `7cff887c`, preserves retained
-  Claude/Codex/null-model intent and the approved helper capability closure;
-  review is pending, not published2.1.0 behavior. Pi plus messaging is still
-  unqualified. Do not silently switch runtimes, force a model, or drop capabilities.
+- aweb 1.10.3 (`24efa6f9`) has no portable binding interface; **aweb 1.11.0**
+  (`v1.11.0`, OATS >=0.24.2) adds it and the five editions now pin it. Its `check`
+  qualifies only an input-capable Claude/Codex primary with an explicit private team
+  and `delivery: session`; strict-Pi print reports `needs-configuration`. Status is on
+  the [program board](design/2026-09-20-redesign-program-board.md). Qualification
+  is HOME-route operational custody only: not human/native-principal delegation,
+  private grants, broker delivery or model consumption.
+- Published OKF2.1.1 accepts retained Claude/Codex helpers with the complete approved
+  capability closure and native-default model intent. Strict Pi still requires an
+  explicit model and the sole-OKF profile; Pi plus messaging remains unqualified.
+  This provider release alone is not combined-profile acceptance. Do not silently
+  switch runtimes, force a model, or drop capabilities.
 
 These are explicit readiness holds, not reasons to weaken the source. Parent must
 select reviewed compatible provider revisions and update the source pin deliberately
 before claiming an operational pilot; metadata-only repository indexes change none
 of these runtime facts.
 
-The workspace intentionally starts with **`imports: []`**. A source cannot pin a
-future commit containing itself. This first commit is publishable source metadata,
-not an already usable/adopted pilot graph or a phase-1 exit verdict.
+Stage one used an empty imports list until source publication. Stage two is now
+committed: all five imports pin **`caa341f34009e37006567419a983d5a743037a79`**, the
+published edition revision containing explicit core requirements and the package.
+The later workspace commit `375b9f42` added those imports. Live source inspection
+against published main resolved all five as `ready-for-preparation`; this is
+metadata readiness, not provider binding, approval, enrollment or a running pilot.
 
-## Publish in this order
+## Preserve source-before-import publication order
 
-1. Review and publish this source/export commit to the framework repository. Save
-   the **actual reviewed immutable source commit** containing the complete soul.
-   Do not put an invented SHA, a mutable branch or an unreviewed local candidate
-   in the workspace import and describe it as the accepted source.
+1. Publish complete, reviewed source editions before pinning them. The current
+   source is `caa341f34009e37006567419a983d5a743037a79`; future revisions must likewise
+   exist before their workspace import update. Never use an invented SHA, a mutable
+   branch or an unreviewed local candidate as the accepted source.
 2. In each of the six repositories, review a root `oats.yaml` against its actual
    source head and actual `oats-package/oats-package.json`. The declaration is:
 
@@ -114,21 +138,25 @@ not an already usable/adopted pilot graph or a phase-1 exit verdict.
    ```
 
    Preserve payloads, versions, old tags and legacy templates. This does not
-   activate oats.dev, messaging or either optional task integration.
-3. In a subsequent reviewed framework commit, replace the empty imports list with
-   an import of the source commit from step 1:
+   activate oats.dev, messaging or either optional task integration. Indexes are
+   published on `main` in all six capability repositories (oats-okf, oats-aweb,
+   oats-authoring, oats-jira, oats-dev, oats-linear); their publication proceeded
+   separately from the framework's own source imports.
+3. A subsequent workspace commit pins the published source, never itself or a
+   future commit. The current first import is:
 
    ```yaml
    imports:
      - source: git:github.com/awebai/oats
        soul: souls/oats-expert
-       revision: <actual-reviewed-published-source-commit>
+       revision: caa341f34009e37006567419a983d5a743037a79
        alias: oats-expert
    ```
 
-   The placeholder is explanatory text, never a value to commit. Update the
-   staged-import test with that real publication evidence at this step. Do not
-   change the stable export path or owner merely because the workspace advances.
+   The [actual workspace](../oats-workspace.yaml) contains all five imports at that
+   same revision; this excerpt is not a replacement for the full list. The layout
+   test now checks stage-two imports and source-document declarations. Do not
+   change stable export paths or owners merely because the workspace advances.
 4. Qualify reciprocal admission at the now-published observations. A missing
    backlink, a fork's copied file or a stale workspace observation is not membership.
    Cross-repository indexes may land separately; until both sides exist, report the
@@ -149,19 +177,18 @@ may consume it without membership in the OATS development workspace.
 
 ## Inspect source metadata before preparation
 
-The public source inspector is implemented in **PR24, commit
-`bc598c484fd097fc5707fd4a33b7877ca00e5da3`**. Use this section only after the
-integration owner supplies a reviewed CLI containing that implementation. It is
-**not a command supported by the original 0.24.0 release**: that older inspect
-route can ignore the request flag and consult ambient classic configuration.
-Do not infer availability from the version floor of a capability.
+The public source inspector ships in [OATS 0.24.1](release-notes/v0.24.1.md),
+following PR24 integration. Use an installed CLI containing that implementation.
+It is **not supported by the original 0.24.0 release**: that older inspect route
+can ignore the request flag and consult ambient classic configuration. Do not
+infer command availability from a capability's version floor or today's catalog.
 
 ```sh
 oats inspect --request /absolute/inspection.json --json
 ```
 
-After the real workspace import from publication step 3 exists, the authored
-inspection input may use the same repository for workspace, member and source:
+With the stage-two imports published, the authored inspection input can use the
+same repository for workspace, member and source:
 
 ```json
 {
@@ -222,7 +249,7 @@ Before preparing, the integration lead must supply:
 - The published workspace/source observations and an explicit fresh physical
   deployment/home placement. Do not copy old locks, retained records or identities.
 - An operator-owned nonsecret request with `workspace` (its source and origin),
-  `source: "oats-expert"` after the real import is published, and `mode: "directory"`.
+  `source: "oats-expert"` (or another published expert alias), and `mode: "directory"`.
   Standalone callers instead give the complete `{source,soul,revision,alias}`
   reference and an explicit standalone context; they do not inherit this workspace.
 - Explicit provider-specific settings and bindings. OKF preparation needs selected
@@ -236,7 +263,7 @@ Before preparing, the integration lead must supply:
   `operator.policy.messaging` selection: capability, matching selected source and
   `settings: {delivery: session}`. Retain host requirements, session `ifInstalled`
   minimums and any selected authoring requirements. Selecting session delivery neither
-  adds the missing1.10.3 binding adapter nor supplies captured wake/input authority.
+  makes a strict-Pi print primary input-capable nor supplies captured wake authority.
 - A qualified primary/helper runtime/model/resource profile. Capture the intended
   helper selection in `helperLaunches["oats.okf:memory-harvest"]`, not the legacy
   `souls.memory-harvest` configuration. Do not replace retained intent to fit an easier
@@ -262,10 +289,12 @@ Do not mix other preparation flags into request-file mode. A needs-configuration
 approval result is not a ready instance. A scaffold materializes resources and may
 run approved hooks; it is not a message exchange or model session. Actual dispatch,
 continuation, native capture, messaging and learning require the integration owner's
-qualified profile and receipts. Captured wake/input and public captured retirement
-remain unsupported; a stopped-home observation is not delivery or retirement authority.
-A session-delivered messaging profile therefore cannot pass on start-only evidence.
-Do not route it through legacy input/retire or remove the messaging requirement.
+qualified profile and receipts. OATS 0.24.1 adds captured custody checks to the
+existing HOME-only session inspect/input route; it does not supply the missing
+messaging adapter or qualify every lifecycle route. Verify wake/input/retirement
+support for the exact route and runtime. A stopped-home observation is not delivery
+or retirement authority, and a messaging profile cannot pass on start-only evidence.
+Do not bypass custody with a legacy fallback or remove the messaging requirement.
 Consult the current installed public help and the provider's supported commands;
 this guide introduces no new CLI grammar. The source inspector above is a separate
 implementation dependency, not a change to the existing prepare request contract.
@@ -282,4 +311,4 @@ indexes are not evidence that the six real repositories are already published.
 Source and metadata checks do not enroll users, initialize the phase-2 store, register
 production writers or qualify private messaging. Parent alone coordinates publication,
 local operator approval and actual adoption. Full Desktop parity follows usable
-infrastructure adoption, not merely seven YAML files passing validation.
+infrastructure adoption, not merely source metadata passing validation.

package/injects/oats-portable.md

@@ -9,6 +9,10 @@ configuration cascade, package lock, similarly named capability, or source path.
 Load **oats-portable** before invoking or reasoning about captured OATS commands.
 Load **oats-portable-artifacts** for exact retained inspection and approval. Do not load the legacy **oats**,
 **oats-config**, or **oats-packages** procedures to fill a captured input.
+If this retained composition includes **oats.core**, its **oats-operate** and
+**oats-souls** skills are capability resources, not implicit kernel additions.
+Use only the resources actually included; a missing capability is not permission
+to fetch or substitute a current version.
 
 Captured start/restart use exact retained launch inputs and supported native
 endpoints. Captured wake/retire, unqualified runtime contributions and non-directory