@awebai/oats 0.69.22 → 0.69.24
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.
- package/bin/oats.mjs +185 -38
- package/docs/capabilities.md +365 -7
- package/docs/capability-manifest.schema.json +37 -1
- package/docs/configuration.md +27 -7
- package/docs/container.md +206 -228
- package/docs/design/2026-11-19-sandboxes.md +1352 -0
- package/docs/design/2026-11-20-provider-home-lifecycle.md +320 -0
- package/docs/design/README.md +7 -0
- package/docs/desktop-cli-api.md +673 -81
- package/docs/desktop.md +241 -65
- package/docs/execution-targets.md +186 -3
- package/docs/first-team.md +11 -0
- package/docs/implementation.md +6 -2
- package/docs/integrations.md +3 -3
- package/docs/knowledge-capability-authoring.md +10 -7
- package/docs/knowledge-reference/acceptance.md +21 -19
- package/docs/knowledge-reference/adoption.md +18 -4
- package/docs/knowledge-reference/model.md +11 -9
- package/docs/knowledge-reference/package-craft.md +2 -2
- package/docs/knowledge-reference/proposal.md +127 -0
- package/docs/knowledge-reference/provider-mapping.md +10 -10
- package/docs/knowledge-reference/reader-capture.md +26 -22
- package/docs/knowledge-theory.md +1 -1
- package/docs/knowledge.md +25 -16
- package/docs/official-catalog.md +4 -4
- package/docs/packages.md +13 -13
- package/docs/release-notes/v0.69.23.md +231 -0
- package/docs/release-notes/v0.69.24.md +264 -0
- package/docs/servers.md +10 -6
- package/docs/souls-and-instances.md +96 -22
- package/docs/tui.md +25 -4
- package/docs/upgrading.md +19 -5
- package/docs/workspaces.md +14 -6
- package/lib/argv.mjs +6 -2
- package/lib/capability-contract.mjs +2 -2
- package/lib/capability-show.mjs +11 -1
- package/lib/command-flags.mjs +40 -3
- package/lib/compile-cache.mjs +1 -1
- package/lib/core.mjs +1201 -195
- package/lib/errors.mjs +4 -1
- package/lib/hook-env.mjs +106 -0
- package/lib/host-run.mjs +11 -3
- package/lib/instance-board.mjs +337 -0
- package/lib/instance-events.mjs +48 -10
- package/lib/instance-inspect.mjs +44 -0
- package/lib/instance-lifecycle.mjs +34 -18
- package/lib/instance-listing.mjs +113 -16
- package/lib/instance-related-work.mjs +143 -0
- package/lib/kernel-features.mjs +13 -1
- package/lib/node-version.mjs +9 -0
- package/lib/provider-call-child.mjs +60 -0
- package/lib/provider-resume.mjs +83 -0
- package/lib/provider-test-seams.mjs +20 -0
- package/lib/read-call.mjs +2 -0
- package/lib/reserved-launch-env.mjs +8 -1
- package/lib/retire-admission.mjs +5 -1
- package/lib/schedule.mjs +14 -4
- package/lib/servers.mjs +151 -17
- package/lib/session-inspect.mjs +104 -13
- package/lib/session-providers.mjs +528 -0
- package/lib/session-resume.mjs +68 -15
- package/lib/stable-node.mjs +3 -0
- package/lib/triggers.mjs +3 -1
- package/package-catalog.json +3 -3
- package/package.json +2 -1
- package/packages/client/capability-list.mjs +21 -0
- package/packages/client/cli-adapter.mjs +19 -4
- package/packages/client/cli-locator.mjs +5 -1
- package/packages/client/deployment-data.mjs +27 -3
- package/packages/client/deployment-panel.mjs +27 -4
- package/packages/client/home-board.mjs +33 -19
- package/packages/client/inspect-boundary.mjs +18 -8
- package/packages/client/instance-acts.mjs +30 -3
- package/packages/client/instance-board.mjs +206 -0
- package/packages/client/instance-presentation.mjs +55 -0
- package/packages/client/instance-tree.mjs +34 -4
- package/packages/client/keymap.mjs +5 -0
- package/packages/client/liveness.mjs +15 -4
- package/packages/client/mail-contract.mjs +130 -0
- package/packages/client/own-codes.mjs +5 -1
- package/packages/client/panel-views.mjs +7 -7
- package/packages/client/related-work.mjs +84 -0
- package/packages/client/remote-roster.mjs +9 -3
- package/packages/client/session-backends.mjs +31 -0
- package/packages/client/session-start.mjs +18 -6
- package/packages/client/spawn-apply-cli.mjs +5 -3
- package/packages/client/spawn-apply-contract.mjs +25 -2
- package/packages/client/spawn-apply.mjs +5 -1
- package/packages/client/spawn-messages.mjs +3 -0
- package/packages/client/terminal-contract.mjs +4 -0
- package/packages/client/waiting-on-you.mjs +12 -2
- package/packages/client/workspace-cli.mjs +13 -2
- package/packages/tui/lib/model.mjs +14 -3
- package/packages/tui/lib/store.mjs +12 -3
- package/skills/oats-getting-started/SKILL.md +11 -8
- package/docs/knowledge-reference/harvester.md +0 -109
- package/lib/instance-same-work.mjs +0 -67
- package/packages/client/same-work.mjs +0 -49
package/docs/knowledge-theory.md
CHANGED
|
@@ -226,7 +226,7 @@ A knowledge capability is more than a storage adapter under a kernel-owned judge
|
|
|
226
226
|
4. A `knowledge-maintainer` instance reviews that pull request and merges, amends, requests changes, closes, or escalates to a human.
|
|
227
227
|
5. Accepted learning becomes available to later consultation; it is not automatically in every instance's active context.
|
|
228
228
|
|
|
229
|
-
|
|
229
|
+
This is the reference doctrine's [judgment and proposal](knowledge-reference/proposal.md) pattern: the instance proposes its own claims, and the maintainer's review of each pull request is where independence lives. An independent harvester, which judges a source's evidence in a separate worker, remains an [option](knowledge-reference/adoption.md#an-option-an-independent-harvester) a capability may choose, with obligations of its own; `oats.okf` 6 replaced it.
|
|
230
230
|
|
|
231
231
|
Directory bases use their own recoverable publication mechanism. Receipts state what actually happened: capture, judgment, delivery and acceptance are different facts, and directory publication does not prove human review. The [operational guide](knowledge.md) describes commands and constraints.
|
|
232
232
|
|
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.
|
|
9
|
+
This is the operator guide for **oats.okf 6.3.0** (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.
|
|
31
|
+
oats.okf: v6.3.0
|
|
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.
|
|
59
|
+
[oats.okf's CHANGELOG](https://github.com/oats-project/oats-okf/blob/v6.3.0/CHANGELOG.md).
|
|
60
60
|
|
|
61
|
-
**Upgrade to 6.0:** pin `oats.okf: v6.
|
|
61
|
+
**Upgrade to 6.0:** pin `oats.okf: v6.3.0` 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.
|
|
70
|
+
(oats.okf's [Upgrading to 6.0](https://github.com/oats-project/oats-okf/blob/v6.3.0/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:
|
|
@@ -231,14 +231,15 @@ other than `off`, or a soul `knowledge.propose` key, refuses the spawn
|
|
|
231
231
|
head of the same PR and each decision made while working are not
|
|
232
232
|
checkpoints: those are captured in `notes/`, and the next checkpoint
|
|
233
233
|
carries them. First update state, log and relevant notes. Apply
|
|
234
|
-
`knowledge-theory` and
|
|
235
|
-
|
|
236
|
-
|
|
237
|
-
|
|
238
|
-
|
|
239
|
-
|
|
240
|
-
for a
|
|
241
|
-
|
|
234
|
+
`knowledge-theory` and run a quick `oats okf search` for each claim: when
|
|
235
|
+
in doubt, propose, because duplicates, the canonical home and the subject
|
|
236
|
+
are the knowledge maintainer's to settle. Make **one proposal per
|
|
237
|
+
checkpoint, carrying only what no earlier proposal carried**, and record
|
|
238
|
+
every checkpoint in `log.md`, either with its proposal's PR URLs or with
|
|
239
|
+
`nothing to propose` and the reason. A claim goes in the owned nodes (or,
|
|
240
|
+
for a version-2 soul, in `claims/` on its subjects); a lesson that belongs
|
|
241
|
+
in a node the soul only reads may be proposed there too, and the check
|
|
242
|
+
flags it for the maintainer, who chooses its home.
|
|
242
243
|
|
|
243
244
|
The instance proposes itself, from its home, in three steps:
|
|
244
245
|
|
|
@@ -259,6 +260,13 @@ other than `off`, or a soul `knowledge.propose` key, refuses the spawn
|
|
|
259
260
|
that would leave the host and prints the complete outgoing diff, the
|
|
260
261
|
commit text, the PR body with its provenance block and a digest; nothing
|
|
261
262
|
remote changes, and the instance reads that diff once as a reviewer would.
|
|
263
|
+
It refuses only what protects against real harm (for example an unsafe
|
|
264
|
+
file, a non-Markdown file where Markdown is required, `okf-base.json`, an
|
|
265
|
+
invalid base or the content screen's findings);
|
|
266
|
+
a path outside the write surface, a claim with no subject, a broken link
|
|
267
|
+
or an unfilled `proposal.md` is a `W_*` warning, listed under
|
|
268
|
+
`## Check warnings` in the PR body, which the maintainer resolves before
|
|
269
|
+
merging.
|
|
262
270
|
`--apply` with that digest commits, pushes a new
|
|
263
271
|
`okf-proposal/<date>-<uuid>` branch (create-only, never the accepted
|
|
264
272
|
branch), labels it `okf-proposal` and opens one PR per changed base. One
|
|
@@ -321,9 +329,10 @@ names but does not judge its content. A bounded content screen runs over
|
|
|
321
329
|
everything that would leave the host before every push, comment and merge,
|
|
322
330
|
and the host's `screen-terms-file` can add terms to it; a clean screen is not
|
|
323
331
|
proof. The proposer reads its outgoing diff before the push; the maintainer,
|
|
324
|
-
the second reader, reads the already-pushed pull request. The
|
|
325
|
-
the provenance checks and the soul's opt-out are enforced in code;
|
|
326
|
-
|
|
332
|
+
the second reader, reads the already-pushed pull request. The refusals of
|
|
333
|
+
`--check`, the provenance checks and the soul's opt-out are enforced in code;
|
|
334
|
+
a path outside the write surface is only a warning the maintainer resolves.
|
|
335
|
+
None is a privacy guarantee. The opt-out ([The soul's opt-out](#the-souls-opt-out)) is
|
|
327
336
|
per soul and covers that soul's own proposals, not what its instances write
|
|
328
337
|
to other seats. A soul whose work is reading third-party correspondence
|
|
329
338
|
should opt out.
|
package/docs/official-catalog.md
CHANGED
|
@@ -9,9 +9,9 @@ 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.
|
|
13
|
-
| `oats.okf` | `v6.
|
|
14
|
-
| `oats.aweb` | `v1.
|
|
12
|
+
| `oats.framework` | `oats-framework/v1.28.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.3.0` | `oats.okf` (knowledge), `oats.okf-harvest`, `oats.okf-maintenance` | `knowledge-harvester`, `knowledge-maintainer` |
|
|
14
|
+
| `oats.aweb` | `v1.47.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` | |
|
|
17
17
|
| `oats.cloning` | `v1.1.0` | `oats.cloning` | `cloner` |
|
|
@@ -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.
|
|
67
|
+
`packages:` map (`oats.okf: v6.3.0`); `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.
|
|
51
|
+
oats.okf: v6.3.0 # 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.
|
|
58
|
+
convention (`v5.8.0` or `oats-framework/v1.28.0`) 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,9 +78,9 @@ members:
|
|
|
78
78
|
- git:github.com/acme/agents
|
|
79
79
|
- git:github.com/acme/platform
|
|
80
80
|
packages:
|
|
81
|
-
oats.framework: v1.
|
|
82
|
-
oats.okf: v6.
|
|
83
|
-
oats.aweb: v1.
|
|
81
|
+
oats.framework: v1.28.0
|
|
82
|
+
oats.okf: v6.3.0
|
|
83
|
+
oats.aweb: v1.47.0
|
|
84
84
|
teams:
|
|
85
85
|
platform: { team: "platform:acme.aweb.ai", description: Platform engineering }
|
|
86
86
|
defaults:
|
|
@@ -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.
|
|
112
|
+
packages acme.tools 0.4.0 ✓ (@ 47f4b816) oats.okf 6.3.0 ✓ (@ 29dfd340)
|
|
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
|
|
@@ -155,7 +155,7 @@ Declaring a package in the workspace's `packages:` is the trust decision
|
|
|
155
155
|
## `oats package add | remove`
|
|
156
156
|
|
|
157
157
|
```bash
|
|
158
|
-
oats package add oats.aweb v1.
|
|
158
|
+
oats package add oats.aweb v1.47.0 # a catalog version
|
|
159
159
|
oats package add acme.tools git:github.com/acme/tools@v0.4.0
|
|
160
160
|
oats package remove acme.tools
|
|
161
161
|
```
|
|
@@ -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.
|
|
185
|
-
"commit": "
|
|
184
|
+
"version": "6.3.0",
|
|
185
|
+
"commit": "29dfd3403d06ec1f14136f81f4dfae63dafcbd9f",
|
|
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.
|
|
435
|
-
"oats.framework": { "url": "https://github.com/awebai/oats.git", "ref": "oats-framework/v1.
|
|
434
|
+
"oats.okf": { "url": "https://github.com/awebai/oats-okf.git", "ref": "v6.3.0", "path": "oats-package" },
|
|
435
|
+
"oats.framework": { "url": "https://github.com/awebai/oats.git", "ref": "oats-framework/v1.28.0", "path": "oats-package" }
|
|
436
436
|
}
|
|
437
437
|
}
|
|
438
438
|
```
|
|
439
439
|
|
|
440
|
-
`ref` carries the tag convention: a workspace's `oats.framework: v1.
|
|
441
|
-
resolves to tag `oats-framework/v1.
|
|
440
|
+
`ref` carries the tag convention: a workspace's `oats.framework: v1.28.0`
|
|
441
|
+
resolves to tag `oats-framework/v1.28.0`. Resolving through the catalog never
|
|
442
442
|
advances a lock by itself: `oats sync` does, and says so.
|
|
@@ -0,0 +1,231 @@
|
|
|
1
|
+
# OATS 0.69.23
|
|
2
|
+
|
|
3
|
+
An agent can keep facts in its person's view and ask them questions with options, on its board
|
|
4
|
+
(`oats instance board`), and oats.core teaches agents to use it. The Desktop reads an agent's own mail, received and
|
|
5
|
+
sent, in a read-only sheet that never marks anything read, through the messaging layer's new `messaging:mail`
|
|
6
|
+
operation (oats.aweb 1.46.0). The sidebar draws lines between related work again, and the kernel's same-work flag becomes the related-work flag, which also binds a sibling (the old spellings stay as aliases). The team image's supervisor runs
|
|
7
|
+
one generic optional child, and the bb image moves to its own repository. The catalog pins oats.framework 1.27.0,
|
|
8
|
+
oats.aweb 1.46.0 and oats.okf 6.3.0.
|
|
9
|
+
|
|
10
|
+
## Upgrade
|
|
11
|
+
|
|
12
|
+
- **Either order of the Desktop and the CLI works** from a Desktop newer than
|
|
13
|
+
0.69.17 ([Either order works](../upgrading.md#either-order-works)).
|
|
14
|
+
- **Package pins:** oats.framework 1.27.0 (from 1.26.0), oats.aweb 1.46.0
|
|
15
|
+
(from 1.45.0) and oats.okf 6.3.0 (from 6.2.0). `oats sync` takes them.
|
|
16
|
+
Respawn instances, or move a stopped one with `oats instance upgrade`, to
|
|
17
|
+
take the new modules: the board teaching (oats.core 2.15.0) and the mail
|
|
18
|
+
read (oats.aweb 1.46.0) reach an agent only through its module copies.
|
|
19
|
+
Until then the Desktop's mail sheet shows `E_OPERATION_UNKNOWN` for that
|
|
20
|
+
agent.
|
|
21
|
+
- **The mail read needs aw 1.36.53 or later**; below it, it answers
|
|
22
|
+
`E_AW_TOO_OLD` (oats.aweb's aw floor is unchanged otherwise).
|
|
23
|
+
- **If you tried the experimental bb image of 0.69.22** (`container/agent-bb`
|
|
24
|
+
with `container/agent/compose.agent.bb.yaml`): rebuild your team image
|
|
25
|
+
from this release's `container/agent`, since the 0.69.22 supervisor does
|
|
26
|
+
not know `AGENT_CHILD`; build the bb image from
|
|
27
|
+
[oats-project/oats-bb](https://github.com/oats-project/oats-bb) on that
|
|
28
|
+
team image; replace `compose.agent.bb.yaml` in your Compose commands by
|
|
29
|
+
that repository's fragment, which sets `AGENT_CHILD: "bb"`; and set no
|
|
30
|
+
`AGENT_BB`. A container that still sets `AGENT_BB` does not start.
|
|
31
|
+
- **The same-work flag is now the related-work flag; the old spellings
|
|
32
|
+
still work.** `oats spawn … --same-work` and `oats instance same-work …`
|
|
33
|
+
are deprecated aliases of `oats spawn … --related-work` and `oats instance
|
|
34
|
+
related-work <instance> on|off`, with the same binding. Each use prints one
|
|
35
|
+
line on stderr (`--same-work is renamed: use --related-work`, `oats
|
|
36
|
+
instance same-work is renamed: use oats instance related-work`); `--json`
|
|
37
|
+
output is unchanged. Instances flagged before the upgrade keep their flag.
|
|
38
|
+
Move skills and scripts to `--related-work` once every host they run
|
|
39
|
+
against is on this release; the aliases stay until their removal is
|
|
40
|
+
decided, with its own release-notes entry.
|
|
41
|
+
|
|
42
|
+
## Added
|
|
43
|
+
|
|
44
|
+
- **An agent's mail in the Desktop.** Alt+M (⌥⌘M on macOS), the palette's **Agent: mail** or **Mail** in Details opens the agent's own mail, received and sent, newest first, in a read-only sheet from the right. Each message shows who it is from or to, its subject and its body as plain text attributed to its sender, and whether it is encrypted, not read by the agent yet, high priority or from an unverified sender. **r** reads it again, **Older mail** reads further back, and Esc closes it ([An agent's mail](../desktop.md#an-agents-mail)).
|
|
45
|
+
|
|
46
|
+
Reading it never acknowledges or marks anything read: the Desktop runs only the messaging layer's `messaging:mail` operation, and only when you open the sheet or ask it to read again. Nothing else on the screen shows an agent's mail. It needs an agent whose messaging layer has the operation; an older one says to upgrade it (`oats instance upgrade`) or start a new agent of its soul.
|
|
47
|
+
|
|
48
|
+
- **The agent's board** (feature `instance-board`, `boardApi: 1`). An agent
|
|
49
|
+
keeps facts in its person's view and asks them questions, from its own
|
|
50
|
+
session:
|
|
51
|
+
- `oats instance board set <key> --label <text> --value <text> [--unit
|
|
52
|
+
<text>] [--link <https-url>]` and `oats instance board unset <key>`. At
|
|
53
|
+
most 12 facts. The kernel keeps each fact's last 20 values. Facts last as
|
|
54
|
+
long as the home.
|
|
55
|
+
- `oats instance board ask <question> --option <text> --option <text>
|
|
56
|
+
[--option <text>]… [--id <id>] [--context-file <f>]` and `oats instance
|
|
57
|
+
board ask --clear <id>`. Each question has 2 to 4 options. At most 9 are
|
|
58
|
+
open, with ids `q1`, `q2`… (never reused) unless `--id` names one. A
|
|
59
|
+
question belongs to the session it was asked in.
|
|
60
|
+
- While a question is open, the kernel holds a needs-input claim of
|
|
61
|
+
producer `oats.board`, reason `attention`, with the oldest question as its
|
|
62
|
+
message. The waiting dot and the waiting row show it as they show any
|
|
63
|
+
claim. It holds no scheduled wake.
|
|
64
|
+
- `board` on `oats status --json` and `oats server roster --json` instance
|
|
65
|
+
rows: the facts and the open questions, at most 8 KiB per row
|
|
66
|
+
(`E_BOARD_FULL` refuses a write past it), or `null` with no board.
|
|
67
|
+
`oats inspect --home <h> --board` adds each fact's history and each
|
|
68
|
+
question's context.
|
|
69
|
+
- The board is the home's `.oats-board.json`. It is kernel-owned: a
|
|
70
|
+
capability can't declare it, and a retire counts it as no work.
|
|
71
|
+
- The kernel routes no answer. A client types the person's answer in the
|
|
72
|
+
agent's terminal as `<id>: <text>`.
|
|
73
|
+
|
|
74
|
+
See [The agent's board](../desktop-cli-api.md#the-agents-board-oats-instance-board).
|
|
75
|
+
|
|
76
|
+
## Changed
|
|
77
|
+
|
|
78
|
+
- **Related work, with a parent or a sibling** (feature
|
|
79
|
+
`instance-related-work`; `instance-same-work` is still advertised beside
|
|
80
|
+
it). The flag binds an instance's recorded parent, as before, and now also
|
|
81
|
+
its recorded sibling when it has no parent. A top-level instance's sibling
|
|
82
|
+
can carry it, so clients can draw a line between two siblings. A sibling
|
|
83
|
+
binding names the sibling the home records: a sibling of a top-level R
|
|
84
|
+
binds R, and a sibling of R's sibling S binds S. `--related-work`, and
|
|
85
|
+
`oats instance related-work <instance> on`, on an instance that records
|
|
86
|
+
neither a parent nor a sibling are refused with `E_BAD_ARGS`, naming why,
|
|
87
|
+
and nothing is spawned or written. The flag reads off after a relink that
|
|
88
|
+
changes the relation (a parent or a sibling retired), until `on` binds it
|
|
89
|
+
again.
|
|
90
|
+
- `oats status --json` rows carry `relatedWork: true`, and `sameWork: true`
|
|
91
|
+
beside it when the flag is bound to the parent (never for a sibling). The
|
|
92
|
+
verb answers `{"instance", "relatedWork", "sameWork"}`. The home file is
|
|
93
|
+
`.oats-related-work.json`, `{"relatedWorkApi": 1, "parent" | "sibling":
|
|
94
|
+
"<instance>", "at": "<ISO time>"}`. An existing `.oats-same-work.json`
|
|
95
|
+
still reads as a parent binding while the new file is absent; the first
|
|
96
|
+
write of the new file removes it, and `off` removes both. Both
|
|
97
|
+
`.oats-related-work` and `.oats-same-work` are kernel-owned home names: a
|
|
98
|
+
capability cannot declare either.
|
|
99
|
+
- **`--server`.** The roster and `oats status --server --json` relay
|
|
100
|
+
`relatedWork: true`, and `sameWork: true` beside it for a parent binding.
|
|
101
|
+
A host on an older OATS, which advertises only `instance-same-work`, is
|
|
102
|
+
sent the old spellings for an instance bound to its parent, and its rows'
|
|
103
|
+
`sameWork: true` reach this machine with `relatedWork: true` beside it. A
|
|
104
|
+
sibling binding is refused there with `E_REMOTE_INCOMPATIBLE`, naming the
|
|
105
|
+
host and the feature it lacks; it is never dropped. See
|
|
106
|
+
[Related work](../desktop-cli-api.md#related-work-oats-instance-related-work).
|
|
107
|
+
- **The team image's supervisor runs one generic optional child, and knows
|
|
108
|
+
no product.** A derived image declares the child in
|
|
109
|
+
`/etc/agent-child.json` (its command, literal and file-read environment,
|
|
110
|
+
readiness URL, loopback ports, version check and stop budget, in a closed
|
|
111
|
+
grammar), and the deployment switches it on from outside the image with
|
|
112
|
+
one fixed Compose entry, `AGENT_CHILD: "<name>"`. Without the switch the
|
|
113
|
+
supervisor reads no file and runs as on the base image. With it, the
|
|
114
|
+
supervisor refuses the start, before any child, on a missing or malformed
|
|
115
|
+
declaration, a declaration that is not root's own regular file, a name
|
|
116
|
+
that differs from the switch, or a command that resolves under a writable
|
|
117
|
+
mount. The child's order, start timeout, restart backoff and process
|
|
118
|
+
group are fixed in the base image; its stop budget is capped at eight
|
|
119
|
+
seconds, so the ordered stop fits the 50-second grace whatever an image
|
|
120
|
+
declares. A file-read variable must hold its value on one line: a file
|
|
121
|
+
with whitespace inside its value refuses the start, and the value reaches
|
|
122
|
+
only the child. Acceptance with `AGENT_CHILD=<name>` exported reads the
|
|
123
|
+
declaration from the running container and checks the file, the declared
|
|
124
|
+
listeners, that nothing but sshd listens beyond loopback, and the declared
|
|
125
|
+
version. Every agent in the container can reach the child's loopback
|
|
126
|
+
ports. See [An optional child](../container.md#an-optional-child).
|
|
127
|
+
|
|
128
|
+
- **OATS pins oats.aweb 1.46.0** (from 1.45.0). It adds the view operation `messaging:mail`: an instance's own mail, read without acknowledging anything, which the Desktop's mail sheet reads (`mailApi: 1`, [Mail](../desktop-cli-api.md#mail-mailapi-1)). Floors are unchanged: OATS >=0.68.0, aw >=1.36.33, tested aw 1.36.58. The mail read alone needs aw >=1.36.53 and answers `E_AW_TOO_OLD` below it. Running instances keep the module they were spawned with: respawn them, or move a stopped one with `oats instance upgrade`, to take 1.46.0. Until then, their mail sheet shows `E_OPERATION_UNKNOWN`.
|
|
129
|
+
|
|
130
|
+
- **Desktop: the sidebar draws its lines again, for related work only.** Where an instance's host
|
|
131
|
+
reports related work, the sidebar draws the lines it drew before its redesign, closed or open,
|
|
132
|
+
and the command palette draws the same lines by the same rule
|
|
133
|
+
([the sidebar's instance tree](../desktop.md#the-sidebars-instance-tree)).
|
|
134
|
+
- **A solid line** joins a parent to a child whose work is related to its parent's. Any other
|
|
135
|
+
child keeps its indent with no line.
|
|
136
|
+
- **A dotted line** joins the dots of two top-level instances of one group when the one linked
|
|
137
|
+
as a sibling of the other reports related work. A top-level instance whose work isn't related
|
|
138
|
+
breaks the dotted line, and the order of the rows doesn't change.
|
|
139
|
+
- **No flag, no line, on every host.** On an older OATS (with `instance-same-work` only), a
|
|
140
|
+
child's line follows `--same-work` and siblings get none. An OATS with neither feature reports
|
|
141
|
+
no related work, so its instances get no line (before, the command palette drew every line
|
|
142
|
+
for it).
|
|
143
|
+
- Both lines hold 3:1 contrast on every row fill, in every theme. A screen reader hears
|
|
144
|
+
"related work" after "under <parent>", and after "sibling of <name>" at both ends of a joined
|
|
145
|
+
pair, in place of the words it heard for a child's flag before.
|
|
146
|
+
|
|
147
|
+
- **oats.framework 1.27.0** (`oats.core` 2.15.0, `oats.knowledge-theory` 1.1.2,
|
|
148
|
+
`oats.setup` 2.16.1). `oats.core`'s inject and `/oats-operate` teach the
|
|
149
|
+
agent's board where the kernel lists `instance-board`, with `attention` as
|
|
150
|
+
the fallback (#2002). The `knowledge-capability-authoring` skill, its copied references
|
|
151
|
+
and the `knowledge-theory-expert` soul teach judgment and proposal at the
|
|
152
|
+
working instance's own checkpoints, with a reviewer accepting every
|
|
153
|
+
proposal. An independent harvester is an option a capability may choose
|
|
154
|
+
(#2009). `oats.setup`'s onboarding and package-pins skills name oats.okf
|
|
155
|
+
v6.3.0 in their examples. Guidance text only: no floor moves, and nothing
|
|
156
|
+
changes for a deployment beyond `oats sync` taking the new tag.
|
|
157
|
+
|
|
158
|
+
- **`oats.core` teaches the agent's board.** Its inject and `/oats-operate`
|
|
159
|
+
say that, where `oats version --json` lists `instance-board`, an agent
|
|
160
|
+
asks a decision between 2 and 4 options on its board (`oats instance board
|
|
161
|
+
ask`, with the summary, context, next step and links in `--context-file`,
|
|
162
|
+
and an option for each choice saying what it does). The answer arrives typed as `<id>: <text>`, and the
|
|
163
|
+
agent closes the question with `oats instance board ask --clear <id>` once
|
|
164
|
+
it has read it. The agent keeps only what its person must keep in view as
|
|
165
|
+
board facts (`oats instance board set`). On an OATS without the board (no
|
|
166
|
+
`instance-board` feature), it uses `oats instance attention`;
|
|
167
|
+
after `E_EVENTS_FAILED` it runs the same board command again.
|
|
168
|
+
See [The agent's board](../desktop-cli-api.md#the-agents-board-oats-instance-board).
|
|
169
|
+
|
|
170
|
+
- **The official catalog pins oats.okf 6.3.0** (from 6.2.0), and OATS's own
|
|
171
|
+
workspace takes it. Knowledge proposals are lighter (oats-project/oats-okf#164):
|
|
172
|
+
`oats okf propose` refuses only what protects against real harm (secrets and
|
|
173
|
+
personal data leaving the host, a base that would be invalid, forged
|
|
174
|
+
provenance, unsafe files, the soul's consent, credentials, one attempt per
|
|
175
|
+
proposal). What the knowledge maintainer judges at review anyway (a claim
|
|
176
|
+
outside the proposer's nodes, a missing subject, a broken link, an unfilled
|
|
177
|
+
`proposal.md`) becomes a `W_*` warning, listed under `## Check warnings` in
|
|
178
|
+
the PR body, which the maintainer resolves before merging. `--slug` and
|
|
179
|
+
`--digest` are optional: `--plan`, then `--apply` (it prints the outgoing
|
|
180
|
+
diff and stops), then `--apply` again publishes exactly what it printed.
|
|
181
|
+
Every 6.2 invocation still works with the same result. **What a deployment
|
|
182
|
+
must change:** nothing; the floor stays OATS >=0.69.2. Running instances
|
|
183
|
+
keep the module they were spawned with: respawn them, or move a stopped one
|
|
184
|
+
with `oats instance upgrade`, to take 6.3.0. The generated mirror under
|
|
185
|
+
`mirrors/oats-okf*` is finalized from the v6.3.0 tag
|
|
186
|
+
([oats.okf's CHANGELOG](https://github.com/oats-project/oats-okf/blob/v6.3.0/CHANGELOG.md)).
|
|
187
|
+
|
|
188
|
+
## Fixed
|
|
189
|
+
|
|
190
|
+
- **Getting started pushes straight to a free plan's private repository.**
|
|
191
|
+
On a private repository whose plan has no rulesets, GitHub answers the
|
|
192
|
+
`oats-getting-started` skill's rules read with a 403 "Upgrade to GitHub
|
|
193
|
+
Pro". Step 7 read that failure as a guarded branch and opened a pull
|
|
194
|
+
request the person then had to merge. It now counts that 403 as no rules,
|
|
195
|
+
as `oats-workspace-config`'s check already does. The skill still opens a
|
|
196
|
+
pull request when others can push, when the branch is protected, when any
|
|
197
|
+
other read fails, or when the push is refused.
|
|
198
|
+
- **Getting started's default workspace name is the repository's.** When a
|
|
199
|
+
project has both a repository and a folder of different names, step 1 now
|
|
200
|
+
proposes the repository's name, and the folder's only when there's no
|
|
201
|
+
repository.
|
|
202
|
+
|
|
203
|
+
## Removed
|
|
204
|
+
|
|
205
|
+
- **`AGENT_BB`, `container/agent-bb`, `container/agent/compose.agent.bb.yaml`
|
|
206
|
+
and the bb relay have left this repository.** They shipped in 0.69.22 as
|
|
207
|
+
experimental, with no compatibility promise in that release's docs and
|
|
208
|
+
notes, and are removed without an alias. The bb image, its Compose
|
|
209
|
+
fragment, the relay and their operator docs now live in
|
|
210
|
+
[oats-project/oats-bb](https://github.com/oats-project/oats-bb), where the
|
|
211
|
+
image declares bb as its optional child and its fragment sets
|
|
212
|
+
`AGENT_CHILD`. A container that still sets `AGENT_BB`, to any value, is
|
|
213
|
+
refused at start with a line that names `AGENT_CHILD`, and acceptance
|
|
214
|
+
refuses it too.
|
|
215
|
+
|
|
216
|
+
## Documentation
|
|
217
|
+
|
|
218
|
+
- **The knowledge-capability authors' guide teaches proposals, not a
|
|
219
|
+
harvester.** The reference model's judgment step is now the working
|
|
220
|
+
instance's own, at its knowledge checkpoints, with a reviewer accepting every
|
|
221
|
+
proposal: [judgment and proposal](../knowledge-reference/proposal.md)
|
|
222
|
+
replaces the harvester page, and the model, reader/capture, provider-mapping,
|
|
223
|
+
acceptance and package-craft pages follow it. An independent harvester stays
|
|
224
|
+
an [option](../knowledge-reference/adoption.md#an-option-an-independent-harvester)
|
|
225
|
+
a capability may choose, with the obligations it then carries. The
|
|
226
|
+
`oats.knowledge-theory` skill `knowledge-capability-authoring`, its copied
|
|
227
|
+
references and the `knowledge-theory-expert` soul change with it; they ship
|
|
228
|
+
with the next `oats.framework` release.
|
|
229
|
+
|
|
230
|
+
- **A view operation may carry one structured field.** Beside its `documents`, a view's result may hold one field named after its operation and versioned by its own `<name>Api`. The kernel validates `documents` only and relays the result unchanged, locally and through `--server`, so a client can rely on the field reaching it as the provider wrote it ([desktop-cli-api.md](../desktop-cli-api.md#oats-operation-run)).
|
|
231
|
+
- **`messaging:mail`, `mailApi: 1`: an agent's own mail, read without acknowledging it.** The messaging layer's answer is described once for every messaging provider: received and sent mail, newest first across the agent's identities, with bounded bodies and answers, paging, partial long conversations, per-identity errors and how older sides answer ([desktop-cli-api.md](../desktop-cli-api.md#mail-mailapi-1)). oats.aweb is its first provider. No kernel change: an older kernel relays it the same way.
|