Dashboard › institutional-transition-lab › Distillation
9a709754-f964-4edf-a089-cbb2a20ae0f4["lore_tm_v1_IjpWJcs8ciMDIajLg0g0NE-HwJ2pMYPZxvtY4KT6ZdA","lore_tm_v1_Vw2lRiqmLrnTflM0if_LaSxCm6iJJX9S5PmJpeNgUJE","lore_tm_v1_wwBqWeBdGTJAVmnFrLy6H3ek_hlE4CJi6JKjYksT1gY","lore_tm_v1_G8VxJ22JRUvPbEfsoXLFLfvtke_r44XnmQEr2RXTI_E","lore_tm_v1_UHSAtc9fE1__6MSDL8jopkarOqlyKPgj1lADkLBRyTo","lore_tm_v1_8512WsdJlXyNuTQNoH_-4iYVco7sjEUAcIG8w9Ic4yQ","lore_tm_v1_kIULxJ6tqlxU0mJhyaAgJ0kg8XztinwTPNjo3dF2ynE","lore_tm_v1_weC75Mo2L18QamTxDatY1oPASHq37kEdSja4pZQ8VXU","lore_tm_v1_DOQgRO41W0XhNYltOwxi5RDBRmHgi625ylaQtlixmWQ"]
Date: Sep 8, 2026
documents.json = 2a62ab05687982c112a29f6126227c26c3ff8defc89ca64662753aaf85c3c0ce; v1.2-coding-package.json = 14644759f53071adfe1173d4e25bb01931b8c1591fa8a48295dbd0556a754769.src/institution_lab/governance_coding.py defines record classes effective_institutional_change, announced_institutional_change, proposal_only, control_event, no_event, and abstain; institutional/proposal records require nonempty power_changes, non-institutional records must have no power_changes, and abstain requires non-null ambiguity.src/institution_lab/governance_coding.py defines right kinds appoint, remove, elect, vote, delegate, override, approve, merge, write, release, veto, own, license, steward, fund, set_budget, set_strategy, set_policy, set_membership, set_terms, and inform; directions are added, removed, or modified; statuses are effective, announced, proposed, rejected, or unclear.validate_response() in src/institution_lab/governance_coding.py requires exactly RESPONSE_KEYS, ISO dates or null, confidence from 0 through 1, and exact POWER_KEYS; every power-change evidence reference must contain exactly source_id and quote, and the verbatim quote must occur in the referenced source text.valkey-github-issue-2961 (valkey-io/valkey, published 2025-12-22, 2,124-byte/39-line body); index 31 valkey-github-issue-3289 (published 2026-03-02, 4,937-byte/49-line body); and index 32 valkey-github-issue-3441 (published 2026-04-03, 8,656-byte/137-line body). Each has exactly one source component, source_id: "body", with source_text_truncated: false, files_listing_complete: null, patch_selection_truncated: false, and patch_unavailable_count: 0.valkey-github-issue-2961 proposes kernel-level hot-key detection and processing: detection within 1 second, custom thresholds, low CPU/memory overhead, dynamic enable/disable and sampling/threshold controls, read/write distinction, real-time external notifications, and access-frequency/trend monitoring.valkey-github-issue-2961 considered 2 alternatives: (1) Monitor command statistics—rejected for poor real-time performance, inability to detect issues in advance, and high resource use; (2) proxy-side or SDK-side implementation—rejected because distributed operation reduces accuracy.valkey-github-issue-3289 proposes a formal Valkey Improvement Proposal (VIP) framework for major Core, Modules, Clients, and Tooling changes, complementing rather than replacing lightweight workflows for minor changes and bug fixes.[DISCUSS] VIP-{number} {heading} thread in Valkey Contributors Slack and iterate; 4. call a [VOTE]; 5. update the VIP page/index to Accepted or Rejected and report the result to the voting thread.Lazy Consensus—3 binding +1 votes and no binding vetoes; Lazy Majority—3 binding +1 votes and more binding +1 than -1; Lazy Approval—allowed unless a -1 triggers lazy majority or lazy consensus; 2/3 Majority—at least two-thirds of binding vote holders, active committers or TSC members, vote +1, reserved for foundational changes. Anyone intending to drive or contribute implementation may initiate a VIP.valkey-github-issue-3289 considered 3 alternatives: (1) continue the informal RFC process—rejected for insufficient structure, visibility, and clear approval mechanisms; (2) GitHub Issues/Discussions only—rejected because they lack an inherent numbered, indexed, lifecycle-tracked system; (3) fully custom process—rejected as greater effort without clear benefit over adapting Apache Kafka’s KIP model.valkey-github-issue-3441 source states avifenesh/valkey-skills contains 15 skills, 281 files, and 37K lines of source-verified material; baseline versions are Valkey 9.0.3, GLIDE 2.3.0, valkey-search 1.2.0, valkey-bloom GA, and Spring Data Valkey 1.0.valkey improved Sonnet 4.6 from 6/14 to 10/14 (+4) and Opus 4.6 from 5/14 to 10/14 (+5); valkey-dev improved Sonnet 4.6 from 8/12 to 11/12 (+3), while Opus was excluded for exceeding the turn cap; valkey-ops improved Opus 4.6 Helm performance from 16/19 at $2.50 to 18/19 at $1.57 (+2, 37% cheaper) and Sonnet 4.6 config performance from 16/22 to 17/22 (+1).valkey-module-dev because its Rust crate was already in training data, valkey-json-dev because the C++ code was navigable without guidance, and the query-syntax skill because it was identical to RediSearch.valkey-skills maintenance model is a normal valkey-io repository with its own MAINTAINERS.md and PR workflow; the source author offers to be initial maintainer, with domain maintainers reviewing accuracy and the source author handling skill architecture, routing, and formatting.valkey-skills repository to attract maintainers faster than other repositories in the organization.valkey-skills: CI-based release tracking; release PRs automatically opening issues with release notes; commit-based version pinning for Codex and Claude Code; tags and immutable releases; agnix reporting 0 errors and 0 warnings; source verification via repo-intel and consumer plugins; and reproducible benchmarks requiring additions to demonstrate value.valkey-github-issue-3441 presents 4 repository-structure options in order: 1. Option A, cross-link only—no new governed repo, but unofficial and less discoverable; 2. Option B, one valkey-io/valkey-skills repository—recommended for unified discovery, tooling, architecture, and modern-project signaling, but adds a repository to govern; 3. Option C, distribute skills among respective repositories—places skills near code, but risks fragmentation, inconsistency, 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 risks lagging releases despite existing benchmarks. Recommendation is B, with D as a stepping stone if gradual adoption is preferred.valkey-skills, in order: 1. distill key knowledge and prewritten diagnostic tools into a lean official plugin for Claude Code, Cursor, Codex, and Copilot marketplaces; 2. build extensions for VS Code, Neovim, JetBrains, and Zed; 3. synchronize skill updates with Valkey, GLIDE, and module releases.