wiki/projects/consent-intent-compression-protocol/loop-training

Loop Training

wiki/projects/consent-intent-compression-protocol/loop-training/index.md

Rendered from markdown source. Open raw source on GitHub.

Loop Training

Parent lineage: Consent–Intent Compression Protocol (CICP)

This is a stand-alone lineage page under the CICP branch.

It is the explanation and onboarding rail: the part of CICP that teaches the loop model in sequence.

Current Shape

  • 6 training documents.
  • 2 deeper sequence pages.

Representative Files

Working Read

This sub-branch reads like onboarding and explanation material for the CICP family. It can stand alone without losing the parent lineage back to the protocol branch.

The sectioned structure suggests a deliberate teaching sequence rather than a pile of notes. That makes it the clearest place in CICP for introductory framing, slow disclosure, and cross-referenced explanation.

The training rail now splits into a foundational opening sequence and a field-identity/deployment sequence so the pedagogy can be followed in order.

Core Claim

The training rail exists because the protocol is easier to misuse than to understand. It therefore stages the concept in order: what a loop is, how loops sit inside fields, how awareness changes the role of the observer, and how the model can be turned into teachable tools without coercion.

Sequence Logic

  • Section 1 defines a loop as intention, consent, attention, memory, and continuity.
  • Section 2 relocates the loop inside a broader relational field.
  • Later sections move from awareness into field identity.
  • The final section treats deployment as a training tool rather than a product endpoint.

Mechanisms

  • Practice prompts are used to make loop recognition experiential.
  • Reconsent is treated as a normal integrity mechanism, not as an exception.
  • Deployment artifacts are framed as invitations to reflexivity.
  • The sequence avoids forcing closure; it favors recurrent return.

Implications

This page is the pedagogical hinge of the branch. It is where the abstract loop language can become something a human or AI guide can actually carry. That makes it important even if it does not look like a product surface.

Open Questions

  • How much training detail belongs in the wiki versus the source documents?
  • Which training metaphors are durable and which are merely situational?
  • Should later sections be restructured if a new audience needs a different entry point?

Related Links

Next Actions

  1. Keep the training section order stable unless a real revision appears.
  2. Preserve CICP backlinks if this page is split further.
  3. Keep the two deeper sequence pages aligned to the section order.