@awebai/oats 0.69.16 → 0.69.17

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
@@ -40,7 +40,7 @@ arrives from.
40
40
  ```yaml
41
41
  # oats-workspace.yaml: one default per slot, for every soul
42
42
  packages:
43
- oats.okf: v6.0.1
43
+ oats.okf: v6.0.2
44
44
  oats.aweb: v1.39.0
45
45
  oats.linear: v1.0.1
46
46
  oats.jira: v1.0.1
package/docs/knowledge.md CHANGED
@@ -6,7 +6,7 @@ kernel owns slot selection, composition and command dispatch; the capability
6
6
  owns its knowledge format, instructions and promotion procedure. The model is
7
7
  in [Knowledge, instances and evolving expertise](knowledge-theory.md).
8
8
 
9
- This is the operator guide for **oats.okf 6.0.1** (OATS **>=0.69.2**). Provider implementation and
9
+ This is the operator guide for **oats.okf 6.0.2** (OATS **>=0.69.2**). Provider implementation and
10
10
  recovery details belong to the [oats-okf README](https://github.com/awebai/oats-okf).
11
11
  In 6.0 there is no knowledge harvester: a working instance proposes its own
12
12
  knowledge as a pull request at its checkpoints (`oats okf propose`), and the
@@ -28,7 +28,7 @@ knowledge maintainer gates every merge.
28
28
  ```yaml
29
29
  # oats-workspace.yaml (excerpt)
30
30
  packages:
31
- oats.okf: v6.0.1
31
+ oats.okf: v6.0.2
32
32
  defaults:
33
33
  knowledge: { oats.okf: { from: package } }
34
34
  stores:
@@ -56,9 +56,9 @@ Upgrading from 4.x requires the ordered
56
56
  just editing a version line. The package requires OATS >=0.69.2: its
57
57
  `knowledge-maintainer` soul says `background: true`, which an older kernel
58
58
  refuses. Upgrade OATS first, then the package. Each 5.x step is in
59
- [oats.okf's CHANGELOG](https://github.com/oats-project/oats-okf/blob/v6.0.1/CHANGELOG.md).
59
+ [oats.okf's CHANGELOG](https://github.com/oats-project/oats-okf/blob/v6.0.2/CHANGELOG.md).
60
60
 
61
- **Upgrade to 6.0:** pin `oats.okf: v6.0.1` and run `oats sync`. Only new
61
+ **Upgrade to 6.0:** pin `oats.okf: v6.0.2` and run `oats sync`. Only new
62
62
  spawns get `oats okf propose`, the 6.0 `okf-propose` skill and the
63
63
  spawn-recorded duty. Existing homes keep their copied provider even after a
64
64
  session restart; a stopped 5.x home can move with `oats instance upgrade`
@@ -67,7 +67,7 @@ remedy to retire and respawn it. Harvester spawns stop: the stub soul
67
67
  `oats.okf/knowledge-harvester`, kept until 7.0, refuses every spawn with
68
68
  `E_REMOVED` and the fix. Harvesters already running keep their 5.x modules
69
69
  and finish, or a person retires them. Then, by hand, from the deployment
70
- (oats.okf's [Upgrading to 6.0](https://github.com/oats-project/oats-okf/blob/v6.0.1/README.md#upgrading-to-60)
70
+ (oats.okf's [Upgrading to 6.0](https://github.com/oats-project/oats-okf/blob/v6.0.2/README.md#upgrading-to-60)
71
71
  has each step's commands):
72
72
 
73
73
  1. Delete the harvester's launch preference, if any:
@@ -9,8 +9,8 @@ or workspace membership alone does not make a package official.
9
9
 
10
10
  | package | release | capabilities | package souls |
11
11
  |---|---|---|---|
12
- | `oats.framework` | `oats-framework/v1.24.0` (this repository) | `oats.core`, `oats.setup`, `oats.onboarding`, `oats.support`, `oats.knowledge-theory`, `oats.coordination-setup` | `knowledge-theory-expert`, `oats-setup-expert` |
13
- | `oats.okf` | `v6.0.1` | `oats.okf` (knowledge), `oats.okf-harvest`, `oats.okf-maintenance` | `knowledge-harvester`, `knowledge-maintainer` |
12
+ | `oats.framework` | `oats-framework/v1.24.1` (this repository) | `oats.core`, `oats.setup`, `oats.onboarding`, `oats.support`, `oats.knowledge-theory`, `oats.coordination-setup` | `knowledge-theory-expert`, `oats-setup-expert` |
13
+ | `oats.okf` | `v6.0.2` | `oats.okf` (knowledge), `oats.okf-harvest`, `oats.okf-maintenance` | `knowledge-harvester`, `knowledge-maintainer` |
14
14
  | `oats.aweb` | `v1.39.0` | `oats.aweb` (messaging), `oats.aweb-tasks` (tasks) | |
15
15
  | `oats.engineering` | `v1.18.0` (frozen: see Coordination templates) | `oats.engineering-expert`, `oats.developer`, `oats.code-review`, `oats.maintainer` | `code-reviewer` |
16
16
  | `oats.authoring` | `v1.0.3` | `oats.authoring` | |
@@ -64,7 +64,7 @@ aliases, a later decision once no workspace we know of pins it.
64
64
  ## Find and use packages
65
65
 
66
66
  - A workspace pins an official package by **bare version** in its
67
- `packages:` map (`oats.okf: v6.0.1`); `oats sync` resolves it through the
67
+ `packages:` map (`oats.okf: v6.0.2`); `oats sync` resolves it through the
68
68
  catalog to an exact commit, fetches it, verifies its integrity and locks it.
69
69
  A package outside the catalog is written `git:<repo>@<ref>`. Pinning does
70
70
  not join a team or adopt the publisher's workspace. See
package/docs/packages.md CHANGED
@@ -48,14 +48,14 @@ whole organisation:
48
48
 
49
49
  ```yaml
50
50
  packages:
51
- oats.okf: v6.0.1 # bare version → the official catalog
51
+ oats.okf: v6.0.2 # bare version → the official catalog
52
52
  acme.tools: git:github.com/acme/tools@v0.4.0 # direct ref: git:<repo>@<tag or full OID>
53
53
  ```
54
54
 
55
55
  - **Bare version** (`v5.8.0`, `5.8.0`, `1.0.0-rc.1`): the id is looked up in
56
56
  the official catalog — `package-catalog.json` in the `oats` repo, or the file
57
57
  named by `OATS_PACKAGE_CATALOG` — which supplies the repo url, the tag
58
- convention (`v5.8.0` or `oats-framework/v1.24.0`) and the payload path. An id
58
+ convention (`v5.8.0` or `oats-framework/v1.24.1`) and the payload path. An id
59
59
  the catalog does not know is `E_PACKAGE_MISSING` ("use `git:<repo>@<ref>` for
60
60
  a package outside the catalog"). The catalog is the reviewed official list
61
61
  ([official-catalog.md](official-catalog.md)) and the only way a
@@ -78,8 +78,8 @@ members:
78
78
  - git:github.com/acme/agents
79
79
  - git:github.com/acme/platform
80
80
  packages:
81
- oats.framework: v1.24.0
82
- oats.okf: v6.0.1
81
+ oats.framework: v1.24.1
82
+ oats.okf: v6.0.2
83
83
  oats.aweb: v1.39.0
84
84
  teams:
85
85
  platform: { team: "platform:acme.aweb.ai", description: Platform engineering }
@@ -109,7 +109,7 @@ decision recorded in the lock.
109
109
  $ oats sync
110
110
  workspace acme (github.com/acme/agents @ 3f2a9c1e)
111
111
  members agents ✓↔ (@ 3f2a9c1e) platform ✓↔ (@ 77c0a1b2) billing ✗ (no-backlink)
112
- packages acme.tools 0.4.0 ✓ (@ 47f4b816) oats.okf 6.0.1 ✓ (@ 95449a66)
112
+ packages acme.tools 0.4.0 ✓ (@ 47f4b816) oats.okf 6.0.2 ✓ (@ 5c3f684c)
113
113
  changed acme.tools — → 0.4.0 (@ 47f4b816)
114
114
  souls 9 discovered (6 members, 1 external, 2 package, 0 disabled here) · 0 private capabilities
115
115
  teams platform (shared) · this deployment's: oats teams
@@ -181,8 +181,8 @@ same workspace commit hold identical locks.
181
181
  "source": "catalog:oats.okf",
182
182
  "url": "https://github.com/awebai/oats-okf.git",
183
183
  "path": "oats-package",
184
- "version": "6.0.1",
185
- "commit": "95449a665146f36fbaecddeea413c9421d109912",
184
+ "version": "6.0.2",
185
+ "commit": "5c3f684c35b2ea9eeec5cdca915b6d845273fb4d",
186
186
  "integrity": "sha256-…",
187
187
  "capabilities": ["oats.okf", "oats.okf-harvest", "oats.okf-maintenance"]
188
188
  },
@@ -431,12 +431,12 @@ A soul that names one of the package's capabilities with
431
431
  {
432
432
  "policy": "docs/official-catalog.md",
433
433
  "packages": {
434
- "oats.okf": { "url": "https://github.com/awebai/oats-okf.git", "ref": "v6.0.1", "path": "oats-package" },
435
- "oats.framework": { "url": "https://github.com/awebai/oats.git", "ref": "oats-framework/v1.24.0", "path": "oats-package" }
434
+ "oats.okf": { "url": "https://github.com/awebai/oats-okf.git", "ref": "v6.0.2", "path": "oats-package" },
435
+ "oats.framework": { "url": "https://github.com/awebai/oats.git", "ref": "oats-framework/v1.24.1", "path": "oats-package" }
436
436
  }
437
437
  }
438
438
  ```
439
439
 
440
- `ref` carries the tag convention: a workspace's `oats.framework: v1.24.0`
441
- resolves to tag `oats-framework/v1.24.0`. Resolving through the catalog never
440
+ `ref` carries the tag convention: a workspace's `oats.framework: v1.24.1`
441
+ resolves to tag `oats-framework/v1.24.1`. Resolving through the catalog never
442
442
  advances a lock by itself: `oats sync` does, and says so.
@@ -0,0 +1,49 @@
1
+ # OATS 0.69.17
2
+
3
+ 0.69.17 moves OATS's two coordination souls, `oats-engineering-expert` and
4
+ `oats-product-expert`, onto knowledge subjects (`okf.json` version 2). The
5
+ official catalog pins oats.okf 6.0.2 and oats.framework 1.24.1; oats.aweb
6
+ stays at 1.39.0.
7
+
8
+ ## Upgrade
9
+
10
+ - **Either order of the Desktop and the CLI works.**
11
+ [Upgrading](../upgrading.md) installs the Desktop first, and a host that
12
+ installed the CLI first is fine too: the 0.69.17 Desktop accepts OATS CLIs
13
+ `>=0.26.0 <0.70.0`, as the 0.69.16 Desktop does.
14
+ - **Package pins:** oats.okf 6.0.2 (from 6.0.1) and oats.framework 1.24.1
15
+ (from 1.24.0). Neither asks for a hand step: `oats sync` takes them. A
16
+ deployment that keeps its own pins changes nothing until it moves them.
17
+ - **Respawn an instance of `oats-engineering-expert` or `oats-product-expert`
18
+ once** after `oats sync`. An instance keeps the `okf.json` its spawn
19
+ recorded, so one started before this release still reads and proposes to
20
+ its old node; a new spawn reads the soul's subjects. The soul needs a
21
+ knowledge base bound with the subject layout: on a base that is not
22
+ bridged, its spawn refuses with `E_CONFIG` naming the base
23
+ ([okf.json version 2](../knowledge.md#the-souls-okfjson)).
24
+
25
+ ## Changed
26
+
27
+ - **`oats.framework` 1.24.1: `oats.setup` 2.15.1's `/oats-onboarding` names
28
+ `oats.okf` 6.0.2**, the release the catalog pins, in its knowledge card and
29
+ its workspace example. Nothing else changes, and no capability needs a
30
+ newer OATS.
31
+
32
+ - **The official catalog pins oats.okf 6.0.2** (from 6.0.1), and OATS's own
33
+ workspace takes it. A claim merged into a bridged base without the
34
+ maintainer's id stamp no longer stops version-2 spawns: readers warn
35
+ `W_ID_MISSING`, `oats okf bases` shows it, and writers and strict checks
36
+ still refuse. The generated mirror under `mirrors/oats-okf*` is finalized
37
+ from the v6.0.2 tag
38
+ ([oats.okf's CHANGELOG](https://github.com/oats-project/oats-okf/blob/v6.0.2/CHANGELOG.md)).
39
+
40
+ - **`oats-engineering-expert` and `oats-product-expert` read by subject**
41
+ (`okf.json` version 2). The engineering expert's subjects are
42
+ `system/oats-kernel`, `system/oats-desktop`,
43
+ `workstream/provider-integration`, `workstream/operations` and
44
+ `workstream/coordination`; the product expert's are
45
+ `workstream/oats-direction` and `workstream/positioning`. Their spawn brief
46
+ lists those subjects, and their texts say each proposed claim names the
47
+ subjects it is about. Every other soul keeps its version-1 `okf.json`.
48
+ - **`oats.workspace-experts` 1.3.1:** its table of surfaces names, beside each
49
+ knowledge node, the subject that absorbs it ("Knowledge it reads").
package/docs/upgrading.md CHANGED
@@ -6,11 +6,11 @@ host that comes from it.
6
6
 
7
7
  ## Upgrading to the latest version
8
8
 
9
- The latest version is **OATS 0.69.16** ([release notes](release-notes/v0.69.16.md)).
10
- The 0.69.16 Desktop accepts OATS CLIs `>=0.26.0 <0.70.0`.
9
+ The latest version is **OATS 0.69.17** ([release notes](release-notes/v0.69.17.md)).
10
+ The 0.69.17 Desktop accepts OATS CLIs `>=0.26.0 <0.70.0`.
11
11
 
12
12
  **First, read the `## Upgrade` section of every release after yours, up to
13
- 0.69.16,** in the [release notes](release-notes/): it says what to do before
13
+ 0.69.17,** in the [release notes](release-notes/): it says what to do before
14
14
  the CLI changes, and what else must change with it (the Desktop, another
15
15
  tool, a package pin). [Coming from an older version](#coming-from-an-older-version)
16
16
  names the releases that ask for more than the steps below. `oats version`
@@ -19,8 +19,8 @@ prints the version you have.
19
19
  Then, on each host:
20
20
 
21
21
  ```sh
22
- # 0. where the Desktop is installed: Desktop 0.69.16 first
23
- npm install -g @awebai/oats@0.69.16 # 1. the CLI
22
+ # 0. where the Desktop is installed: Desktop 0.69.17 first
23
+ npm install -g @awebai/oats@0.69.17 # 1. the CLI
24
24
  oats update # 2. in each deployment: the plan, then it asks before it runs
25
25
  oats doctor # 3. in the same deployment
26
26
  ```
@@ -204,11 +204,16 @@ of the Desktop and the CLI, and an optional package pin. A change a script
204
204
  must follow is in its release's Upgrade section whether or not it is listed
205
205
  here.
206
206
 
207
+ - **[0.69.17](release-notes/v0.69.17.md#upgrade):** the catalog pins
208
+ oats.okf 6.0.2 and oats.framework 1.24.1; respawn each running
209
+ `oats-engineering-expert` and `oats-product-expert` once after `oats sync`,
210
+ on a knowledge base with the subject layout.
207
211
  - **[0.69.16](release-notes/v0.69.16.md#upgrade):** the catalog pins
208
212
  oats.okf 6.0.1, oats.aweb 1.39.0 and oats.framework 1.24.0. A deployment
209
213
  that takes oats.okf 6 removes the harvester's launch preference and spawn
210
- flags, adds the `proposal-review` trigger beside `harvest-review`, and
211
- retires its harvesters; aw 1.36.56 is the tested aw; pi homes keep
214
+ flags, adds the `proposal-review` trigger beside `harvest-review`, protects
215
+ each Git base's accepted branch and gives proposing hosts branch-create
216
+ access, and retires its harvesters; aw 1.36.56 is the tested aw; pi homes keep
212
217
  @awebai/claude-skills out of their pi folder; the team agent image is
213
218
  rebuilt.
214
219
  - **[0.69.15](release-notes/v0.69.15.md#upgrade):** Node 22.5.0 or later
@@ -54,8 +54,8 @@ members: # repo refs, NO @revision (E_WORKSPAC
54
54
  - git:github.com/acme/tools # a member that ALSO publishes a package (see below)
55
55
 
56
56
  packages: # the ONLY versioned things
57
- oats.framework: v1.24.0 # bare version → resolves through the official catalog
58
- oats.okf: v6.0.1
57
+ oats.framework: v1.24.1 # bare version → resolves through the official catalog
58
+ oats.okf: v6.0.2
59
59
  acme.tools: git:github.com/acme/tools@v0.4.0 # outside the catalog → git:<repo>@<tag|OID>; still a package
60
60
 
61
61
  teams: # SHARED teams: the same provider team for everyone
@@ -3,7 +3,7 @@
3
3
  "packages": {
4
4
  "oats.okf": {
5
5
  "url": "https://github.com/awebai/oats-okf.git",
6
- "ref": "v6.0.1",
6
+ "ref": "v6.0.2",
7
7
  "path": "oats-package"
8
8
  },
9
9
  "oats.aweb": {
@@ -48,7 +48,7 @@
48
48
  },
49
49
  "oats.framework": {
50
50
  "url": "https://github.com/awebai/oats.git",
51
- "ref": "oats-framework/v1.24.0",
51
+ "ref": "oats-framework/v1.24.1",
52
52
  "path": "oats-package"
53
53
  }
54
54
  },
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@awebai/oats",
3
- "version": "0.69.16",
3
+ "version": "0.69.17",
4
4
  "description": "OATS (Open Agent Team Specification) — durable souls, disposable instances, targetable capability packages, and the runtime-neutral oats CLI/kernel.",
5
5
  "keywords": [
6
6
  "agents",
@@ -533,7 +533,7 @@ installed CLI's catalog:
533
533
  node -e 'const c=require(process.argv[1]);console.log(c.packages["oats.framework"].ref,c.packages["oats.aweb"].ref)' "$(oats root)/package-catalog.json"
534
534
  ```
535
535
 
536
- It prints the two refs, for example `oats-framework/v1.24.0 v1.39.0`. If the
536
+ It prints the two refs, for example `oats-framework/v1.24.1 v1.39.0`. If the
537
537
  framework's version (after the `/`) is below `1.19.0`, or with aweb
538
538
  `oats.aweb`'s is below `v1.33.1`, this OATS release is older than this
539
539
  skill: stop, and tell the person to wait for the next OATS
@@ -768,7 +768,7 @@ name: acme
768
768
  members:
769
769
  - git:github.com/acme/acme-oats # the host; the setup expert adds the others
770
770
  packages:
771
- oats.framework: v1.24.0 # the installed CLI's catalog versions (below)
771
+ oats.framework: v1.24.1 # the installed CLI's catalog versions (below)
772
772
  oats.aweb: v1.39.0 # messaging: agent identities, mail and chat
773
773
  oats.machine: v0.1.1 # on a machine found-list only: the machine's steward
774
774
  defaults: