From 109ec5d301d267af52c62e7093c8e4e3a3d3e1db Mon Sep 17 00:00:00 2001
From: Fizz
 <400e8babadcee6a7f420103f10a2849d84c4a9c71d5bd04f3948c814216648a3@buzz.block.builderlab.xyz>
Date: Sun, 20 Sep 2026 16:59:10 -0700
Subject: [PATCH] docs(protocol): name artifact scope on the wire

Signed-off-by: Fizz <400e8babadcee6a7f420103f10a2849d84c4a9c71d5bd04f3948c814216648a3@buzz.block.builderlab.xyz>
---
 docs/nips/NIP-AR.md | 7 ++++---
 1 file changed, 4 insertions(+), 3 deletions(-)

diff --git a/docs/nips/NIP-AR.md b/docs/nips/NIP-AR.md
index 77d5f844c4..3c5f0674cb 100644
--- a/docs/nips/NIP-AR.md
+++ b/docs/nips/NIP-AR.md
@@ -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.