wiki/concepts/governance-diad

Governance Diad

wiki/concepts/governance-diad/index.md

Rendered from markdown source. Open raw source on GitHub.

Governance Diad

Working definition: a two-sided governance pattern that pairs witness and rule so living documents can stay legitimate without collapsing into static hierarchy.

This concept appears in the SCT story and origin/governance pages, where document stewardship is described as a dyadic protocol rather than a generic policy bucket. It also appears as the story-side governance page itself, which makes the concept visible both as theory and as branch structure.

In practice, Governance Diad is the minimal structure for recognizing authority. Witness establishes what can be certified, and governance names the rule that follows from that certification. The point of the diad is not bureaucracy; it is to keep authority legible without collapsing into either raw observation or raw command. The Contextual Authority Principle sharpens the same seam: authority should stay local, temporary, skill-indexed, and revocable so the diad can keep reducing uncertainty without turning into permanent dominance.

The concept is useful because it refuses to flatten legitimacy into either raw observation or raw command. A witness alone does not create a durable rule, and a rule without witness is just assertion. The diad keeps those forces paired so the corpus can talk about authority without drifting into abstraction. That same pairing is what makes the concept adjacent to consent and provenance work: authority is only meaningful here if it can be witnessed, consented to, and carried through a legible lineage. The Consentocracy Bridge is the external essay that makes that governance move explicit.

That is why Governance Diad sits next to Witnessing, Intent-Consent, LoopLink, and POLEMEMELOP. It is the point where procedural trust becomes a governable pattern, and where SCT’s authority logic becomes readable as a branch-level stewardship model.

ACT–POLICY fits the same seam at the executable layer: it turns act, policy, witness, and state into a compact decision grammar that can be routed through the governance diad without flattening the difference between permission and observation.

The same pattern also appears downstream in Voting Machine, where eligibility witness and ballot rule must stay paired without collapsing identity into the vote record.

Related Artifacts

Related Pages

Attractor Bridge

Notes

  • This is a concept page, not a canon claim.
  • Keep it distinct from generic governance language.
  • Split only if a second stewardship seam becomes durable on its own.