Dashboard › institutional-transition-lab › Distillation
cb35a7f9-8245-418e-a2d7-ede19f92c717["lore_tm_v1_ZGuadLG17mPeCKhB6kVJ6lXH5u9BpiAm4OsTpSymlNw","lore_tm_v1_bx19vaAI-LUDhEHskTuWyYWsXhIQ1s6ju4iv5nQ5TGY"]
Date: Sep 8, 2026
valkey-github-issue-4276 as open issue valkey-io/valkey#4276, titled [NEW] Valkey Samples Repository, authored by jbrinkman, labeled enhancement, with 2 comments, no assignee or milestone, and no reactions; created 2026-07-28T00:52:23Z, updated 2026-08-10T16:03:48Z, and not closed. (meaning Jul 28–Aug 10, 2026)valkey-github-issue-4276 body explicitly identifies itself as a proposal/RFC rather than an implemented arrangement: “This RFC proposes the design, governance model, and contribution framework for a valkey-io/valkey-samples repository” and “community members can comment on [it] before implementation begins.”valkey-io/valkey-samples governance rights in issue 4276: 1. the TSC appoints initial maintainers; 2. additional maintainers are nominated through the standard process; 3. maintainers review PRs, enforce quality standards, and ensure vendor neutrality; 4. a maintainer approves a new-sample proposal or requests changes before implementation; 5. at least one maintainer reviews implementation for acceptance criteria, vendor neutrality, code/documentation quality, and passing CI; 6. once approved and CI is green, the maintainer merges.4276 proposes a clean-slate migration: start with only README, CONTRIBUTING, MAINTAINERS, LICENSE, and CI workflows; grandfather no existing content; revert existing repository content; and require every contribution to follow proposal → approval → implementation → review → merge.4276 proposes 3 content categories in exact order: 1. cookbooks/ for narrative tutorials with runnable code, including Jupyter notebooks or scripts plus README; 2. demos/ for lightweight applications demonstrating one Valkey use case; 3. samples/ for fuller, production-style integrations that must document where Valkey-specific code resides.README.md, CONTRIBUTING.md, LICENSE using BSD-3-Clause or Apache-2.0, MAINTAINERS.md, .github/ISSUE_TEMPLATE/new-sample.md, .github/ISSUE_TEMPLATE/bug-report.md, .github/PULL_REQUEST_TEMPLATE.md, and workflows validate-samples.yml, lint-markdown.yml, and label-sync.yml; directories are self-contained, remain flat rather than nested by language, and identify language in names such as cache-aside-python/ and cache-aside-java/.4276 runs on every PR and weekly, validating: Markdown with markdownlint; links with lychee or markdown-link-check; per-sample dependency installation using pip, npm, gradle, etc.; language-specific linting; execution against a Valkey Docker container; and a GitHub Actions matrix across samples./home/byk/Code/institutional-transition-lab/schema/governance-coding-v1.schema.json is JSON Schema draft 2020-12 with $id https://github.com/BYK/institutional-transition-lab/schema/governance-coding-v1.schema.json, title Performance-blinded governance coding v1, root "type": "object", and "additionalProperties": false.governance-coding-v1.schema.json requires exactly these named top-level fields: record_class, event_kind, title, announced_on, effective_on, affected_scope, body_patch_relation, power_changes, confidence, and ambiguity.record_class = effective_institutional_change, announced_institutional_change, proposal_only, control_event, no_event, or abstain; event_kind = leadership, board_or_steering, control_rights, reorganization, foundation_transfer, license, fork, reunification, strategy, product, external, or null; body_patch_relation = consistent, patch_supersedes_body, body_only, patch_only, conflict, not_applicable, or unclear.power_changes item must disallow additional properties and require actor, right_kind, target, direction, change_status, scope, and evidence_refs; actor, target, and scope are nonempty strings.right_kind enum is exactly: 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, inform. direction is added, removed, or modified; change_status is effective, announced, proposed, rejected, or unclear.evidence_refs array has minItems: 1; every item disallows additional properties and requires nonempty-string source_id and quote. confidence is numeric from 0 through 1; title, affected_scope, and ambiguity permit string or null; announced_on and effective_on permit date-formatted string or null.