Skip to content

HarnessRouter Community Edition: the self-hosted, Apache-2.0 edition of the unified interface for agent harnesses. Run Codex, Claude Code, Hermes, PI, DSH, and more through one API, with sessions, streaming, files, cancellation, and failure handling. Implements the Unified Harness Protocol (UHP), an open standard. Your keys, your infrastructure.

UHP 2026-10-04: a person and an agent are the same kind, and access has one mechanism (#391)

github-actions[bot]cd0c104437ae
diff --git a/protocol/CHANGELOG.md b/protocol/CHANGELOG.md
index 23cf9283..8640df89 100644
--- a/protocol/CHANGELOG.md
+++ b/protocol/CHANGELOG.md
@@ -48,6 +48,16 @@ by the `provider`, with `consolidation_id` beside it, and a record derived from
carries `on_behalf_of`. A credential is not a kind. Schema: `MemoryWriter`, and a pattern on a
grant's `principal`. Suite `2026.10.4.post4`: ME-02 checks the writer's kind.
+**Fifth patch of 2026-10-04, same version.** A person and an agent are the same kind, and access
+has one mechanism. The fourth patch listed `member` (a person) and `harness` (an agent) as two
+kinds; they are one, `member`, and which of the two a member is, is its `type` (`human`, `agent`),
+a property no rule depends on. With that, a harness no longer carries a list of attached memories
+with an `access` that narrowed a grant: an agent reaches what it was granted, on the memory, as a
+person does. `/v1/harnesses/{id}/memories` reads the agent's principal and what it was granted, and
+sets two things: `default_memory_id` and `observe`. An agent joins a group only when someone adds
+it. Kinds are now `member`, `group` and, for a writer only, `provider`. Schema: `HarnessMemories`
+reshaped, `HarnessMemorySettings` added, `HarnessMemoryEntry` removed. Suite `2026.10.4.post5`.
+
- **Memories** ([Memories](versions/2026-10-04/memories.md)), the Harness Memories sub-protocol,
optional at every class behind the `memories` capability. A memory is a named node in a tree:
it holds records and may have child memories. A grant gives a principal privileges (`read`,
diff --git a/protocol/conformance/pyproject.toml b/protocol/conformance/pyproject.toml
index 43654868..075dcd22 100644
--- a/protocol/conformance/pyproject.toml
+++ b/protocol/conformance/pyproject.toml
@@ -1,6 +1,6 @@
[project]
name = "uhp-conformance"
-version = "2026.10.4.post4"
+version = "2026.10.4.post5"
description = "Conformance suite for the Unified Harness Protocol (UHP)"
readme = "README.md"
requires-python = ">=3.10"
diff --git a/protocol/conformance/uhp_conformance/checks.py b/protocol/conformance/uhp_conformance/checks.py
index 55f3de72..456ef5e4 100644
--- a/protocol/conformance/uhp_conformance/checks.py
+++ b/protocol/conformance/uhp_conformance/checks.py
@@ -2058,8 +2058,9 @@ def me02(ctx):
got = ctx.client.get(f"/v1/memories/{rec['memory_id']}/records/{rec['id']}").json or {}
assert got.get("id") == rec["id"] and got.get("content") == rec["content"], "the record does not read back by its id"
w = rec.get("written_by") or {}
- assert w.get("kind") in ("member", "harness") or str(w.get("kind") or "").startswith("x."), (
- f"a stated record's writer is a member, a harness or an x.-prefixed kind of the server's own; got {w.get('kind')!r}")
+ assert w.get("kind") == "member" or str(w.get("kind") or "").startswith("x."), (
+ f"a stated record's writer is a member (a person or an agent) or an x.-prefixed kind of the server's own; got {w.get('kind')!r}")
+ assert w.get("type") in (None, "human", "agent"), f"a member's type is human or agent; got {w.get('type')!r}"
assert w.get("id"), "written_by carries the id of who wrote the record"
return f"{rec['id']} written by {rec.get('written_by')}"
diff --git a/protocol/conformance/uhp_conformance/uhp-2026-10-04.schema.json b/protocol/conformance/uhp_conformance/uhp-2026-10-04.schema.json
index 32cf7b92..d47ffa23 100644
--- a/protocol/conformance/uhp_conformance/uhp-2026-10-04.schema.json
+++ b/protocol/conformance/uhp_conformance/uhp-2026-10-04.schema.json
@@ -2182,8 +2182,8 @@
},
"principal": {
"type": "string",
- "pattern": "^(member|harness|group|x\\.[a-z0-9_.-]+):.+",
- "description": "Who holds the grant, `<kind>:<id>`: `member`, `harness`, `group`, or a kind of the server's own, `x.`-prefixed."
+ "pattern": "^(member|group|x\\.[a-z0-9_.-]+):.+",
+ "description": "Who holds the grant, `<kind>:<id>`: a `member` (a person or an agent), a `group`, or a kind of the server's own, `x.`-prefixed."
},
"privileges": {
"type": "array",
@@ -2583,11 +2583,19 @@
"properties": {
"kind": {
"type": "string",
- "pattern": "^(member|harness|provider|x\\.[a-z0-9_.-]+)$"
+ "pattern": "^(member|provider|x\\.[a-z0-9_.-]+)$"
},
"id": {
"type": "string"
},
+ "type": {
+ "type": "string",
+ "enum": [
+ "human",
+ "agent"
+ ],
+ "description": "For a member: a person or an agent. No rule depends on it."
+ },
"on_behalf_of": {
"type": "string",
"description": "When the provider wrote it: the principal whose observation it was derived from."
@@ -3135,41 +3143,79 @@
}
}
},
- "HarnessMemoryEntry": {
+ "HarnessMemorySettings": {
"type": "object",
- "required": [
- "memory_id"
- ],
"properties": {
- "memory_id": {
- "type": "string"
- },
- "access": {
- "type": "string",
- "enum": [
- "read",
- "write"
- ]
+ "default_memory_id": {
+ "type": [
+ "string",
+ "null"
+ ],
+ "description": "Where an unaddressed remember goes and where turns are recorded. A memory the agent may write."
},
- "default": {
+ "observe": {
"type": "boolean",
- "description": "Where observe and an unaddressed remember go: one entry at most, and one the agent writes."
+ "description": "Record each finished turn in the default memory. On by default."
}
}
},
"HarnessMemories": {
"type": "object",
+ "required": [
+ "principal",
+ "data"
+ ],
"properties": {
- "memories": {
- "type": "array",
- "items": {
- "$ref": "#/$defs/HarnessMemoryEntry"
- }
+ "object": {
+ "type": "string",
+ "const": "harness.memories"
+ },
+ "principal": {
+ "type": "string",
+ "description": "Who this harness's agent is to the access model, `member:<id>`. A grant names it."
+ },
+ "default_memory_id": {
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "observe": {
+ "type": "boolean"
},
"data": {
"type": "array",
+ "description": "Every memory the agent holds a grant on, highest in the tree first. Read off the grants.",
"items": {
- "$ref": "#/$defs/HarnessMemoryEntry"
+ "type": "object",
+ "required": [
+ "id",
+ "privileges"
+ ],
+ "properties": {
+ "id": {
+ "type": "string"
+ },
+ "name": {
+ "type": "string"
+ },
+ "privileges": {
+ "type": "array",
+ "items": {
+ "type": "string",
+ "enum": [
+ "read",
+ "write",
+ "create",
+ "delete"
+ ]
+ }
+ },
+ "default": {
+ "type": "boolean"
+ }
+ },
+ "additionalProperties": true
}
}
}
diff --git a/protocol/schema/uhp-2026-10-04.openapi.yaml b/protocol/schema/uhp-2026-10-04.openapi.yaml
index 151672f9..592a81eb 100644
--- a/protocol/schema/uhp-2026-10-04.openapi.yaml
+++ b/protocol/schema/uhp-2026-10-04.openapi.yaml
@@ -1167,7 +1167,7 @@ paths:
get:
tags: [Memories]
operationId: listHarnessMemories
- summary: "The memories a harness is attached to"
+ summary: "What a harness's agent was granted, and the harness's two memory settings"
description: "Capability `memories`."
responses:
'200':
@@ -1178,14 +1178,14 @@ paths:
'404': { $ref: '#/components/responses/NotFound' }
put:
tags: [Memories]
- operationId: attachHarnessMemories
- summary: "Attach memories to a harness"
- description: "Attaching is granting. An entry the harness does not hold is granted when the caller may change the grants of that memory, and refused otherwise. An empty list detaches."
+ operationId: setHarnessMemories
+ summary: "Set where the agent writes by default and whether its turns are recorded"
+ description: "Access is not set here: an agent is a member and is granted on the memory."
requestBody:
required: true
content:
application/json:
- schema: { $ref: '#/components/schemas/HarnessMemories' }
+ schema: { $ref: '#/components/schemas/HarnessMemorySettings' }
responses:
'200':
description: OK
@@ -2694,7 +2694,7 @@ components:
id: { type: string }
object: { type: string, const: memory.grant }
memory_id: { type: string }
- principal: { type: string, pattern: '^(member|harness|group|x\.[a-z0-9_.-]+):.+', description: 'Who holds the grant, `<kind>:<id>`: `member`, `harness`, `group`, or a kind of the server''s own, `x.`-prefixed.' }
+ principal: { type: string, pattern: '^(member|group|x\.[a-z0-9_.-]+):.+', description: 'Who holds the grant, `<kind>:<id>`: a `member` (a person or an agent), a `group`, or a kind of the server''s own, `x.`-prefixed.' }
privileges: { type: array, items: { $ref: '#/components/schemas/MemoryPrivilege' } }
inherited: { type: boolean, description: True when the grant sits on an ancestor. }
MemoryGrantCreate:
@@ -2809,8 +2809,9 @@ components:
description: 'Who wrote a record, stamped by the server from the authenticated caller. `kind` and `id` joined by a colon are the principal a grant would name.'
required: [kind, id]
properties:
- kind: { type: string, pattern: '^(member|harness|provider|x\.[a-z0-9_.-]+)$' }
+ kind: { type: string, pattern: '^(member|provider|x\.[a-z0-9_.-]+)$' }
id: { type: string }
+ type: { type: string, enum: [human, agent], description: 'For a member: a person or an agent. No rule depends on it.' }
on_behalf_of: { type: string, description: 'When the provider wrote it: the principal whose observation it was derived from.' }
consolidation_id: { type: string, description: 'When the provider wrote it: the consolidation run that concluded it.' }
additionalProperties: true
@@ -2991,15 +2992,28 @@ components:
type: object
properties:
data: { type: array, items: { $ref: '#/components/schemas/MemoryType' } }
- HarnessMemoryEntry:
+ HarnessMemorySettings:
type: object
- required: [memory_id]
properties:
- memory_id: { type: string }
- access: { type: string, enum: [read, write] }
- default: { type: boolean, description: 'Where observe and an unaddressed remember go: one entry at most, and one the agent writes.' }
+ default_memory_id: { type: [string, 'null'], description: 'Where an unaddressed remember goes and where turns are recorded. A memory the agent may write.' }
+ observe: { type: boolean, description: 'Record each finished turn in the default memory. On by default.' }
HarnessMemories:
type: object
+ required: [principal, data]
properties:
- memories: { type: array, items: { $ref: '#/components/schemas/HarnessMemoryEntry' } }
- data: { type: array, items: { $ref: '#/components/schemas/HarnessMemoryEntry' } }
+ object: { type: string, const: harness.memories }
+ principal: { type: string, description: 'Who this harness''s agent is to the access model, `member:<id>`. A grant names it.' }
+ default_memory_id: { type: [string, 'null'] }
+ observe: { type: boolean }
+ data:
+ type: array
+ description: Every memory the agent holds a grant on, highest in the tree first. Read off the grants.
+ items:
+ type: object
+ required: [id, privileges]
+ properties:
+ id: { type: string }
+ name: { type: string }
+ privileges: { type: array, items: { type: string, enum: [read, write, create, delete] } }
+ default: { type: boolean }
+ additionalProperties: true
diff --git a/protocol/schema/uhp-2026-10-04.schema.json b/protocol/schema/uhp-2026-10-04.schema.json
index 32cf7b92..d47ffa23 100644
--- a/protocol/schema/uhp-2026-10-04.schema.json
+++ b/protocol/schema/uhp-2026-10-04.schema.json
@@ -2182,8 +2182,8 @@
},
"principal": {
"type": "string",
- "pattern": "^(member|harness|group|x\\.[a-z0-9_.-]+):.+",
- "description": "Who holds the grant, `<kind>:<id>`: `member`, `harness`, `group`, or a kind of the server's own, `x.`-prefixed."
+ "pattern": "^(member|group|x\\.[a-z0-9_.-]+):.+",
+ "description": "Who holds the grant, `<kind>:<id>`: a `member` (a person or an agent), a `group`, or a kind of the server's own, `x.`-prefixed."
},
"privileges": {
"type": "array",
@@ -2583,11 +2583,19 @@
"properties": {
"kind": {
"type": "string",
- "pattern": "^(member|harness|provider|x\\.[a-z0-9_.-]+)$"
+ "pattern": "^(member|provider|x\\.[a-z0-9_.-]+)$"
},
"id": {
"type": "string"
},
+ "type": {
+ "type": "string",
+ "enum": [
+ "human",
+ "agent"
+ ],
+ "description": "For a member: a person or an agent. No rule depends on it."
+ },
"on_behalf_of": {
"type": "string",
"description": "When the provider wrote it: the principal whose observation it was derived from."
@@ -3135,41 +3143,79 @@
}
}
},
- "HarnessMemoryEntry": {
+ "HarnessMemorySettings": {
"type": "object",
- "required": [
- "memory_id"
- ],
"properties": {
- "memory_id": {
- "type": "string"
- },
- "access": {
- "type": "string",
- "enum": [
- "read",
- "write"
- ]
+ "default_memory_id": {
+ "type": [
+ "string",
+ "null"
+ ],
+ "description": "Where an unaddressed remember goes and where turns are recorded. A memory the agent may write."
},
- "default": {
+ "observe": {
"type": "boolean",
- "description": "Where observe and an unaddressed remember go: one entry at most, and one the agent writes."
+ "description": "Record each finished turn in the default memory. On by default."
}
}
},
"HarnessMemories": {
"type": "object",
+ "required": [
+ "principal",
+ "data"
+ ],
"properties": {
- "memories": {
- "type": "array",
- "items": {
- "$ref": "#/$defs/HarnessMemoryEntry"
- }
+ "object": {
+ "type": "string",
+ "const": "harness.memories"
+ },
+ "principal": {
+ "type": "string",
+ "description": "Who this harness's agent is to the access model, `member:<id>`. A grant names it."
+ },
+ "default_memory_id": {
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "observe": {
+ "type": "boolean"
},
"data": {
"type": "array",
+ "description": "Every memory the agent holds a grant on, highest in the tree first. Read off the grants.",
"items": {
- "$ref": "#/$defs/HarnessMemoryEntry"
+ "type": "object",
+ "required": [
+ "id",
+ "privileges"
+ ],
+ "properties": {
+ "id": {
+ "type": "string"
+ },
+ "name": {
+ "type": "string"
+ },
+ "privileges": {
+ "type": "array",
+ "items": {
+ "type": "string",
+ "enum": [
+ "read",
+ "write",
+ "create",
+ "delete"
+ ]
+ }
+ },
+ "default": {
+ "type": "boolean"
+ }
+ },
+ "additionalProperties": true
}
}
}
diff --git a/protocol/versions/2026-10-04/architecture.md b/protocol/versions/2026-10-04/architecture.md
index 50fdda0f..6e52bf5f 100644
--- a/protocol/versions/2026-10-04/architecture.md
+++ b/protocol/versions/2026-10-04/architecture.md
@@ -94,7 +94,7 @@ Model ───┘ └──▶ Container ──▶ File, File,
part of a container: artifacts come from the working directory, the environment is what the
working directory reads ([Environments](environments.md)).
- A **memory** is a place that outlasts every session: a node in a tree, holding records, with access
- granted per node and inherited downward. A harness names the memories its agent starts from; it is
+ granted per node and inherited downward. An agent is granted memories as a person is; a memory is
never part of a session or a container ([Memories](memories.md)).
> **Why is the session implicit?**
diff --git a/protocol/versions/2026-10-04/errors.md b/protocol/versions/2026-10-04/errors.md
index 8bf8f15b..8b126aa0 100644
--- a/protocol/versions/2026-10-04/errors.md
+++ b/protocol/versions/2026-10-04/errors.md
@@ -84,7 +84,7 @@ Rules:
| `memory_not_found` | 404 | No such memory, or one the caller holds no privilege on: the two are one answer ([Memories §12](memories.md#12-errors)). |
| `memory_forbidden` | 403 | The caller sees the memory and lacks the privilege the operation needs. |
| `memory_record_not_found` | 404 | No such record in this memory. |
-| `memories_not_attached` | 404 | The harness has no memories attached. |
+| `memories_not_attached` | 404 | The agent holds no memory: nothing was granted to it. |
| `memory_invalid` | 422 | A parent that would make a cycle, two default entries, a record with no content, a query whose parameters do not match. |
| `memory_unsupported` | 422 | An operation the memory's provider does not implement at all. A partial answer is reported in `degraded`, not as this. |
| `memory_busy` | 409 | A move or a delete while a consolidation runs. |
diff --git a/protocol/versions/2026-10-04/harnesses.md b/protocol/versions/2026-10-04/harnesses.md
index 8867eac8..9fac5e04 100644
--- a/protocol/versions/2026-10-04/harnesses.md
+++ b/protocol/versions/2026-10-04/harnesses.md
@@ -65,9 +65,9 @@ Returns one harness object, or `404` with `code: "harness_not_found"`.
| `timeoutSeconds` | integer \| null | no | Default wall-clock budget |
| `createdAt` | integer | yes | Unix milliseconds |
-The memories a harness's agent starts from are attached at a route of their own,
-`PUT /v1/harnesses/{id}/memories`, because attaching one is granting the harness access to it
-([Memories §9](memories.md#9-attaching-memories-to-a-harness)); they are not a field of this object.
+The memories a harness's agent reaches are not a field of this object. The agent is a member and
+is granted on the memory, like a person; `/v1/harnesses/{id}/memories` reads what it was granted
+and keeps two settings ([Memories §9](memories.md#9-an-agent-and-its-memories)).
`base` values are not enumerated by this specification. A server MAY support bases this document has
never heard of, and a client MUST treat `base` as an opaque string — anything else means the
diff --git a/protocol/versions/2026-10-04/memories.md b/protocol/versions/2026-10-04/memories.md
index 3ca3c91b..dfc44002 100644
--- a/protocol/versions/2026-10-04/memories.md
+++ b/protocol/versions/2026-10-04/memories.md
@@ -16,9 +16,9 @@ procedure. Memories are arranged in a tree, the way folders are, so one memory c
company knows and another, beneath it, what is known about one customer. Access is granted per
memory, and a memory's children inherit it.
-A harness is attached to the memories its agent should start from. During a task the agent searches
-them and adds to them with tools. What it may read and where it may write is decided by the server,
-from what the harness was granted, and never by the agent itself.
+An agent is given access to memories the way a person is. During a task it searches them and adds
+to them with tools. What it may read and where it may write is decided by the server, from what
+the agent was granted, and never by the agent itself.
This chapter is the Harness Memories sub-protocol. It is optional: a server advertises it with the
`memories` capability, and a server that does not implement it is conformant at every class.
@@ -105,21 +105,27 @@ may act, and a record's `written_by` names who did.
| Kind | Who | Holds grants | Writes records |
|---|---|---|---|
-| `member` | A person | yes | yes |
-| `harness` | An agent, running under that harness | yes | yes |
+| `member` | Anyone who acts: a person or an agent | yes | yes |
| `group` | A set of members the server resolves: a team, a workspace | yes | no, its members do |
| `provider` | The memory's provider itself: what it derived from an observation, what a consolidation run concluded | no | yes |
+**A person and an agent are the same kind.** Both are members, granted the same way, checked the
+same way, and able to belong to the same groups. Which of the two a member is, is a property of
+the member, `type`: `human` or `agent`. It is carried for a reader who wants to know, and no rule
+of this chapter depends on it. An agent belongs to a group when someone adds it, as a person does;
+a server MUST NOT place an agent in a group on its own.
+
A kind of a server's own is `x.`-prefixed (`x.team`). A server MUST NOT use another unprefixed
kind, and refuses a grant that names one.
The two places write the same identity two ways. In a grant, a **principal** is the string
-`<kind>:<id>`. On a record, the writer is `{ "kind": …, "id": … }`. They name the same thing:
+`<kind>:<id>`. On a record, the writer is `{ "kind": …, "id": …, "type": … }`. They name the same thing:
`written_by.kind` and `written_by.id`, joined by a colon, are the principal a grant would name.
The `id` is the server's own and opaque to a client.
-A credential is not a kind. A request made with an API key acts as the member or the harness the
-key belongs to, and is granted and stamped as that.
+A credential is not a kind, and neither is a harness. A request made with an API key acts as the
+member the key belongs to. A harness is a configuration; its agent is a member, and a server says
+which one ([§9](#9-an-agent-and-its-memories)).
### 3.1 Grants and inheritance
@@ -175,7 +181,7 @@ A record is one thing a memory holds. Its `id` is the provider's and opaque to a
"valid_from": "2026-09-30T00:00:00Z", "valid_to": null,
"written_at": "2026-10-01T17:02:11Z", "invalidated_at": null
},
- "written_by": { "kind": "harness", "id": "chrn_41c0" },
+ "written_by": { "kind": "member", "id": "chrn_41c0", "type": "agent" },
"references": [
{ "rel": "derived_from", "memory_id": "hmem_…", "record_id": "hrec_…" }
],
@@ -505,45 +511,57 @@ Each operation states the privilege it needs and is offered to an agent as a too
no limit on type names (beyond the `x.` prefix for types it does not define), fields or operations.
A provider that registers none reports `types: false` and answers the listing with the core types.
-## 9. Attaching memories to a harness
+## 9. An agent and its memories
+
+An agent is a member ([§3](#who-acts-on-a-memory)). It reaches the memories it was granted, and it
+is granted where everyone is: on the memory, with `POST /v1/memories/{id}/grants`. There is no
+second list of what an agent may use, and nothing on a harness widens or narrows what its agent
+was granted.
-A harness names the memories it works with:
+A harness adds two settings of its own:
| Request | What it does |
|---|---|
-| `PUT /v1/harnesses/{id}/memories` | Replace the list of attached memories; an empty list detaches them all |
-| `GET /v1/harnesses/{id}/memories` | The memories this harness is attached to |
+| `GET /v1/harnesses/{id}/memories` | The agent's principal, the memories it was granted with its privileges on each, and the two settings |
+| `PUT /v1/harnesses/{id}/memories` | Set `default_memory_id` and `observe` |
```json
-{ "memories": [
- { "memory_id": "hmem_0a1b…", "access": "read" },
- { "memory_id": "hmem_7c1e…", "access": "write", "default": true }
-] }
+{
+ "object": "harness.memories",
+ "principal": "member:chrn_41c0",
+ "default_memory_id": "hmem_7c1e…",
+ "observe": true,
+ "data": [
+ { "id": "hmem_0a1b…", "name": "Support",
+ "privileges": ["read"], "default": false },
+ { "id": "hmem_7c1e…", "name": "Agent notes",
+ "privileges": ["read", "write"], "default": true }
+ ]
+}
```
-- Attaching is granting. Access has one source, the grants ([§3](#3-access)): an entry the
- harness already holds is attached as it is; one it does not hold is granted by the same call when
- the caller may change that memory's grants (`delete`), and refused otherwise, when the harness is
- written and not at run time. Detaching removes a starting point and leaves the grant, which is
- revoked where grants are.
-- `access` narrows; it never widens. `read` on a memory the harness may also write gives the agent
- read tools only, on that memory and on whatever it walks to from it.
-- One entry MAY be marked `default`: where `observe` and an unaddressed `remember` go.
-- A task MAY name one more memory in `metadata.memory` on the request, where `harness_id` and
+- `principal` is who this harness's agent is to the access model. A grant names it; a record the
+ agent writes is stamped with it.
+- `data` is read off the grants, never stored on the harness: every memory the agent holds a grant
+ on, highest in the tree first. It is where the agent starts. From each it reaches everything
+ below, and nothing above that it was not granted.
+- `default_memory_id` is where an unaddressed `remember` goes and where turns are recorded. It MUST
+ be a memory the agent may write; a server refuses one it may not, with `memory_invalid`.
+- `observe`, on by default, records each finished turn in the default memory as an episode.
+- A task MAY name a memory in `metadata.memory` on the request, where `harness_id` and
`environment` already travel ([Tasks §1.2](tasks.md#12-selecting-the-harness)): the memory of
- the person this task is for, say. It is added to the harness's for the session the task starts,
- it is where that session writes by default when the harness may write it, and it is checked
- against the harness's privileges exactly as an attached memory is: a task naming a memory the
- harness holds nothing on is refused with `memory_not_found` before it starts. A memory is always
- named by its id. The server does not derive a node from anything else in a request, and creating
- a person's memory is the caller's act, done before the task with `POST /v1/memories`.
+ the person this task is for, say. It is the default for the session that task starts. It grants
+ nothing: a task naming a memory the agent holds nothing on is refused with `memory_not_found`
+ before it starts. A memory is always named by its id. The server does not derive a node from
+ anything else in a request, and creating a person's memory, and letting the agent into it, is
+ the caller's act, done before the task.
### 9.1 What a session does
| Moment | Called by | What happens |
|---|---|---|
-| **Prime** | server, at session start and after the conversation is compacted | The server reads what the provider marks as always-relevant in each attached memory and places it, with each memory's `name`, `description` and children, in the agent's instructions |
-| **Tools** | agent, during a turn | `memory_list`, `memory_recall`, `memory_get`, `memory_remember`, `memory_revise`, `memory_forget`, `memory_run_query` for the named queries a memory lists, `memory_operate` for a type's operations, and `memory_query` where a provider offers free queries. Write tools are offered only to a harness attached somewhere to write. The attached memories are where the agent starts; from each it may walk to the parent and the children a response names, and on from there, as far as the harness's own privileges reach. The server checks every step |
+| **Prime** | server, at session start and after the conversation is compacted | The server reads what the provider marks as always-relevant in each memory the agent was granted and places it, with each memory's `name`, `description` and children, in the agent's instructions |
+| **Tools** | agent, during a turn | `memory_list`, `memory_recall`, `memory_get`, `memory_remember`, `memory_revise`, `memory_forget`, `memory_run_query` for the named queries a memory lists, `memory_operate` for a type's operations, and `memory_query` where a provider offers free queries. Write tools are offered only to an agent that holds `write` somewhere. The memories it was granted are where the agent starts; from each it may walk to the parent and the children a response names, and on from there, as far as its own privileges reach. The server checks every step |
| **Observe** | server, when a turn ends | The turn (what was asked, what was answered, which tools ran) is sent to the default memory as episodes. No model is involved on the server's side |
| **Consolidate** | server, on a schedule or when idle | The server asks the provider to do its background work. What that is belongs to the provider |
@@ -554,8 +572,8 @@ the cost is visible even where it is not set by the client.
Priming is not repeated every turn. Instructions that change every turn defeat prompt caching, and
retrieval during a turn is what the tools are for.
-A server MUST tell the person who attaches a memory whose provider is outside the server that every
-turn will be sent to it.
+A server MUST tell the person who sets a default memory whose provider is outside the server that
+every turn will be sent to it.
### 9.2 Consolidation runs
@@ -663,7 +681,7 @@ the differences are said, and three rules keep it honest:
```
A server that reports `memories: true` implements [§2](#2-the-memory-object) to [§6.3](#63-the-response)
-and [§9](#9-attaching-memories-to-a-harness). Named and free queries, types, the media a record's content may carry, snapshots, consolidation runs and erase are
+and [§9](#9-an-agent-and-its-memories). Named and free queries, types, the media a record's content may carry, snapshots, consolidation runs and erase are
reported per provider ([§10.2](#102-the-capability-document)). A server that does not implement the
chapter reports `false` or omits it and answers its endpoints with `404`.
@@ -674,8 +692,8 @@ chapter reports `false` or omits it and answers its endpoints with `404`.
| `memory_not_found` | 404 | No such memory, or one the caller may not see |
| `memory_forbidden` | 403 | The caller sees the memory and lacks the privilege the operation needs |
| `memory_record_not_found` | 404 | No such record in this memory, including a record of another memory asked for through this one |
-| `memories_not_attached` | 404 | The harness has no memories attached |
-| `memory_invalid` | 422 | A parent that would make a cycle; a default on two entries; a query whose params do not match |
+| `memories_not_attached` | 404 | The agent holds no memory: nothing was granted to it |
+| `memory_invalid` | 422 | A parent that would make a cycle; a default memory the agent may not write; a query whose params do not match |
| `memory_unsupported` | 422 | An operation the memory's provider does not implement at all (a partial answer is `degraded`, not this) |
| `memory_busy` | 409 | A move or a delete while a consolidation runs |
| `memory_unavailable` | 502 or 503 | The provider did not answer, or is not connected |
@@ -686,10 +704,12 @@ chapter reports `false` or omits it and answers its endpoints with `404`.
another agent, for another person. A server MUST present recalled content to the agent as data,
fenced from instructions, and MUST carry `written_by` with it.
- **The agent chooses its path, never its reach.** An agent may walk up and down the tree from the
- memories its harness attaches, and a search covers what is below the memory it asks. What it can
- reach either way is every memory the harness holds a privilege on, no more, checked by the server
- on every call and for every memory a search covers. A harness that should see one branch and
+ memories it was granted, and a search covers what is below the memory it asks. What it can
+ reach either way is every memory it holds a privilege on, no more, checked by the server
+ on every call and for every memory a search covers. An agent that should see one branch and
nothing above it is granted that branch and nothing above it.
+- **An agent is granted on purpose.** It starts with nothing, and joins a group only when someone
+ adds it. Equal standing with a person does not mean an agent inherits what people share.
- **Provenance is stamped, not supplied.** `written_by` and `written_at` come from the authenticated
caller and the server's clock.
- **Unknown is indistinguishable from forbidden** on reads of memories and of reference targets.
diff --git a/protocol/versions/2026-10-04/security.md b/protocol/versions/2026-10-04/security.md
index a32a3982..a2d9ea0c 100644
--- a/protocol/versions/2026-10-04/security.md
+++ b/protocol/versions/2026-10-04/security.md
@@ -159,7 +159,7 @@ for another person. Three properties follow, and none can be left to the agent.
- **What a memory returns is untrusted content.** A record may have been written by a model that
had read a hostile page. A server MUST present recalled content to an agent as data, fenced from
instructions, with who wrote it ([Memories §13](memories.md#13-security)).
-- **Reach is the harness's grants, on every call.** An agent may walk the tree from where it was
+- **Reach is the agent's grants, on every call.** An agent may walk the tree from where it was
attached, and a search covers what is below the memory it asks; what it can reach is decided by the server from grants, not by what the agent asks
for, and a memory it may not read is answered exactly as one that does not exist.
- **A provider's credential never reaches a sandbox.** It belongs to whoever connected the provider
diff --git a/protocol/versions/2026-10-04/tasks.md b/protocol/versions/2026-10-04/tasks.md
index f129c511..ad289b1d 100644
--- a/protocol/versions/2026-10-04/tasks.md
+++ b/protocol/versions/2026-10-04/tasks.md
@@ -28,7 +28,7 @@ Content-Type: application/json
|---|---|---|---|
| `input` | string \| item[] | yes | The work. A bare string is shorthand for one user message. See §2. |
| `model` | string | no | Canonical model id. Omitted means the harness's default. |
-| `metadata` | object | no | Client metadata. `harness_id` selects the configured harness (§1.2). `memory` names one more memory this task works with, on a server with the `memories` capability ([Memories §9](memories.md#9-attaching-memories-to-a-harness)). |
+| `metadata` | object | no | Client metadata. `harness_id` selects the configured harness (§1.2). `memory` names one more memory this task works with, on a server with the `memories` capability ([Memories §9](memories.md#9-an-agent-and-its-memories)). |
| `stream` | boolean | no | `true` streams Server-Sent Events; default `false` returns one JSON object. |
| `previous_response_id` | string | no | Continue the session that produced that response. See [Sessions](sessions.md). |
| `instructions` | string | no | Additional system guidance for this task only. |