Dashboard › institutional-transition-lab › Distillation
eb2022cf-becb-481c-9ef3-e0df06f672b9["lore_tm_v1_K9fP2e7eSDjSbqZnH56DM1MV-aCUWmYfBMsisgWwTAk","lore_tm_v1_LvUleN_9xknRe6Bij5PaMsHJ1dOYvSle_9YAIT72cTw","lore_tm_v1_6ev2TuxCCz8LJgCh_TYmUrxwRluhu9O6YMYXeMfsps0","lore_tm_v1_Rrvm5o03HYBSvf7FuimhgwpK9gM08J2zoVANUNnHdU8"]
/tmp/opencode/valkey-36-40.json, schema version 1, design status performance_blinded_llm_assisted_source_adjudication, containing 5 independently source-adjudicated Valkey records by reviewer opencode-gpt-5.6-sol-valkey-b (openai/gpt-5.6-sol, role source_adjudicator).valkey-github-issue-4509 was adjudicated reject: final coding no_event / product, title “Proposal to create n8n-nodes-valkey repository,” no announced or effective date, scope proposed valkey-io/n8n-nodes-valkey repository and n8n-nodes-valkey package, body_patch_relation: "body_only", no power changes, confidence 0.96. The proposed valkey-io stewardship edge was removed because repository placement, endorsement, maintenance, governance files, and review conventions did not expressly grant an organizational decision right.valkey-github-issue-4509 evidence was limited to the untruncated issue body; the frozen envelope provided no issue state, approval, repository creation, package publication, or implementation evidence.valkey-github-pr-1390 was adjudicated revise: final coding effective_institutional_change / control_rights, title “Valkey adds two committers with repository-code write access,” scope Valkey project repositories, body_patch_relation: "consistent", confidence 0.96.valkey-github-pr-1390 announced the committer change on 2024-12-04. (meaning December 4, 2024)valkey-github-pr-1390 effectively granted repository-code write access to Harkrishn Patro (hpatro, Amazon) and Ran Shidlansik (ranshid, Amazon) on merge. (meaning December 9, 2024)valkey-github-pr-1390, the proposed effective Maintainers → own → governance edge was removed: the new definition said maintainers have full repository access and own governance, but the frozen source did not prove that the PR newly granted this authority rather than clarifying the pre-existing TSC role.valkey-github-pr-1788 was adjudicated revise: final coding control_event / license, title “Standardized Valkey file license headers,” scope limited to license headers in the retained Valkey file patches, no power changes, confidence 0.86.valkey-github-pr-1788 metadata reported 31 changed files, but only 20 patches were retained; patch_selection_truncated: true left 11 file patches unavailable for assessment, preventing a repository-wide claim about every changed file or licensing rights.valkey-github-pr-2927 was adjudicated revise: final coding effective_institutional_change / board_or_steering, title “Valkey TSC membership and major-decision rules revised,” scope Valkey Technical Steering Committee membership and major-decision procedures, body_patch_relation: "patch_supersedes_body", confidence 0.98.valkey-github-pr-2927 was announced on 2025-12-11. (meaning December 11, 2025)valkey-github-pr-2927 became effective on merge and modified six TSC powers: (1) technical-major-decision approval by simple majority when obtainable; (2) an added fallback allowing explicit +2 support from at least two TSC members after a two-week voting period when no simple majority and no negative vote exist; (3) governance-major-decision approval by a 2/3 affirmative vote of the entire TSC; (4) membership composition capped so no more than 1/3 of members represent the same or affiliated organizations; (5) involuntary member removal through the Governance Major Decision process; and (6) delegation to maintainers of other Valkey-organization projects, with delegation itself treated as a Governance Major Decision. (meaning December 12, 2025)valkey-github-pr-2927, the merged patch superseded the PR body’s proposed simple-majority treatment of non-technical decisions by classifying governance matters and requiring a 2/3 vote.valkey-github-pr-345 was adjudicated revise: final coding effective_institutional_change / board_or_steering, title “Valkey governance establishes Technical Steering Committee,” scope Valkey project and all current and future repositories under the Valkey-io organization, body_patch_relation: "consistent", confidence 0.99.valkey-github-pr-345 was announced on 2024-04-21. (meaning April 21, 2024)valkey-github-pr-345 established the Technical Steering Committee with six effective rights: (1) set policy across all Valkey technical, project, approval, and policy matters; (2) add or remove maintainers/TSC members by at least a 2/3 affirmative vote; (3) appoint a Chair to organize TSC meetings; (4) amend the governance document by at least a 2/3 affirmative vote; (5) delegate decision-making for other Valkey-organization projects to their maintainers; and (6) override decisions made by those other projects, while showing restraint. (meaning April 30, 2024)valkey-github-pr-345, adjudication retained five rights from luna_b and added the omitted project-wide set_policy edge covering technical, project, approval, and policy matters.cases/review/oss-governance-adjudication-v1/fragments/valkey-36-40.json.8 fragments and 33 records, with exact decision counts: 4 abstain, 19 accept, 3 reject, and 7 revise.opentofu-10-18.json, opentofu-a1.json, opentofu-a2.json, opentofu-pr-1650.json, terraform-c.json, valkey-31-33.json, valkey-34-35.json, and valkey-36-40.json.retained_in_frozen_order was false.1-18, 22, 25, 26, and 29-40.terraform-github-issue-22468, terraform-github-issue-34139, terraform-github-issue-35563, terraform-github-pr-21345, terraform-github-pr-22332, terraform-github-pr-34096, and terraform-github-pr-34103.opentofu-github-pr-2830, opentofu-github-pr-2953, opentofu-github-pr-2959, and valkey-github-issue-4276.33/40: all 18 OpenTofu records, all 10 Valkey records, and 5 Terraform records. It stated that seven Terraform records remained and four explicit abstentions kept the gate closed.