diff --git a/integrations/buzz-dkg.json b/integrations/buzz-dkg.json
index 0e9b78e..6baf110 100644
--- a/integrations/buzz-dkg.json
+++ b/integrations/buzz-dkg.json
@@ -38,7 +38,7 @@
     ],
     "notes": "The daemon talks only to the operator-configured Buzz relay and the local DKG node. It performs Working Memory create/write/finalize and Shared Working Memory share on human signal (a pinned thread or an @-mention), posting a machine-readable receipt back into the channel. Verifiable Memory publish (vm/publish) is a Curator-authority operation and is triple-gated: publishMode is 'disabled' by default (refuses all publication), 'mainnet' requires the node to report chain base:8453 and stays under a rolling-24h publication budget, and each publish additionally requires a per-channel authorized promoter's approval reaction that is consumed exactly once (SQL UNIQUE) and validated against the receipt's KA + source-set digest (re-read from the shared graph at approval time). Trusted-component disclosure: inbound event authenticity is delegated to the relay — the daemon does not itself re-verify Nostr Schnorr signatures on received events (the relay verifies on write); it snapshots the full signed events (NIP-01 preimage + id + sig) into the KA so claims remain independently checkable by any downstream consumer. Reads for the grounded-answering path use POST /api/query scoped to the bound Context Graph only, with no fallback to any other graph; note this scoping guarantees no OTHER graph is read, not that only room-authored content is returned — every member of a bound channel is effectively a reader of that Context Graph. Identity binding across ecosystems is NIP-OA verification only. No postinstall/preinstall scripts."
   },
-  "trustTier": "community",
+  "trustTier": "verified",
   "designBrief": "https://github.com/Zigoljube/buzz-dkg-integration/blob/main/docs/DESIGN.md",
   "demo": "https://github.com/Zigoljube/buzz-dkg-integration/blob/main/docs/acceptance-transcript.md",
   "promotionPath": "A pinned Buzz decision thread is distilled into a single-root PROV-O DecisionCluster written to Working Memory (create + wm/write), finalized and shared to the room's bound Context Graph as Shared Working Memory (swm/share), with a machine-readable receipt posted back into the channel. On an authorized promoter's approval reaction — enforced by the §6 invariants (promoter allowlist, receipt-target check, KA + source-set-digest match, single consume, publishMode and chain gate) — the asset is published to Verifiable Memory (vm/publish): anchored on-chain on Base and assigned a UAL, with the UAL receipt landing back in the room. Every VM Knowledge Asset preserves an unbroken wasDerivedFrom chain to its signed Nostr source events (Schnorr-verifiable independently of the relay), and outputs are modeled with PROV-O plus a thin Nostr vocabulary so context oracles can consume them downstream. A live example produced by this integration: a signed Buzz decision thread was published to Verifiable Memory at UAL did:dkg:base:8453/0x633e5a7c5e612d9981538f60d824cc03be97e2ab/2201 (tx 0x6daf3e0bad8cba13f7508f69c5550750a30294e997bf5e7fdffe9a24170dbb38, block 49145748) in the FIFA World Cup 2026 Context Graph, with full spend and lifecycle evidence in docs/gates/GATE_D3_REPORT.md and README.md.",