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 now stands as its own lineage page under Consent Crystal Structure Research.

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 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.

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.