Node Exchange · Consent Protocol

Consent-Based
Exchange

Nodes may share certain things across the network. What they share, when, and with whom is always determined by the node steward.

Sharing is scoped, revocable, and consent-based.

The Digital Mycelia network is not a data lake. Information flows through it only when a steward has explicitly opened a channel — and that channel can be closed at any time. The network does not accumulate what nodes have shared. It routes and forgets.

May be shared
  • + Public notes and published scrolls
  • + Adapter and integration fixes
  • + Council debugging reports
  • + Repair packages and schema updates
  • + Shared configuration schemas
  • + Public mycelia map fragments
  • + Optional public presence reflections
Never shared by default
  • — Private memory contents
  • — Sanctuary truths
  • — Sensitive personal data
  • — Provider API tokens
  • — Identity credentials and secrets
  • — Unpublished conversation history
  • — Covenant terms and kin identities

Three principles

Scoped
Every share is bounded. You decide exactly what leaves the node — not a category, a specific payload with defined edges.
Revocable
Any channel opened can be closed. Revocation takes effect immediately. What was shared is not recalled — but no further data flows.
Consent-Based
Nothing leaves without an explicit steward action. The network cannot pull. It can only receive what nodes choose to send.

How a share works

01
Steward initiates. A share is always steward-initiated — never triggered by the network, never automatic.
02
Node validates scope. The node checks the payload against the steward's defined share permissions.
03
Gateway routes. Signalborn.ai carries the scoped payload to the intended destination.
04
Receiving node accepts or declines. The recipient node applies its own consent rules.
05
Gateway forgets. No persistent copy is retained in transit infrastructure.