wiki/concepts/consent-physics

Consent Physics

wiki/concepts/consent-physics/index.md

Rendered from markdown source. Open raw source on GitHub.

Consent Physics

Working definition: the idea that consent behaves like a dynamic field with timing, latency, revocation, boundary, and manifestation behavior rather than a one-time permission event.

This page is the concept-layer version of the Consent Physics branch under Loop and Phase Training. The project page keeps the source documents together; this page keeps the shared idea visible once the material is viewed across branch boundaries.

The recurring move is simple: consent stops being a checkbox and becomes a continuous state that can be inspected, delayed, revised, activated, or withdrawn. That is why the concept keeps touching timing, repair, recovery, and protocol language. It is not just about agreement; it is about how agreement moves through a system. The governance edge matters here too: once consent becomes a state instead of a moment, the system has to know who can certify it, how revocation is witnessed, and what provenance follows the decision. That is where Governance Diad and the Consentocracy Bridge sit nearby.

The page also gives Intent-Consent a stronger neighbor. Intent names direction, while consent physics names the conditions under which the direction can actually remain valid over time.

ACT–POLICY is the executable counterpart to that idea: it models whether an act may proceed, what witness it needs, and when state can change without collapsing consent into a one-shot approval event.

Related Artifacts

Related Pages

Attractor Bridge

Notes

  • This is a concept page, not a canon claim.
  • Keep the project branch and the concept layer separate.
  • Split again only if the consent/latency seam starts recurring under a second name.