Dashboard › institutional-transition-lab › Distillation
4b80a7f3-0e4d-4677-a00c-a1cbec40b6bc["lore_tm_v1_RLC2s3lvhZxaQkokixZae2eo1BfYhzgYQYGO5_IPETU","lore_tm_v1_YRJMmHny8j00_ePScRH9cZtEwW74TwiwAghTBd1BQEQ","lore_tm_v1_sIJiCgrsk7gy3GBAsCwLdp3QwfGq3sGpVVebaG6swbQ","lore_tm_v1_qfWaQCJ3dfeSz0KzVNL9X4dES7NRm-C5QZIRuld5T8k"]
valkey-github-issue-3289: terra_advisory codes a proposal_only/control_rights event announced 2026-03-02, scope “Major changes to Valkey's Core, Modules, Clients, and Tooling,” body_patch_relation: body_only, confidence 0.98; proposed edge adds voting power to “binding vote holders (active committers or TSC members)” over foundational project changes through a 2/3 Majority, evidenced by the exact body table row. (meaning March 2, 2026)valkey-github-issue-3441: luna_b codes a proposal_only/foundation_transfer event announced 2026-04-03, scope valkey-skills repository, body_patch_relation: body_only, confidence 0.98; proposed edge gives valkey-io ownership of valkey-io/valkey-skills, while ambiguity notes multiple options remain and the TSC has not decided. (meaning April 3, 2026)valkey-github-issue-4508: terra_advisory codes a proposal_only/control_rights event announced 2026-08-24, scope valkey-io/langchain-valkey repository and @langchain/valkey package, body_patch_relation: body_only, confidence 0.88; proposed edge gives valkey-io stewardship over hosting and community maintenance of the package, with no evidence that approval, repository creation, or stewardship transfer took effect. (meaning August 24, 2026)valkey-github-issue-4509: luna_b codes a proposal_only/control_rights event announced 2026-08-24, scope n8n Valkey Vector Store community node repository, body_patch_relation: body_only, confidence 0.98; proposed edge gives valkey-io stewardship over repository hosting and long-term maintenance of n8n-nodes-valkey, based on body statements proposing valkey-io/n8n-nodes-valkey and describing official endorsement and maintenance commitment. (meaning August 24, 2026)valkey-github-pr-1390: terra_advisory codes an effective_institutional_change/control_rights event announced 2024-12-04 and effective 2024-12-09, scope Valkey project repositories, body_patch_relation: consistent, confidence 0.88; effective edges add repository-code write rights for Harkrishn Patro (hpatro) and Ran Shidlansik (ranshid) and governance ownership for Maintainers. Ambiguity: the patch distinguishes committers from maintainers but does not explicitly identify any rights removed from existing individuals. (meaning December 4-9, 2024)valkey-github-pr-345: luna_b codes an effective_institutional_change/board_or_steering event announced 2024-04-21 and effective 2024-04-30, scope “Valkey project and all current and future repositories under the Valkey-io organization,” body_patch_relation: consistent, confidence 0.99; effective TSC rights are, in order: 1. Set TSC membership through no less than a 2/3 affirmative vote; 2. Appoint a Chair; 3. Amend the governance document through no less than a 2/3 affirmative vote; 4. Delegate other-project decision-making to those projects’ maintainers; 5. Override decisions made by other projects within the Valkey organization. (meaning April 21-30, 2024)valkey-github-issue-4276 all abstain: luna_a confidence 0.9, title [NEW] Valkey Samples Repository; luna_b confidence 0.72, title RFC for Valkey Samples Repository; terra_advisory confidence 0.88, title Valkey Samples Repository. All use event_kind: control_rights, body_patch_relation: body_only, no power changes, and cite truncation in the governance section plus absent implementation/patch evidence as the reason rights cannot be resolved from the frozen packet.valkey-github-pr-1788: luna_a codes a merged control_event/license event effective 2025-02-27, body_patch_relation: consistent, confidence 0.91, treating visible changes as standardized file-license headers; luna_b abstains with body_patch_relation: unclear, confidence 0.55; terra_advisory abstains with body_patch_relation: unclear, confidence 0.38. All flag truncated patch selection; the abstentions state visible excerpts cannot establish whether licensing terms or associated rights materially changed. (meaning February 27, 2025)valkey-github-pr-2927 all code an effective_institutional_change effective 2025-12-12: luna_a uses event_kind: control_rights, body_patch_relation: patch_supersedes_body, confidence 0.96; luna_b uses event_kind: board_or_steering, body_patch_relation: consistent, confidence 0.98; terra_advisory uses event_kind: board_or_steering, body_patch_relation: patch_supersedes_body, confidence 0.92. (meaning December 12, 2025)valkey-github-pr-2927 candidate edges collectively identify: technical-major-decision approval by simple majority; fallback approval after two weeks through explicit +2 support from at least two TSC members if no member votes against; governance-major-decision approval by 2/3 of the entire TSC; a cap preventing more than 1/3 of the TSC from representing one organization or affiliated organizations, with prompt restoration action including removal or reassignment; involuntary TSC-member removal through the Governance Major Decision process; and delegation of project decision-making as a Governance Major Decision. luna_a includes five edges but omits the explicit +2 fallback; luna_b includes the fallback but omits composition and delegation edges; terra_advisory combines fallback language into technical approval and includes composition and delegation but omits a separate removal edge.valkey-github-issue-3289 proposes the Valkey Improvement Proposal (VIP) process for major changes to Core, Modules, Clients, and Tooling. Lifecycle, in order: 1. Create a numbered VIP; 2. Complete required sections and add it to an index; 3. Start a [DISCUSS] VIP-{number} {heading} Slack thread and iterate transparently; 4. Call a [VOTE], ordinarily using lazy majority with 3 binding +1 votes, more +1 than -1, and a minimum 72/96-hour voting window; 5. Update the VIP page/index and report Accepted/Rejected status.valkey-github-issue-3289 defines approval modes: Lazy Consensus = 3 binding +1 votes and no binding vetoes; Lazy Majority = 3 binding +1 votes and more binding +1 than -1; Lazy Approval = implicit approval unless a -1 triggers Lazy Majority or Lazy Consensus; 2/3 Majority = at least 2/3 of binding vote holders, defined as active committers or TSC members, voting +1, reserved for foundational project changes.valkey-github-issue-3289 alternatives, in order: 1. Continue the informal RFC process—rejected because it lacks structure, visibility, clear voting, and consistent review; 2. GitHub Issues/Discussions only—rejected because they do not inherently provide numbered, indexed lifecycle tracking for major architecture changes; 3. Build a fully custom process—rejected as more effort without clear benefit over adapting the Kafka Improvement Proposal (KIP) model. The proposed VIP process complements rather than replaces lightweight workflows for minor changes and bug fixes.valkey-github-issue-3441 states valkey-skills contains 15 skills, 281 files, and 37K lines of source-verified material. Benchmarks reported: valkey—Sonnet 4.6 improved 6/14 → 10/14 (+4) and Opus 4.6 improved 5/14 → 10/14 (+5); valkey-dev—Sonnet 4.6 improved 8/12 → 11/12 (+3); valkey-ops—Opus 4.6 Helm improved 16/19 ($2.50) → 18/19 ($1.57), +2 and 37% cheaper, while Sonnet 4.6 config improved 16/22 → 17/22 (+1). Opus was excluded from the valkey-dev benchmark after exceeding the turn cap.valkey-github-issue-3441 reports three skills removed after showing no benchmark improvement: 1. valkey-module-dev because the Rust crate was already in training data; 2. valkey-json-dev because the C++ code was navigable without guidance; 3. A query-syntax skill because its syntax was identical to RediSearch.valkey-github-issue-3441 proposes the same maintenance model as other valkey-io repositories: its own MAINTAINERS.md and PR workflow; the proposer would serve as initial maintainer, domain maintainers would validate accuracy, and the proposer would handle skill architecture, routing, and formatting. CI-based version tracking would auto-open issues from release PRs; commit-based versioning would allow version pinning; tags and immutable releases would provide stable anchors.valkey-github-issue-3441 quality tooling: agnix linter with 0 errors, 0 warnings, updated weekly against major AI labs; source verification using repo-intel and consumer plugins; reproducible benchmarks requiring additions to prove value.valkey-github-issue-3441 repository-structure options, in order: 1. Option A, cross-link only—no new governed repository, but unofficial and less discoverable; 2. Option B, a single valkey-io/valkey-skills repository—recommended for unified discovery, tooling, architecture, and official signaling, though it adds a repository to govern; 3. Option C, distribute skills among existing repositories—places skills near code but risks fragmentation, inconsistency, missed discovery, and no natural home for cross-cutting migration skills; 4. Option D, phased adoption beginning with valkey, GLIDE, valkey-dev, and ops—smaller initial scope but delays already-benchmarked material. Recommendation: B, with D as a stepping stone if gradual adoption is preferred; final structure remains for the TSC to decide.valkey-github-issue-3441 proposed next steps, in order: 1. Distill key knowledge and prewritten diagnostic tools into an official marketplace skill for Claude Code, Cursor, Codex, and Copilot; 2. Build extensions for VS Code, Neovim, JetBrains, and Zed; 3. Update skills in sync with Valkey, GLIDE, and module releases. Existing repository: avifenesh/valkey-skills, licensed BSD-3-Clause.valkey-github-issue-4508 proposes valkey-io/langchain-valkey to host @langchain/valkey, a standalone LangChainJS VectorStore implementation using Valkey Search and valkey-glide. Existing implementation capabilities: KNN and range-query vector search; TAG/TEXT/NUMERIC metadata filters; custom index schemas; batch pipeline writes; escaped TAG values against query injection; configurable index prefixes and COSINE/IP/L2 distance metrics.valkey-github-issue-4508 alternatives: 1. Personal/company organization—rejected for lower discoverability and trust; 2. Existing valkey-io repository—rejected because the standalone NPM package has its own build, test, and release lifecycle; 3. Wait for LangChainJS to resume in-repository integrations—rejected because maintainers and guidelines permanently direct new integrations to independent packages. The starting implementation is in daric93/langchainjs, branch feature/valkey-vector-store, path libs/providers/langchain-valkey/; upstream PR langchain-ai/langchainjs#9915 ran February-May 2026 with 8 commits and a completed security review.valkey-github-issue-4509 proposes valkey-io/n8n-nodes-valkey, a standalone n8n-nodes-valkey NPM community node depending on @langchain/valkey and indirectly valkey-glide. Proposed operations are Insert, Load, Get, and Retrieve (as Tool); target capabilities include KNN/range vector search, TAG/TEXT/NUMERIC filtering, automatic-embedding ingestion, Agent Tool retrieval, and self-hosted or managed Valkey support including AWS ElastiCache, GCP Memorystore, and Aiven.valkey-github-issue-4509 alternatives: 1. Fix n8n’s existing Redis node—rejected because n8n explicitly declines compatible-database support and closed the issue as an enhancement; 2. Use the LangChain Code Node workaround—rejected because it requires JavaScript, is self-hosted-only, and lacks visual workflow integration; 3. Host under a personal organization—rejected for reduced discoverability, trust, official endorsement, long-term maintenance, and n8n verification prospects. @langchain/valkey from issue #4508 is a prerequisite and langchain-valkey should be created first; the SAP HANA Vector Store node is cited as the package-structure reference.