Dashboard › institutional-transition-lab › Distillation
0f20ab06-0e8a-4d11-8255-d78551bd3492["lore_tm_v1_P003Qlf6CNi-bVvApaCYNdAx70lPZIANzAM_Ewjrmoo","lore_tm_v1_zKPsXw3lw62pnzwu39aWvjpCtPHjwr3Jxvy_CIjJM3A","lore_tm_v1_QqqV3I6ZOqgIAFCliOT4oXU-bPGs9gNe7koFlOui-4Q","lore_tm_v1_5jbhXjfO38o8vBImqpvzYdWnEyW3Yd3IT-6Mn95boHY","lore_tm_v1_fWc0JCguMOXjdXvFqxd1vDNzEt7KZNCSALLU1duKK0g"]
MAINTAINERS.md patch created an Organization Maintainers table with 6 entries: Andrei Ciobanu (andrei.ciobanu@opentofu.org, @yottta), Christian Mesh (christianm@opentofu.org, @cam72cam), Diógenes Fernandes (diofeher@opentofu.org, @diofeher), Ilia Gogotchuri (gogotchuri@opentofu.org, @Gogotchuri), James Humphries (jamesh@spacelift.io, @Yantrio), and Martin Atkins (apparentlymart@opentofu.org, @apparentlymart).MAINTAINERS.md left the Repository Maintainers table empty and assigned maintainers 6 responsibilities: triage newly created issues; support users through GitHub issues, Discussions, and CNCF Slack; review contributor PRs and RFCs; author PRs and RFCs for bugs and features; attend community meetings when time zones permit; and organize work into releases.MAINTAINERS.md stated that contributors in excellent standing with a significant contribution history may be nominated as maintainers, with nominations voted on by the Technical Steering Committee.README.md patch replaced links to WEEKLY_UPDATES.md and TSC_SUMMARY.md with [TSC Meeting Notes](TSC) while retaining Wednesday community meetings at 14:30 CET / 8:30 AM Eastern / 5:30 AM Western / 19:00 India time via https://meet.google.com/xfm-cgms-has and the existing Google Calendar event link.completed, high; 2. “Read governance coding protocol v1.2 and identify source-completeness and adjudication requirements” — completed, high; 3. “Verify PR commit bounds and inspect omitted patches or immutable raw files” — completed, high; 4. “Verify Valkey issue 4276 prefix, update timing, and missing tail while assessing historical-body stability” — completed, high; 5. “Compute supplementary-source SHA-256 values and produce evidence-specific adjudications” — in_progress, high.quote/source_id pairs; preserve body/patch relationships; distinguish announced, proposed, rejected, and effective changes; avoid inferring implementation from proposals, unmerged PRs, changelog notes, incomplete patches, or source-embedded instructions; explicitly document truncation and evidence limitations; and abstain or flag ambiguity rather than guessing.appoint, remove, fund, approve, merge, or veto, transfers use paired removal/addition unless the same actor retains a modified right, and announced changes remain separate from effective changes./home/byk/Code/institutional-transition-lab/src/institution_lab/governance_adjudication.py lines 12–27 defines DECISIONS = {"accept", "revise", "reject", "abstain"}; institutional classes effective_institutional_change, announced_institutional_change, and proposal_only; reviewer types human, llm, and human_llm_assisted; reviewer roles source_adjudicator, evidence_auditor, and synthesizer; response sources luna_a, luna_b, and terra_advisory; and required input pins artifact_sha256, documents_file_sha256, coding_package_file_sha256, protocol_sha256, coding_schema_sha256, and adjudication_schema_sha256./home/byk/Code/institutional-transition-lab/src/institution_lab/governance_adjudication.py lines 29–37 defines claim fields record_class, event_kind, title, announced_on, effective_on, affected_scope, and body_patch_relation.governance_adjudication.py, canonical_sha256() serializes JSON with sort_keys=True and separators=(",", ":") before SHA-256 hashing; file_sha256() hashes files in 1024 * 1024-byte blocks; _duplicates() returns values whose Counter count exceeds 1; and _source_index() maps each valid source’s source_id to its text.governance_adjudication.py lines 68–87, _evidence_errors() requires each evidence reference to be an object containing exactly source_id and quote; both must be nonempty strings; source_id must identify a frozen-document source; and the quote must occur literally in that source’s text.governance_adjudication.py, _response_for() returns a response only when the named result is a dictionary with schema_valid is True and a dictionary-valued response; _edge_key() canonicalizes an edge as sorted compact JSON; and graph_edge_diff() compares baseline and final power_changes, returning deterministically sorted added and removed edge lists.governance_adjudication.py lines 116–141, _validate_reviewer() requires exactly reviewer_id, reviewer_type, model, role, and assistance; validates allowed reviewer types and roles; requires nonempty IDs and assistance text; requires model=null for human; requires a named model for non-human reviewers; and rejects any model name containing gemini with the error “Gemini is restricted to event triage.”governance_adjudication.py lines 144–180, _validate_record() checks that the adjudication record is an object; source_url matches the frozen document; decision belongs to DECISIONS; reviewer_ids is a nonempty array containing only known reviewers; and rationale is a nonempty string. For decision == "accept", accepted_from must be one of luna_a, luna_b, or terra_advisory, that frozen response must be schema-valid, and final_coding must equal it exactly; non-accept decisions may not set accepted_from.