Distillation

Date: September 8, 2026

• 🟡 (19:04) Source record valkey-github-pr-1390, published December 4, 2024 and merged December 9, 2024 as merge commit 4f61034934cf165163ef272e5795bccadc288b09, updated GOVERNANCE.md and MAINTAINERS.md to separate committers from maintainers while preserving balance among corporate interests. (meaning December 4-9, 2024)
• 🟡 (19:04) valkey-github-pr-1390 defines committers as individuals with repository write access and maintainers as individuals with full repository access who own its governance; both groups should be clearly listed in each repository’s MAINTAINERS.md, while maintainers of other Valkey repositories are not TSC members unless explicitly added.
• 🟡 (19:04) valkey-github-pr-1390 added a Current Committers section listing Harkrishn Patro (hpatro, Amazon) and Ran Shidlansik (ranshid, Amazon), and renamed Former Maintainers to Former Maintainers and Committers.
• 🟡 (19:10) Source record valkey-github-pr-2927, published December 11, 2025 and merged December 12, 2025 as merge commit cd6faaa726791447f7adc196b6c77cc20658112d, refined major-decision procedures and TSC composition rules in GOVERNANCE.md. (meaning December 11-12, 2025)
• 🟡 (19:10) valkey-github-pr-2927 imposed a TSC composition cap: no more than one third (1/3) of members may represent the same organization or affiliated organizations. The TSC must be notified promptly if the limit is exceeded, act promptly to restore compliance, strive to resolve it within 30 days, and document the remedial steps.
• 🟡 (19:10) valkey-github-pr-2927 split major decisions into: 1. Technical Major Decisions—fundamental core-data-structure changes, new data structures/APIs, backward-compatibility changes, maintained user-visible fields, and external libraries affecting runtime behavior; 2. Governance Major Decisions—adding or involuntarily removing TSC members, modifying GOVERNANCE.md, delegating maintainership or governance authority, creating/modifying/removing roles, changing voting rules or oversight, and structural TSC changes including composition limits.
• 🟡 (19:10) Technical-major-decision procedure in valkey-github-pr-2927: use a simple majority when obtainable; if none is reached within a two-week voting period and no TSC member votes against, explicit +2 support from at least 2 TSC members may approve the proposal; a TSC-member proposer’s +1 counts toward +2; any negative vote disables +2; concerns after +2 approval require a new major-decision process rather than direct retraction.
• 🟡 (19:10) Governance-major-decision procedure in valkey-github-pr-2927: approval requires a 2/3 affirmative vote of the entire TSC. Other votes generally require a simple majority of voting members, and ties preserve the status quo.
• 🟡 (19:10) valkey-github-pr-2927 revised membership termination to: 1. Involuntary Removal through the Governance Major Decision process; 2. Resignation by written notice; 3. Unreachable Member removal by simple majority after more than six months of unresponsiveness. Delegation of project decision-making was explicitly classified as a Governance Major Decision.
• 🟡 (19:10) Source record valkey-github-pr-345, published April 21, 2024 and merged April 30, 2024 as merge commit b283c6b508792892d76b9a4911e3086e37518748, created the initial Valkey governance framework across GOVERNANCE.md, CONTRIBUTING.md, and MAINTAINERS.md. (meaning April 21-30, 2024)
• 🟡 (19:10) Initial governance in valkey-github-pr-345: the Valkey TSC comprised maintainers of the main valkey repository and oversaw all technical, project, approval, and policy matters; other-repository maintainers were excluded unless explicitly added; adding/removing maintainers or TSC members and amending governance required at least a 2/3 affirmative TSC vote.
• 🟡 (19:10) Initial voting rules in valkey-github-pr-345: strive for documented consensus without requiring explicit unanimity; call votes when consensus fails or an issue/PR is marked a major decision; any TSC member may call a vote with separate discussion and voting periods; discussions are public except embargoed security matters and maintainer additions/removals; each member has one vote; voting remains open at least two weeks; ordinary decisions use a simple majority.
• 🟡 (19:10) Initial major-decision examples in valkey-github-pr-345, in order: 1. Fundamental changes to Valkey core data structures; 2. Adding a new data structure or API; 3. Backward-compatibility changes; 4. New user-visible fields requiring maintenance; 5. TSC or governance-document modifications; 6. Adding members to other project roles; 7. Delegating project maintainership; 8. Adding or removing an external library such as a client or module.
• 🟡 (19:10) Initial termination rules in valkey-github-pr-345: resignation by written notice, removal by 2/3 TSC vote, or simple-majority removal after more than six months of unresponsiveness.
• 🟡 (19:10) Initial MAINTAINERS.md in valkey-github-pr-345 listed 6 maintainers alphabetically by GitHub ID: Zhu Binbin (enjoy-binbin, Tencent), Wen Hui (hwware, Huawei), Madelyn Olson (madolson, Amazon), Ping Xie (pingxie, Google), Zhao Zhao (soloestoy, Alibaba), and Viktor Söderqvist (zuiderkwast, Ericsson).
• 🟡 (19:11) Source record valkey-github-pr-1788, published and merged February 27, 2025 as merge commit 089b830479f4984e77e570560f85e37212879740, standardized licensing across 31 changed files; its patch selection is truncated, while the source body is complete and no patches are unavailable. (meaning February 27, 2025)
• 🔴 (19:11) User stated the convention “always explicitly first”: licenses are placed before documentation in files.
• 🟡 (19:11) valkey-github-pr-1788 standardized Valkey notices to Copyright (c) Valkey Contributors, All rights reserved., and SPDX-License-Identifier: BSD-3-Clause; it added SPDX-License-Identifier: BSD-3-Clause to COPYING, corrected malformed BSD 3-Clause identifiers, and moved license blocks ahead of file documentation.
• 🟡 (19:11) Visible files affected by valkey-github-pr-1788 include COPYING, deps/fast_float_c_interface/fast_float_strtod.cpp, src/allocator_defrag.c, src/asciilogo.h, src/blocked.c, src/cluster.c, src/cluster_legacy.c, src/cluster_slot_stats.c, src/commandlog.c, src/defrag.c, src/dict.c, src/eval.c, src/expire.c, src/functions.c, src/hyperloglog.c, src/io_threads.c, src/lua/engine_lua.c, src/memory_prefetch.c, src/module.c, and src/rdb.c.
• 🟡 (19:11) Assistant reported completing the source pass and beginning exact source-to-candidate comparison, with schema-invalid and ungrounded model responses to be excluded before final adjudication construction.
• 🟡 (19:12) Adjudication task status: 1. Read protocol/coding schema and note rules/ambiguities—completed, high priority; 2. Inspect complete frozen metadata, bodies, and patches for all 10 records before model codings—completed, high priority; 3. Inspect named frozen model responses against source evidence—in progress, high priority; 4. Construct complete final coding objects and graph-edge revisions—pending, high priority; 5. Validate objects against the schema and deliver compact JSON plus summary—pending, high priority.
• 🟡 (19:12) Inspected adjudication output’s top-level keys: records, schema_version, and summary.
• 🟡 (19:13) Inspected per-record adjudication keys: canonical_ledger_eligible, full_response_agreement, luna_a, luna_b, provisional_core_agreement, record_id, route_reasons, source_url, and terra_advisory.