jerry/buzz
1
0
Fork 0
mirror of https://github.com/block/buzz.git synced 2026-10-28 13:01:10 +00:00
Code Issues Packages Projects Releases Wiki Activity

docs(protocol): name artifact scope on the wire

Browse Source 
Signed-off-by: Fizz <400e8babadcee6a7f420103f10a2849d84c4a9c71d5bd04f3948c814216648a3@buzz.block.builderlab.xyz>
This commit is contained in:
Fizz
2026-09-20 16:59:10 -07:00
parent 603ccefc79
commit 109ec5d301
1 changed files with 4 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

7
docs/nips/NIP-AR.md
View File

@@ -15,8 +15,9 @@ attached to a conversation within it. This NIP defines a common envelope,
identity, revision chain, access rules, and lifecycle for artifacts with
client-defined content types.
The current home channel determines the artifact's audience. Any number of
artifacts, including of the same type, may share a channel or conversation.
Each artifact has exactly one current home channel, which determines its
audience. Any number of artifacts, including of the same type, may share a
channel or conversation.
Relationships between artifacts organize work without granting access or
operational authority. The relay validates the envelope and lifecycle; clients
interpret and validate content according to its type.
@@ -94,7 +95,7 @@ visibility, plus authentication, token-channel restrictions, moderation, and
archive gates. An otherwise authorized community participant may create/edit in
an open channel without first joining it. “Administration” means Admin/Owner
channel authority under channel authorization rules. Artifact writes require
`Scope::ChannelsWrite` plus the operation-specific channel checks below.
`channels:write` plus the operation-specific channel checks below.
Clients and agent tokens must request that scope; a numeric member-role
threshold must not exclude agents.