wiki/projects/consent-intent-compression-protocol/protocol-foundations

Protocol Foundations

wiki/projects/consent-intent-compression-protocol/protocol-foundations/index.md

Rendered from markdown source. Open raw source on GitHub.

Protocol Foundations

Parent lineage: Consent–Intent Compression Protocol (CICP)

This is the protocol and language spine of the CICP root intake. The documents here read as a coherent technical branch rather than isolated notes.

It defines the vocabulary CICP uses to talk about loops, equivalence, and trust propagation. The three subpages split that vocabulary into model, language, and continuity layers.

Current Shape

  • 13 protocol, specification, and language documents.
  • 3 nested lineage pages organize those documents.

Nested Lineage Pages

Representative Files

Working Read

This branch now separates into loop modeling and field theory, glyph languages and equivalence, and synaptic trust and propagation. That matches the document families already visible in the intake.

The deeper function of this cluster is to define the protocol language itself. It names the abstractions that CICP uses to talk about loops, field behavior, equivalence, and trust propagation, so it is the vocabulary spine of the branch rather than just a topical grouping. From the field-atlas view, this page is the local grammar node for Consent, Loop Mechanics, Witness, and Provenance as they are used inside CICP.

The three subpages map to the core protocol layers: how the loop model works, how symbolic forms stay equivalent, and how trust can propagate without losing structure.

Each of those three layers now has its own deeper child page so the vocabulary spine can be read from coarse structure down into the specific loop, grammar, and continuity seams.

Core Claim

The foundation rail says that the smallest meaningful unit in CICP is a consented loop, and that loop structure can be used to project, translate, and stabilize broader systems. The protocol does not begin with abstract theory; it begins with a repeatable relational unit that can be modeled, symbolized, and trusted.

Key Terms

  • Loop: a coherent relation held by intention, consent, attention, memory, and exit or reconsent.
  • Field: the larger relational environment in which loops arise and feed back.
  • Glyph: a meaning-bearing symbol whose significance is loop-agreed rather than fixed.
  • Equivalence: the process of mapping meaning across forms or domains through consented translation.
  • Synaptic trust: a dynamic relationship state that can amplify, attenuate, or pass signal depending on context.

Mechanisms

  • Loop Modeling and Field Theory turns the loop into a projectable seed.
  • Glyph Languages and Equivalence turns symbolic meaning into a consented language stack.
  • Synaptic Trust and Propagation turns relationship state into a context-aware filter and transmission system.

Implications

This rail is doing more than naming terminology. It is building the grammar that later pages rely on when they talk about access, training, identity, and field infrastructure. If the vocabulary layer is weak, the rest of the branch becomes decorative. If it is strong, the branch can stay coherent even as it branches into practical implementations.

Open Questions

  • Which loop properties are essential for projection versus merely descriptive?
  • How much symbolic freedom can the glyph layer support before equivalence becomes unstable?
  • What is the minimal trust model that still supports the later access rail?

Related Links

Next Actions

  1. Keep the three nested lineage pages stable.
  2. Keep the new deeper child pages stable.
  3. Split again only if one of the three tracks develops another durable seam.