Skip to content

Commit 560a67b

Browse files
Paulwpfleger96
andcommitted
docs(nip-ap): keep 44300 deletions private and pin share semantics
Deletion requests for instructions versions carried version ids in a publicly readable kind:5, contradicting the author-only promise; they now require k=44300 and inherit the author-only gate. Shares are defined as snapshots, team deletion confirms in the authoritative store rather than assuming a relay, and the delivered team layer is the trimmed text. Co-authored-by: Will Pfleger <[email protected]> Signed-off-by: Will Pfleger <[email protected]> Signed-off-by: Paul <4a1bfa0013bc6d14a8d600d8bf6392efefbd2a26ac3c96c9b2a106b0d12297ca@buzz.block.builderlab.xyz>
1 parent 4369b7a commit 560a67b

1 file changed

Lines changed: 9 additions & 4 deletions

File tree

‎docs/nips/NIP-AP.md‎

Lines changed: 9 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -268,7 +268,7 @@ Kind `30178` is the **shareable projection of a team**: owner-authored, paramete
268268

269269
**Content carries only sanitized fields.** No environment variables, no `respond_to` allowlist pubkeys, no source or local ids, no filesystem paths, no secrets. Sharing a team makes the team's and every member's instructions community-readable plaintext.
270270

271-
**A share carries current instructions, never history.** A writer embeds the team's current instructions (see "Team instructions") and no `kind:44300` versions. A reader that adopts a shared team creates a new team with a new id; the adopted team starts its own instructions history.
271+
**A share is a snapshot, never history.** A writer embeds the team's current instructions at the time it publishes (see "Team instructions") and no `kind:44300` versions. Saving a version does not change an existing share; the owner updates a share by publishing a new head. A client MAY show the owner that a share is older than the team's current instructions. A reader that adopts a shared team creates a new team with a new id; the adopted team starts its own instructions history.
272272

273273
## Teams
274274

@@ -300,14 +300,14 @@ Before a team has any version, a client MAY use instructions held in its private
300300

301301
When an agent starts, the client resolves the current instructions of every team the agent is a member of and compares them after trimming leading and trailing whitespace. A team without instructions has empty instructions, which is a value like any other.
302302

303-
- If every team's instructions are equal, the agent receives that text once, as its team layer.
303+
- If every team's instructions are equal, the agent receives the trimmed text once, as its team layer.
304304
- If any differ, or any are invalid, the client MUST NOT start the agent, and SHOULD name the teams involved. A running agent is not affected. The owner resolves a conflict by changing a team's instructions or removing a membership.
305305

306306
An agent that is a member of no team has no team layer. The team layer is delivered after the agent's own instructions (see "Launch composition").
307307

308308
### Deleting a team
309309

310-
A client that deletes a team SHOULD also delete the team's instructions versions (see "Deletion: kind:44300"). It MUST first confirm that the relay stored the deletion of its private team record, so the team never appears with an older version as current while versions are being deleted. After that, a client MUST NOT publish a version for the deleted team, including a save that was pending when the team was deleted.
310+
A client that deletes a team SHOULD also delete the team's instructions versions (see "Deletion: kind:44300"). It MUST first confirm that the deletion of its private team record is durable in the store that is authoritative for that record (for a record held on a relay, that the relay stored the deletion), so the team never appears with an older version as current while versions are being deleted. After that, a client MUST NOT publish a version for the deleted team, including a save that was pending when the team was deleted.
311311

312312
At each member's next start, the client removes the deleted team's membership and resolves the team layer from the remaining teams. A running agent is not affected. Missing versions alone never mean that a team was deleted.
313313

@@ -421,9 +421,11 @@ Instructions versions are readable only by their author. The agent's key has no
421421

422422
The relay still sees each event's subject tag, timestamp, and padded size, so it can observe how often each agent's or team's instructions change and roughly how long they are.
423423

424+
Clients MUST publish instructions versions, and deletion requests for them, only to the relay community that holds the subject.
425+
424426
### Deletion: kind:44300
425427

426-
Owners MAY publish [NIP-09](09.md) deletion requests for instructions versions, one `e` tag per version, with `["k", "44300"]`. A relay MAY accept only one target per request. Clients SHOULD publish one request per version, retry until every version is deleted, and MUST NOT report a subject's history deleted after deleting only part of it.
428+
Owners MAY publish [NIP-09](09.md) deletion requests for instructions versions, one `e` tag per version. A deletion request for a `kind:44300` event MUST carry `["k", "44300"]`; the relay classifies it by that tag, so it stays private after its target is removed (see "Access control: kind:44300 author-only"). A relay MAY accept only one target per request. Clients SHOULD publish one request per version, retry until every version is deleted, and MUST NOT report a subject's history deleted after deleting only part of it.
427429

428430
- A client that deletes an agent SHOULD delete all of that agent's versions. It MUST NOT delete any team's versions.
429431
- A client that deletes a team follows "Deleting a team".
@@ -457,12 +459,15 @@ Kind `30178` is stored globally and its content is unvalidated, exactly as for `
457459
- The relay MUST reject, with `invalid:`, a `kind:44300` event that does not carry exactly one subject tag as defined in "Event envelope", whose `p` value is not 64-character lowercase hex, or whose `t` value does not match the team id grammar.
458460
- The relay MUST reject a `kind:44300` event with an empty `content` or a `content` longer than 218,548 bytes. It cannot validate the plaintext; that is a client responsibility.
459461
- The relay MUST reject a `kind:44300` event that carries an `h` tag.
462+
- The relay MUST reject a `kind:5` deletion request that targets a stored `kind:44300` event and does not carry `["k", "44300"]`.
460463
- The relay stores `kind:44300` events globally, outside any channel.
461464

462465
### Access control: kind:44300 author-only
463466

464467
The relay MUST withhold `kind:44300` events, and their existence, from every reader except their authenticated author, on every read surface: historical REQ delivery, NIP-01 `ids` lookup, live fan-out, COUNT, and the HTTP bridge's query and count endpoints.
465468

469+
The relay MUST apply the same rule, on the same read surfaces and in search results, to every `kind:5` deletion request that carries `["k", "44300"]`, whether or not its target is still stored. A deletion request reveals a version's id and the time it was deleted.
470+
466471
The relay MUST exclude `kind:44300` from full-text search results for every reader, including the author.
467472

468473
The relay MUST apply a `#p` or `#t` filter on `kind:44300` before `ORDER BY … LIMIT`, so that `limit: 1` returns a subject's current version even when the owner has newer versions for other subjects.

0 commit comments

Comments
 (0)