Dashboard › institutional-transition-lab › Distillation
1c7080c9-c9f7-4edb-b27e-621912f4e448["lore_tm_v1_ejLg74vp8L3k749QHeHuydd2d2hjG1LDHA1wF9CXVSE","lore_tm_v1_Toqbv0gdhc_hzVp0AJKsogWXcVTugTr3CyOrUtislEA","lore_tm_v1_YCoLmS7m8Ti-36hBWuzOwveT9IHTVYkKy6lOO4lU7o4","lore_tm_v1_BgT-gLB8nBnPTlqYkk6aJcARaKU-8wdCU1CKsPyIjr8"]
Date: Sep 8, 2026
valkey-github-issue-4509 were inspected. luna_a classified it as proposal_only / control_rights, body_only, announced 2026-08-24, no effective date, confidence 0.98; proposed power change: valkey-io gains steward rights over repository hosting and long-term maintenance for the proposed valkey-io/n8n-nodes-valkey repository. Its ambiguity states the repository and stewardship arrangement are proposed with no implementation evidence. The response was schema-invalid because its sole evidence quote was not grounded.luna_b classified valkey-github-issue-4509 as proposal_only / control_rights, body_only, announced 2026-08-24, no effective date, confidence 0.98; proposed power change: valkey-io gains steward rights for repository hosting and long-term maintenance of the n8n-nodes-valkey repository. Grounded body evidence included “Create a valkey-io/n8n-nodes-valkey repository to host the n8n-nodes-valkey NPM package” and “Hosting under valkey-io provides official endorsement and long-term maintenance commitment.” The response was schema-valid.terra_advisory classified valkey-github-issue-4509 as no_event / product, body_only, announced 2026-08-24, no effective date, confidence 0.98, with no power changes; its rationale-level ambiguity was that the issue proposes a product repository and package but shows no organizational-rights change. The response was schema-valid.valkey-github-issue-4509: both Luna responses treated proposed official hosting and long-term maintenance as a proposed stewardship/control-right change, while Terra treated it as a product proposal with no governance event.valkey-github-pr-1390 were inspected. luna_a classified it as effective_institutional_change / control_rights, consistent, announced 2024-12-04, effective 2024-12-09, confidence 0.97, affecting Valkey project repositories.luna_a coded 3 effective added rights for valkey-github-pr-1390, in order: 1. Harkrishn Patro gains write rights to repository code, grounded in “We added two more committers,” the committer definition, and his MAINTAINERS.md row; 2. Ran Shidlansik gains the same write right, grounded in the same body/definition evidence and his row; 3. Maintainers gain own rights over governance, grounded in “Maintainers are defined as individuals with full access to a repository and own its governance.” The response was schema-valid.luna_b classified valkey-github-pr-1390 as effective_institutional_change / control_rights, consistent, announced 2024-12-04, effective 2024-12-09, confidence 0.98, affecting Valkey repositories.luna_b coded 3 effective added rights for valkey-github-pr-1390, in order: 1. Harkrishn Patro gains write rights to code within a Valkey repository; 2. Ran Shidlansik gains the same write right; 3. Maintainers gain set_policy rights over repository governance. The response was schema-valid.terra_advisory classified valkey-github-pr-1390 as effective_institutional_change / control_rights, consistent, announced 2024-12-04, effective 2024-12-09, confidence 0.88, affecting Valkey project repositories. It coded 3 effective added rights: 1. Harkrishn Patro gains repository-code write; 2. Ran Shidlansik gains repository-code write; 3. Maintainers gain own rights over repository governance. Its ambiguity notes that the patch does not explicitly identify any existing governance rights removed from other individuals. The response was schema-valid.valkey-github-pr-1390 was limited chiefly to the Maintainers edge: luna_a and Terra used right_kind:own, whereas luna_b used right_kind:set_policy; all 3 agreed on an effective institutional control-rights change and on added write rights for Harkrishn Patro and Ran Shidlansik.valkey-github-pr-1788 were inspected. luna_a classified it as control_event / license, consistent, announced and effective 2025-02-27, confidence 0.91, with no power changes. It interpreted the supplied patches as license-header standardization rather than a demonstrated organizational-rights change, while noting the truncated patch selection prevents assessment of omitted changes. The response was schema-valid.luna_b classified valkey-github-pr-1788 as abstain / license, unclear, announced 2025-02-27, no effective date, confidence 0.55, with no power changes. It reasoned that visible patches normalize license notices but omitted changes could contain a substantive licensing-rights change because the patch selection is truncated. The response was schema-valid.terra_advisory classified valkey-github-pr-1788 as abstain / license, unclear, announced 2025-02-27, no effective date, confidence 0.38, with no power changes. It reasoned that merger is established, but truncated excerpts do not establish whether licensing terms or associated rights materially changed rather than merely being standardized or clarified. The response was schema-valid.valkey-github-pr-1788: luna_a treated visible license-header normalization as a merged control_event with an effective date; luna_b and Terra abstained because patch truncation prevents ruling out an omitted substantive licensing-rights change.valkey-github-pr-2927 were inspected. luna_a classified it as effective_institutional_change / control_rights, patch_supersedes_body, announced 2025-12-11, effective 2025-12-12, confidence 0.96, affecting Valkey project governance and the TSC. It identified a body/patch conflict: the body describes simple-majority voting for non-technical decisions, while the merged patch requires a 2/3 threshold for governance major decisions.luna_a coded 5 effective modified TSC rights for valkey-github-pr-2927, in order: 1. approve technical major decisions by simple majority; 2. approve governance major decisions by a 2/3 affirmative vote of the entire TSC; 3. set_membership subject to the one-third organizational-affiliation cap; 4. remove TSC members through the Governance Major Decision process; 5. approve delegation of project decision-making as a Governance Major Decision. The response was schema-valid.luna_b classified valkey-github-pr-2927 as effective_institutional_change / board_or_steering, consistent, announced 2025-12-11, effective 2025-12-12, confidence 0.98, affecting TSC governance, membership, and major-decision procedures.luna_b coded 4 TSC rights for valkey-github-pr-2927, in order: 1. modified approve rights for technical major decisions through simple-majority voting; 2. added fallback approve rights when no simple majority is reached within 2 weeks and no TSC member votes against, using explicit “+2” support from at least 2 TSC members recorded on the relevant issue or pull request; 3. added approve rights over Governance Major Decisions via a 2/3 affirmative vote of the entire TSC; 4. modified remove rights for involuntary removal of TSC members. The response was schema-valid.terra_advisory classified valkey-github-pr-2927 as effective_institutional_change / board_or_steering, patch_supersedes_body, announced 2025-12-11, effective 2025-12-12, confidence 0.92, affecting TSC membership and decision processes. It followed the merged patch because the body calls the updates “non-technical decisions,” while the patch classifies them as Governance Major Decisions.terra_advisory coded 4 effective modified TSC rights for valkey-github-pr-2927, in order: 1. set_membership under the one-third affiliation cap and prompt compliance-restoration obligation; 2. approve technical major decisions through simple majority or, after 2 weeks without opposition, explicit “+2” support from at least 2 TSC members; 3. approve Governance Major Decisions through a 2/3 affirmative vote of the entire TSC; 4. delegate project decision-making to maintainers of other Valkey-organization projects, with such delegation classified as a Governance Major Decision. The response was schema-invalid because the combined technical-major-decision evidence quote was not grounded.valkey-github-pr-2927: luna_a and Terra used patch_supersedes_body, while luna_b used consistent; luna_a used event kind control_rights, while luna_b and Terra used board_or_steering; the edge sets varied—luna_a included membership composition, involuntary removal, and delegation approval but omitted the explicit “+2” fallback, luna_b included the fallback and removal but omitted membership composition and delegation, and Terra included membership composition, the combined majority/“+2” process, governance approval, and delegation but omitted a separate removal edge.