wiki/projects/side-projects-desktop/consent-grammar

Rendered from markdown source. Open raw source on GitHub.

Consent Grammar

This branch collects the consent, witness, boundary, and agency protocol cluster.

It is a provisional field-atlas branch, not a canon declaration. The material describes the grammar that keeps observation, permission, refusal, legibility, and state change distinct enough to remain governable.

Nested Lineage Pages

• How Consent Works
• Frame-Anchored Consent Protocol
• Witness + Options Protocol Framework
• Boundary Compute
• Physics of Agency

Working Read

This cluster converges on one claim: contact is cheaper to govern at the boundary than to repair after propagation. Consent, witness, and agency stay meaningful only when their boundaries remain explicit and revisable.

Semantic Role

• Consent names the boundary condition for contact.
• Witness names the non-merge discipline that keeps observation legible.
• Policy names the admissibility rule.
• Boundary compute names the work done before propagation.
• Agency names the available degrees of freedom.

Related Links

• Side Projects Desktop
• Consent–Intent Compression Protocol (CICP)
• Consentful Cybernetics
• Consent-Scoped Communication
• WitnessKey
• Trust Interoperability Standard
• Semantic Integrity

Attractor Bridge

• Consent
• Witness
• Agency
• Governance
• Trust
• Loop Mechanics

Next Actions

1. Keep this branch together until a second seam appears.
2. Route future boundary or consent essays here if they describe interaction grammar rather than finished policy.
3. Split only when one child page begins carrying a distinct protocol definition.