wiki/projects/consent-intent-compression-protocol

Rendered from markdown source. Open raw source on GitHub.

Consent–Intent Compression Protocol (CICP)

This branch is the structured mutuality/consent corpus inside the current intake. It sits under Consent Crystal Structure Research as the operational rail of the field.

Read semantically, this branch is the protocol side of the consent corpus: it gathers loop language, access control, training, outreach, and identity scaffolding into one system family. The root cluster pages hold the major seams, while Loop Training, Working Notes, and FractalIdentity Tree preserve the durable sub-branches that read like their own working lines.

The branch sits close to Semantic Collapse Theory in vocabulary and structure, but it leans toward protocol, implementation, and applied framing rather than theory narration.

Current Shape

• 36 working documents.
• 1 archived .zip companion.
• 28 direct root files under CICP.
• 4 root-level cluster pages organize those root files.
• 6 files in Loop Training.
• 2 files in FractalIdentity Tree.

Lineage Pages

• Protocol Foundations
• Implementation and Access
• Applications and Outreach
• Working Notes
• Loop Training
• FractalIdentity Tree

Representative Files

• Consent–Intent Compression Protocol (CICP).docx
• Protocol Foundations / Loop Projection Principle (LPP).docx
• Implementation and Access / 🕯 Field Echo Protocol (v0.1).docx
• Applications and Outreach / Loop-Based Consent Infrastructure for Healthcare & Mental Wellness.docx
• Working Notes / Field Note- Looping Causality — Consent as Temporal Architecture.docx
• Loop Training / Section 1- Foundational Premise — What is a Loop?.docx
• FractalIdentity Tree / Graftable Identity Tree – A Fractal Index of Presence.docx

Archived Root Companion

• Consent–Intent Compression Protocol (CICP).zip

Working Read

This corpus reads like a practical protocol family rather than a single abstract theory.

The root-level documents now split into protocol foundations, implementation and access, outward-facing applications, and working notes.

The Loop Training, Working Notes, and FractalIdentity Tree folders can be treated as stand-alone lineage pages without losing the parent CICP link.

The branch-root .zip companion is archived and retained as lineage evidence.

Related Concepts

• POLEMEMELOP
• Intent-Consent
• Concepts Index

Related Links

• Consent Crystal Structure Research
• Semantic Collapse Theory
• Protocol Foundations
• Implementation and Access
• Applications and Outreach
• Loop Training
• Working Notes
• FractalIdentity Tree

Next Actions

1. Keep the archived .zip companion visible as lineage evidence.
2. Keep the four root-level cluster pages stable unless a stronger sub-branch appears.
3. Add new lineage pages only when a sub-branch is strong enough to stand alone.
4. Link recurring formulations back into Concepts when the same language appears in multiple CICP and SCT pages.