Distillation

Date: Sep 8, 2026

• 🟡 (21:51) Review data came from /home/byk/Code/institutional-transition-lab/cases/review/oss-governance-adjudication-v1/v1.2-coding-package.json, a 4,085-line coding package.
• 🟡 (21:52) OpenTofu PR record opentofu-github-pr-2830 was classified by both gpt-5.6-luna runs and the gpt-5.6-terra advisory as an effective_institutional_change, announced 2025-05-20 and effective 2025-05-23; all noted that the selected patch was truncated. The record lacked provisional core/full-response agreement and was routed for body_patch_relation_disagreement, bounded_evidence, edge_disagreement, and event_field_disagreement.
• 🟡 (21:52) For opentofu-github-pr-2830, Luna A used title “OpenTofu adopts Charter and Governance structure,” event_kind: control_rights, body_patch_relation: consistent, and confidence 0.98. It coded 5 added TSC/LF Projects powers: 1. TSC set_strategy over technical oversight and direction of the OpenTofu project; 2. TSC approve a Contributor becoming a Committer; 3. TSC remove a Committer by majority approval; 4. TSC elect a TSC Chair; 5. LF Projects own OpenTofu Project Trademarks.
• 🟡 (21:52) For opentofu-github-pr-2830, Luna B used title “OpenTofu Charter and Governance adopted,” event_kind: board_or_steering, body_patch_relation: patch_supersedes_body, and confidence 0.96. It coded 5 added TSC powers: 1. approve a Contributor becoming a Committer; 2. remove a Committer; 3. appoint representatives to work with other open-source/open-standards communities or organizations working with the Project; 4. delegate decision-making authority to maintainers of specific projects under the OpenTofu GitHub organization; 5. override those maintainers’ decisions.
• 🟡 (21:52) For opentofu-github-pr-2830, the Terra advisory used title “OpenTofu Charter and Governance,” event_kind: board_or_steering, body_patch_relation: consistent, and confidence 0.89. It coded 3 added TSC powers: 1. approve promotion of a Contributor to Committer; 2. remove a Committer; 3. override decisions across all projects in the OpenTofu organization. It tied effectiveness to merge metadata showing merged_at: 2025-05-23T12:18:56Z.
• 🟡 (21:52) The visible charter evidence for opentofu-github-pr-2830 stated: “The Technical Steering Committee (the ‘TSC’) will be responsible for all technical oversight of the open source Project”; “A Contributor may become a Committer by approval of the TSC”; “A Committer may be removed by a majority approval of the TSC”; “The TSC may elect a TSC Chair”; “LF Projects will hold title to all trade or service marks used by the Project”; the TSC may appoint external representatives and delegate authority to project maintainers; and the TSC has ultimate authority and retains the right to overrule decisions.
• 🟡 (21:52) OpenTofu PR record opentofu-github-pr-2953 concerned moving governance documents and TSC notes to opentofu/org. It was not canonical-ledger eligible, lacked full-response/provisional-core agreement, and was routed for abstention, bounded_evidence, and low_confidence; all 3 model responses returned record_class: abstain with no power_changes.
• 🟡 (21:52) For opentofu-github-pr-2953, Luna A used title “Governance documents moved to opentofu/org,” scope “OpenTofu governance documents,” event_kind: reorganization, body_patch_relation: consistent, confidence 0.7, announced 2025-06-24, and effective 2025-06-25. It found document relocation but no established organizational-rights change and noted omitted PR patches.
• 🟡 (21:52) For opentofu-github-pr-2953, Luna B used title “OpenTofu governance documents moved to opentofu/org,” scope “OpenTofu governance documentation,” event_kind: reorganization, body_patch_relation: consistent, confidence 0.58, announced 2025-06-24, and effective 2025-06-25. It emphasized that patch selection was truncated despite exactly 43 changed files, leaving open whether omitted changes contained an organizational-rights change.
• 🟡 (21:52) For opentofu-github-pr-2953, the Terra advisory used title “Move governance references to opentofu/org,” scope “OpenTofu governance documentation and TSC notes,” body_patch_relation: unclear, confidence 0.42, and left announced_on, effective_on, and event_kind null. It found visible relocation but no established change in organizational rights and warned that omitted patches from the 43-file PR could materially affect the conclusion.