Dashboard › institutional-transition-lab › Distillation
fa984e6d-c016-4486-a066-279004f62e34["lore_tm_v1_MuY5bN06s73ru8n8JCQyC76qQO38VuucoC1uFrluwZo","lore_tm_v1_v2Mmffn9opIlhOdS6tPMdqrMtQ-BwAoA01MQde8wo4U","lore_tm_v1_siXqjfipckhdHzzhw4HFZlA8uXkbK9g2wKX26CxlX5Y","lore_tm_v1_1V2bgjWA3h2fyrW-IFM5mXBi4i2FR4wcXMxXSq6kkB4"]
/home/byk/Code/institutional-transition-lab/src/institution_lab/governance_coding.py:241-315 showed that validate_response requires the response’s keys to equal RESPONSE_KEYS; validates record_class against RECORD_CLASSES, non-null event_kind against EVENT_KINDS, non-null title/affected_scope/ambiguity as non-empty strings, announced_on/effective_on as ISO dates or null, and body_patch_relation against BODY_PATCH_RELATIONS.validate_response requires confidence to be a finite non-Boolean integer or float from 0 through 1; requires power_changes to be an array; and requires each power change to have exactly POWER_KEYS, non-empty actor/target/scope, allowed right_kind/direction/change_status, and at least one evidence reference.REF_KEYS; its source_id must resolve to a source in the frozen document and its non-empty quote must occur exactly in that source text. Institutional/proposal records require at least one power change, non-institutional records prohibit power changes, and record_class: abstain requires non-null ambiguity.completed, high priority; 2. inspect and compare only direct Luna A, Luna B, and Terra responses — in_progress, high priority; 3. derive source-grounded final codings and graph-edge revisions — pending, high priority; 4. validate the five-record adjudication fragment against frozen inputs and schema — pending, high priority; 5. return one substantive response with reviewer provenance and all five decisions — pending, high priority.valkey-github-issue-4509, Luna A (gpt-5.6-luna, medium, 6430 ms) coded proposal_only/control_rights, confidence 0.98, announced 2026-08-24, no effective date, body_only, with a proposed added steward right for valkey-io over repository hosting and long-term maintenance; it was schema-invalid because its combined body quote was not grounded.valkey-github-issue-4509, Luna B (gpt-5.6-luna, medium, 6026 ms) produced a schema-valid proposal_only/control_rights coding, confidence 0.98, titled Create valkey-io/n8n-nodes-valkey repository, announced 2026-08-24, no effective date, body_only; its single proposed added steward edge assigned valkey-io repository-hosting and long-term-maintenance stewardship over the n8n-nodes-valkey repository, grounded by the body quotes Create a \valkey-io/n8n-nodes-valkey` repository to host the `n8n-nodes-valkey` NPM packageandHosting under valkey-io provides official endorsement and long-term maintenance commitment`.valkey-github-issue-4509, Terra (gpt-5.6-terra, xhigh, 4756 ms) produced a schema-valid no_event/product coding, confidence 0.98, titled Proposal to create n8n-nodes-valkey repository, announced 2026-08-24, no effective date, body_only, and no power changes; ambiguity stated that the issue proposes a product repository and package but demonstrates no organizational-rights change.valkey-github-pr-1390, Luna A (gpt-5.6-luna, medium, 17591 ms) produced a schema-valid effective_institutional_change/control_rights coding, confidence 0.97, titled Valkey adds committers and separates committer and maintainer rights, announced 2024-12-04, effective 2024-12-09, consistent, with three effective added edges: Harkrishn Patro → write code in Valkey project repositories; Ran Shidlansik → write code in Valkey project repositories; Maintainers → own governance of Valkey project repositories.valkey-github-pr-1390’s committer edges with body quote We added two more committers, patch definition Committers are defined as individuals with write access to the code within a repository., and patch table rows for Harkrishn Patro/hpatro and Ran Shidlansik/ranshid; the maintainer edge used Maintainers are defined as individuals with full access to a repository and own its governance.valkey-github-pr-1390, Luna B (gpt-5.6-luna, medium, 10462 ms) produced a schema-valid effective_institutional_change/control_rights coding, confidence 0.98, titled Valkey separates committer and maintainer roles, announced 2024-12-04, effective 2024-12-09, consistent; it coded effective added write edges for Harkrishn Patro and Ran Shidlansik and an effective added set_policy edge for Maintainers over repository governance.valkey-github-pr-1390, Terra (gpt-5.6-terra, xhigh, 25966 ms) produced a schema-valid effective_institutional_change/control_rights coding, confidence 0.88, titled Separate committers from maintainers and add two committers, announced 2024-12-04, effective 2024-12-09, consistent; it coded effective added write edges for Harkrishn Patro and Ran Shidlansik and an effective added own edge for Maintainers over repository governance. Terra noted that the patch does not explicitly identify any governance rights removed from other individuals.valkey-github-pr-1788, Luna A (gpt-5.6-luna, medium, 8370 ms) produced a schema-valid control_event/license coding, confidence 0.91, titled Standardized Valkey file license headers, announced and effective 2025-02-27, consistent, with no power changes; ambiguity said the truncated patch selection prevents assessment of omitted changes, while supplied patches show license-header standardization rather than demonstrated organizational-rights change.valkey-github-pr-1788, Luna B (gpt-5.6-luna, medium, 13215 ms) produced a schema-valid abstain/license coding, confidence 0.55, titled Consistent look and feel of licenses, announced 2025-02-27, no effective date, body_patch_relation: unclear, and no power changes; it reasoned that visible patches normalize license notices but truncated omitted changes might contain substantive licensing-rights changes.valkey-github-pr-1788, Terra (gpt-5.6-terra, xhigh, 7370 ms) produced a schema-valid abstain/license coding, confidence 0.38, titled Consistent look and feel of licenses, announced 2025-02-27, no effective date, body_patch_relation: unclear, and no power changes; it noted that the PR was merged but truncated supplied excerpts do not establish whether licensing terms or rights materially changed rather than being standardized or clarified.valkey-github-pr-2927, Luna A (gpt-5.6-luna, medium, 15868 ms) produced a schema-valid effective_institutional_change/control_rights coding, confidence 0.96, titled Valkey governance and TSC decision rules revised, announced 2025-12-11, effective 2025-12-12, patch_supersedes_body; ambiguity explained that the body’s simple-majority language for non-technical decisions conflicts with the patch’s 2/3 governance-major-decision threshold, so the merged patch controls.valkey-github-pr-2927, in order: 1. approve technical major decisions by simple majority; 2. approve governance major decisions by 2/3 affirmative vote of the entire TSC; 3. set_membership via the rule that no more than one third (1/3) of TSC members may represent the same or affiliated organizations; 4. remove TSC members through the Governance Major Decision process; 5. approve delegation of project decision-making as a Governance Major Decision.valkey-github-pr-2927, Luna B (gpt-5.6-luna, medium, 9913 ms) produced a schema-valid effective_institutional_change/board_or_steering coding, confidence 0.98, titled Valkey governance and TSC voting rules revised, announced 2025-12-11, effective 2025-12-12, consistent.valkey-github-pr-2927, in order: 1. effective modified approve right for technical major decisions by simple majority; 2. effective added approve path when no simple majority is reached within two weeks, no TSC member votes against, and at least two members record explicit “+2” support; 3. effective added approve right requiring a 2/3 affirmative vote for Governance Major Decisions covering governance, membership, roles, voting rules, responsibilities, and oversight; 4. effective modified remove right for involuntary removal of TSC members.valkey-github-pr-2927, Terra (gpt-5.6-terra, xhigh, 50960 ms) coded effective_institutional_change/board_or_steering, confidence 0.92, titled TSC voting rules and membership composition limit updated, announced 2025-12-11, effective 2025-12-12, patch_supersedes_body; it noted that the body calls the updates “non-technical decisions,” whereas the implementing patch classifies them as Governance Major Decisions.valkey-github-pr-2927, in order: 1. set_membership for the one-third organization-affiliation cap and compliance restoration; 2. approve technical major decisions via simple majority or the two-week/no-opposition/two-+2 fallback; 3. approve Governance Major Decisions by 2/3 of the entire TSC; 4. delegate project decision-making to maintainers, with delegation itself treated as a Governance Major Decision. Terra’s response was schema-invalid because the multiline quote grounding edge 2 was not an exact source-text match.valkey-github-pr-345, Luna A (gpt-5.6-luna, medium, 9798 ms) produced a schema-valid effective_institutional_change/board_or_steering coding, confidence 0.99, titled Valkey Technical Steering Committee governance established, announced 2024-04-21, effective 2024-04-30, patch_supersedes_body, affecting all current and future repositories under the Valkey-io organization.valkey-github-pr-345, in order: 1. set_membership for adding or removing Maintainers and accordingly TSC members by no less than a 2/3 affirmative vote of the current TSC; 2. appoint a Chair responsible for organizing TSC meetings; 3. delegate decision-making for other Valkey-organization projects to their maintainers; 4. override decisions made by other Valkey-organization projects, with restraint advised.valkey-github-pr-345, Luna B (gpt-5.6-luna, medium, 9300 ms) produced a schema-valid effective_institutional_change/board_or_steering coding, confidence 0.99, titled Valkey governance establishes Technical Steering Committee, announced 2024-04-21, effective 2024-04-30, consistent, affecting the Valkey project and all current and future repositories under the Valkey-io organization.valkey-github-pr-345, in order: 1. set_membership over TSC members by a 2/3 affirmative vote; 2. appoint the Chair; 3. set_policy by amending the governance document with no less than a 2/3 affirmative vote; 4. delegate decision-making for other Valkey-organization projects; 5. override decisions made by those projects.valkey-github-pr-345, Terra (gpt-5.6-terra, xhigh, 17093 ms) produced a schema-valid effective_institutional_change/board_or_steering coding, confidence 0.98, titled Add Valkey project governance and Technical Steering Committee, announced 2024-04-21, effective 2024-04-30, consistent, affecting all current and future repositories under the Valkey-io organization.valkey-github-pr-345, each additionally grounded by pr_metadata quote "merged": true, "merged_at": "2024-04-30T21:57:21Z": 1. The TSC → set_policy over all technical, project, approval, and policy matters for Valkey; 2. current TSC → set_membership over Maintainers and accordingly TSC members by 2/3 vote; 3. The TSC → appoint a Chair; 4. The TSC → delegate project decision-making to responsible maintainers; 5. The TSC → override decisions of other projects within the Valkey organization.