wiki/projects/side-projects-desktop/consent-scoped-communication/overview
One Protocol. Every Conversation.
wiki/projects/side-projects-desktop/consent-scoped-communication/overview/index.mdRendered from markdown source. Open raw source on GitHub.
One Protocol. Every Conversation.
This page compresses the one-page overview into the consent-scoped communication branch.
Source Artifact
- Source role:
standard_named_source - Inbound original: one_protocol_every_conversation_one_page_overview.md
- Standard-named source: 20260710__SIDE-PROJECTS-DESKTOP__OVERVIEW__CONSENT-SCOPED-COMMUNICATION__v1__one-protocol-every-conversation.md
Working Read
The overview states the simplest version of the argument: one communication substrate can support public, group, private, and secure interaction if every message declares scope. The conversation-persistence concept sits adjacent to this because a protocol for every conversation still has to account for energy, velocity, and whether the exchange remains resonant over time.
Core Claim
The communication stack does not need separate systems for different contexts. It needs explicit scope and enforcement as separate layers.
Key Ideas
- Public to private is scope refinement, not a platform switch.
- No hidden analytic privilege.
- AI must respect declared scope.
- The same mental model works across all environments.
Related Pages
- Consent-Scoped Communication
- Substrate Specification
- Infrastructure Opportunity
- Reference Implementation
- AI Readiness / Machine-Readable Intent
- Conversation as a Persistent System
Attractor Bridge
Notes
- This is a source-anchored overview, not a canon claim.
- Keep the sentence-level compression intact.