Dashboard › institutional-transition-lab › Distillation
d9e50240-ddad-4ed7-aaa1-b83afb864594["lore_tm_v1_chcVYS5StVAJNCdkDh7qW3DifcP1jDDxJ-w0JE9rb30"]
Date: Sep 9, 2026
/home/byk/Code/institutional-transition-lab/cases/review/oss-governance-adjudication-v1/v1.2-coding-package.json, lines 1950–2749 of 4085.valkey-github-issue-2961, the supplied package shows disagreement over a Valkey kernel-level hot-key-detection request: luna_a coded control_event/product, title Proposal for Valkey kernel-level hot key detection, affected scope Valkey hot key detection and processing, announced 2025-12-22, body_patch_relation=body_only, confidence 0.98, and no effective date or power changes; luna_b coded control_event/product, title Proposal for kernel-level hot key detection in Valkey, affected scope Valkey hot key detection, processing, and monitoring, announced 2025-12-22, body_patch_relation=not_applicable, confidence 0.98, and no effective date or power changes; terra_advisory coded no_event, title Valkey kernel-level hot key detection function request, body_patch_relation=not_applicable, confidence 0.99, with no dates, event kind, affected scope, or power changes. The route reason is body_patch_relation_disagreement, and canonical_ledger_eligible=false. (meaning December 22, 2025)2026-03-02, luna_a and luna_b both coded a non-effective proposal_only/control_rights event concerning major or foundational Valkey changes, with body_patch_relation=body_only and no effective date. Both proposed adding a vote power requiring a 2/3 majority of binding vote holders—active committers or TSC members—to approve foundational changes; luna_a confidence is 0.99, and luna_b confidence is 0.98. Both state there is no evidence the proposed voting and approval process was adopted or implemented. (meaning March 2, 2026)