wiki/concepts/intent-consent

Intent-Consent

wiki/concepts/intent-consent/index.md

Rendered from markdown source. Open raw source on GitHub.

Intent-Consent

Working definition: a paired language for aligning intention with consent inside loop-based training, protocol, and identity material.

This concept appears in the Loop and Phase Training essay branch, its sibling branch page, the repair and maintenance pages, the Misc Loop sibling seam, the Consent Physics branch, and the CICP corpus, where the same vocabulary is used to frame mutuality, guidance, protocol behavior, and recovery.

In practice, Intent-Consent is the phrase-level attractor for work that tries to describe how intention becomes legible without losing consent structure. It is broad enough to recur, but still narrow enough to stay distinct from generic consent language. The training branch uses it as a vocabulary seam for repair, maintenance, and sequencing, while the concept page keeps the broader cross-branch pattern visible.

The useful distinction is that intent names direction while consent names permission. The corpus keeps returning to that pair because many of the documents are trying to model action without collapsing agency into assertion. In that sense, the concept is both a linguistic pattern and a governance primitive: it is where a proposed move becomes an accepted move, or fails to do so cleanly. What keeps the pair from becoming purely rhetorical is witness and provenance: the move has to be legible enough to certify, carry, and later explain. That is why the same language keeps touching governance and the Consentocracy Bridge whenever the corpus needs consent to survive time rather than only a single moment of approval.

Quantum Invariants is a useful comparator here because it makes the boundary/comparator/repair vocabulary explicit in a machine-readable form. That does not replace the concept; it just gives the concept a structural neighbor.

The newer research bundle around consent graphs, loop summaries, protocol intros, vector mapping, and consent-constrained intelligence pushes the same idea toward a more explicit model. Instead of treating consent as a static boundary, the bundle makes it a structured relation that can be graphed, summarized, and compared against outcome pressure.

That makes it an important neighbor to Abracadabracadoo, Witnessing, Governance Diad, LoopLink, and Consent Physics. Those pages describe what happens when intent-consent becomes protocol, certification, transport, legitimacy, or activation instead of remaining only a phrase.

ACT–POLICY extends that same grammar into a small executable substrate: it gives intent, permission, witness, and state a machine-readable rule set without pretending the rule set is the whole concept.

Related Artifacts

Related Pages

Attractor Bridge

Notes

  • This is a concept page, not a canon claim.
  • Keep the essay branch and the misc-loop sibling separate until a duplicate decision says otherwise.
  • Use this page when the same intent/consent phrasing shows up across multiple branches.