wiki/projects/consentful-cybernetics

Consentful Cybernetics

wiki/projects/consentful-cybernetics/index.md

Rendered from markdown source. Open raw source on GitHub.

Consentful Cybernetics

This branch collects the public site, research framing, and iteration bundles for the Consentful Cybernetics family.

It reads as a public-facing articulation of voluntary intelligence: one seam tunes the site and visual language, and the other seam tracks preregistration and research artifacts. The material is durable enough to keep together, but still better treated as an evolving site family than as a finished doctrine. The Consentocracy Bridge sits nearby as the external governance/provenance articulation of the same consent-first logic.

Quantum Invariants is a useful structural companion because it gives the consent and intelligence language a comparator model for boundaries, legibility, and drift.

Current Shape

  • 1 public site family.
  • 1 research and preregistration track.
  • 2 nested support pages organize the set.

Nested Support Pages

Representative Files

Working Read

This branch is the site-facing companion to the consent and voluntary-intelligence language already appearing in the concept pages and adjacent project work.

The homepage and research copy evolve together, which is why the wiki should keep this as a coherent project family rather than scattering the files into unrelated buckets. The newer essays make the same point from the other side: consentful systems stay expensive because they keep paying attention, and organizational legibility only works when that attention can be witnessed. That also means the branch has an agency dimension: if attention is the cost of remaining consentful, then agency is the capacity that has to survive long enough to keep making the consent meaningful. Governance shows up here as the condition that keeps voluntary intelligence voluntary: if authorization, refusal, and review are not legible, the site language stops being consentful and starts becoming merely decorative. The accounting seam matters too: Accounting for Meaning names the trust burden that appears when language itself becomes consequential, and Responsibility-Bounded Observability explains why the system has to scope observation to the responsibility it is willing to carry. That puts Witness Infrastructure directly in the branch, because consentful systems need continuity and admissibility as much as they need phrasing. The new essay The Loop Requirement sharpens the same basin from the communication side: a statement only becomes durable meaning when uptake is reflected back through interpretation or confirmation. The Voting Machine project is the civic-infrastructure analogue of that claim: consent, refusal, review, and evidence have to stay separable if the system is going to remain trustworthy. Loop mechanics belongs here too, because a voluntary-intelligence system has to remain repairable after drift, not just well phrased at launch. The new The Big Hook essay pushes the same logic outward into business-as-code, while Loopways names the interloop exchange layer that lets consented systems route state without flattening boundaries.

Telic Field Bridge

Relation class: ethical precursor, implementation precursor, and parent-project bridge

Consentful Cybernetics supplies the governing ethical frame for the Telic Field Papers: systems do not merely move toward ends; they recruit attention, energy, data, labor, standing, and future possibility into those ends. Consent determines which recruitment is legitimate.

The later work adds a semantic and relational instrument for making those ends visible before optimization collapses them into one objective.

Consent determines which purposes may legitimately recruit which energies.

Semantic polytelometry belongs here as a candidate capability of voluntary intelligence: the system may help participants compare their expressed telic projections, but it may not own the map, declare their true purpose, or erase unresolved standing.

Related candidate concepts:

Related Links

Attractor Bridge

Next Actions

  1. Keep the site variants and research track separate.
  2. Add more support material only if it clearly belongs to one of those two rails.
  3. Split again only if the site family develops another durable seam.