wiki/projects/side-projects-desktop/consent-scoped-communication

Rendered from markdown source. Open raw source on GitHub.

Consent-Scoped Communication

This branch collects the explicit-scope communication substrate and its practical framing materials.

It is a provisional infrastructure branch, not a canon declaration. The material treats scope as first-class metadata so public, group, private, and secure communication can share one protocol surface.

Nested Lineage Pages

• Substrate Specification
• Reference Implementation
• Infrastructure Opportunity
• One Protocol. Every Conversation.
• AI Readiness / Machine-Readable Intent
• Internal Briefing

Working Read

This family argues that communication systems fail when scope is implicit. Once AI can analyze, summarize, infer, and retain at scale, scope has to move from social convention into declared message metadata.

The branch is narrower than general governance and wider than a single product: it defines a communication substrate that can support enforcement, privacy, moderation, compliance, and machine-readable intent without fragmenting into separate systems.

Semantic Role

• Scope names who may see, participate, and reuse.
• Enforcement names how scope is carried out.
• Intent names what the organization or participant means to permit.
• Machine-readable intent names the legible form of that boundary.
• Communication substrate names the shared message grammar.

Related Links

• Consent Grammar
• ACT–POLICY
• Witnessing
• Intent-Consent
• Governance Diad
• Consent Physics
• Continuity Office

Attractor Bridge

• Consent
• Witness
• Governance
• Trust
• Agency
• Meaning

Next Actions

1. Keep the substrate, implementation, and opportunity pages together unless a second durable seam appears.
2. Route future communication-scope or machine-readable-intent drafts here when they describe shared protocol rather than a specific product.
3. Split only when a child branch develops a separate operational identity.