Dashboard › institutional-transition-lab › Distillation
d7982645-6c26-47c8-969e-5fea4cfe00a0["lore_tm_v1_pq4HliaNen-vH1xYZ9hd550fwKna8t2uSK2Lorlled8"]
/home/byk/Code/institutional-transition-lab/cases/review/oss-governance-adjudication-v1/fragments/opentofu-a1.json is a schema-version-1 adjudication fragment with design_status="performance_blinded_llm_assisted_source_adjudication" and exactly 4 OpenTofu records reviewed by opencode-sol-opentofu-a1 (reviewer_type="llm", model openai/gpt-5.6-sol, role source_adjudicator, assistance Source-first review of four frozen OpenTofu records).opentofu-github-issue-1353 (https://github.com/opentofu/opentofu/issues/1353) was accepted from terra_advisory as record_class="no_event" with confidence 0.98, title Proposal for documentation and user interface writing style framework, affected scope OpenTofu technical documentation and user interface writing, announced_on="2024-03-08", effective_on=null, event_kind=null, body_patch_relation="body_only", no power changes, and no graph-edge additions or removals. (meaning March 8, 2024)opentofu-github-issue-1353 is that the issue proposes guidance, tooling, and a process for amending the guidance but allocates no organizational decision right; therefore, the proposed content standard does not alter the institutional power graph. The only audited source was the complete body; no evidence showed adoption or assignment of authority.opentofu-github-issue-2109 (https://github.com/opentofu/opentofu/issues/2109) was accepted from terra_advisory as record_class="no_event" with confidence 0.99, all event metadata null, body_patch_relation="body_only", no power changes, and no graph-edge additions or removals.opentofu-github-issue-2109 is that installing providers from GitHub and bypassing a registry is a software/product capability rather than organizational authority. The sole audited source was the complete body, which supplied no implementation evidence.opentofu-github-issue-2573 (https://github.com/opentofu/opentofu/issues/2573) was accepted from luna_b as record_class="no_event" with confidence 0.99, title Use correct year in Technical Steering Committee (TSC) Summary, announced_on=null, effective_on=null, event_kind=null, affected_scope=null, body_patch_relation="not_applicable", no power changes, and no graph-edge additions or removals.opentofu-github-issue-2573 is that it reports an incorrect year in TSC summaries—a documentation correction rather than an institutional or product-control event. The complete issue body was the sole audited source and was considered sufficient to classify the date error.opentofu-github-issue-258 (https://github.com/opentofu/opentofu/issues/258) was accepted from luna_a as record_class="control_event" and event_kind="product" with confidence 0.98, title Homebrew-like registry design chosen for implementation, affected scope OpenTofu registry design, announced_on="2023-11-03", effective_on=null, body_patch_relation="body_only", no power changes, and no graph-edge additions or removals. (meaning November 3, 2023)opentofu-github-issue-258 is that its 2023-11-03 update says the Technical Steering Committee selected the Homebrew-like registry design for implementation. This exercised existing TSC product-design authority but did not add, remove, or transfer organizational rights. The complete issue body was audited, but linked issue 741 and implementation artifacts were absent, preventing support for an effective implementation date or broader authority change. (meaning November 3, 2023)opentofu-a1.json, source_audit.inspected_before_codings=true; each audit lists only source_ids=["body"], with files_listing_complete=null, patch_selection_truncated=false, patch_unavailable_count=0, and source_text_truncated=false.