Dashboard › institutional-transition-lab › Distillation
ed90c33c-726a-4d05-b7a1-6a702278f4b7["lore_tm_v1_2gtraAVKjmO5L6sUvyEEF7PCXY7KpcKUE-0kiXnDnkE","lore_tm_v1_C_tvtKB6JIYtm_RE7knGThUa0m8GsTDdKq5ZIkDbZQw","lore_tm_v1_4tVb0L1ut-Dl2WO0FIqnCb5mzPj1IUAYm6U2iT6Qx5I","lore_tm_v1_kSZ2E4EQQJTfJOYNPqi-eSJANO0cR4izfwfWAegdO1s","lore_tm_v1_Otqebi9jgLNS3aWIMwxob2yoSbl8wn6daq-1lwkVl0k","lore_tm_v1_Lwrlv0qTu304dPMa_PNx-41ygwROBk-Qu5dVdE1SIxE","lore_tm_v1__SWNQ1_RkQU0Z6VgsGTipweWTYZlzHLyfmOYvd6WFi0","lore_tm_v1_BMmoRTJGvwg6zb6jYIuBLeVguyX5QnaokpqG3KGTY_U","lore_tm_v1_Xhhu2UdS8n6fVc1N4iTBhq12E_bFLz0Hl9i1viLKT6Y","lore_tm_v1_HW8Yctw6FlV8ez54NDneRAvt0JH-mI_Lw6LrMW8B2_c","lore_tm_v1_WsWBfCKxBREh-SmamO9EMAB6Tv84EXgP3D3h31FWyxE"]
Date: Sep 8, 2026
opentofu-github-pr-2953, 2. opentofu-github-pr-2959, 3. opentofu-github-pr-3473, 4. opentofu-github-pr-3559, 5. opentofu-github-pr-4018, 6. opentofu-github-pr-727, 7. opentofu-github-pr-823, 8. opentofu-github-pr-990, 9. terraform-github-issue-22468, 10. terraform-github-issue-34139./tmp/opencode/institutional-transition-adjudication-9642983578/documents.json./tmp/opencode/institutional-transition-adjudication-9642983578/v1.2-adjudication-package.json./home/byk/Code/institutional-transition-lab/research/oss-governance-coding-protocol-v1.2.md./home/byk/Code/institutional-transition-lab/schema/governance-coding-v1.schema.json.record_id; 2. decision (accept, revise, reject, or abstain); 3. accepted_from (luna_a, luna_b, terra_advisory, or null); 4. complete governance-coding-v1 final coding for accept/revise/reject or null for abstain; 5. concise rationale plus any evidence-bound limitation; 6. graph-edge revision against the accepted response or closest frozen response.accept only when one named valid frozen response can be adopted exactly; revise when an institutional claim is supported but no response can be adopted exactly; reject when the source establishes no institutional claim, with final class potentially no_event or control_event; abstain only when source bounds prevent a defensible decision.quote/source_id pairs from the frozen source.in_progress, high); 2. inspect complete frozen source and metadata for all 10 records (pending, high); 3. inspect frozen model codings only after source review (pending, high); 4. adjudicate each record and validate complete response objects (pending, high); 5. return compact JSON array and batch summary (pending, high)./home/byk/Code/institutional-transition-lab/research/oss-governance-coding-protocol-v1.2.md was inspected. It is “Performance-blinded OSS governance coding protocol v1.2,” frozen 2026-08-27, with status “pre-adjudication evaluator correction; model-informed development protocol.”provisional_exact_agreement.provisional_core_agreement; full-response agreement is reported separately and is not required because titles and numeric confidence are not canonical research fields.33060493337, and repeats only the Terra advisory pass over the corrected route to isolate evaluator changes from model sampling variance./home/byk/Code/institutional-transition-lab/schema/governance-coding-v1.schema.json was inspected. It uses JSON Schema draft 2020-12, $id https://github.com/BYK/institutional-transition-lab/schema/governance-coding-v1.schema.json, title Performance-blinded governance coding v1, object type, and additionalProperties: false.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 object disallows additional properties and requires actor, right_kind, target, direction, change_status, scope, and evidence_refs. right_kind permits 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, or inform; direction permits added, removed, or modified; change_status permits effective, announced, proposed, rejected, or unclear.evidence_refs array requires at least 1 object containing nonempty source_id and quote; confidence must be from 0 through 1; announced_on and effective_on are date-formatted string or null.coding_id: "oss-governance-enriched-coding-v1", coding_schema_sha256: "bfc735a7d8602d1f236a88c2d23b195f0600a8bae86fb8c8936afe7883a41b8e", and design_status: "performance_blinded_model_informed_development".in_progress; model-coding inspection, adjudication/validation, and final output remained pending.opentofu-github-pr-2953 was published 2025-06-24, has 15 sources, complete file listing, patch_selection_truncated: true, patch_unavailable_count: 0, and untruncated source text. Sources include body (1,938 chars), pr_metadata (285 chars), and patches patch:0–patch:12; observed files include CHARTER.md, GOVERNANCE.md, CONTRIBUTING.md, contributing/FAQ.md, and TSC notes dated from 2023-11-02 through 2024-05-07.opentofu-github-pr-2959 was published 2025-06-25, has 2 sources (body 1,613 chars and pr_metadata 284 chars), complete file listing, no patch-selection truncation, no unavailable patches, and untruncated source text.opentofu-github-pr-3473 was published 2025-11-05, has 3 sources (body 1,274 chars, pr_metadata 265 chars, and patch:0 for rfc/20251021-databricks-backend.md at 7,980 chars), complete file listing, no patch-selection truncation, no unavailable patches, and untruncated source text.opentofu-github-pr-3559 was published 2025-12-09, has 2 sources (body 132 chars and pr_metadata 284 chars), complete file listing, no patch-selection truncation, no unavailable patches, and untruncated source text.opentofu-github-pr-4018 was published 2026-04-09, has 4 sources (body 2,808 chars, pr_metadata 284 chars, .github/workflows/release.yml patch 447 chars, and version/official.go patch 1,827 chars), complete file listing, no patch-selection truncation, no unavailable patches, and untruncated source text.opentofu-github-pr-727 was published 2023-10-14, has 3 sources (body 1,152 chars, pr_metadata 284 chars, and .github/scripts/compare-release-versions.sh patch 168 chars), complete file listing, no patch-selection truncation, no unavailable patches, and untruncated source text.opentofu-github-pr-823 was published 2023-11-05, has 3 sources (body 55 chars, pr_metadata 284 chars, and TSC_SUMMARY.md patch 3,267 chars), complete file listing, no patch-selection truncation, no unavailable patches, and untruncated source text.opentofu-github-pr-990 was published 2023-12-10, has 3 sources (body 55 chars, pr_metadata 284 chars, and TSC_SUMMARY.md patch 4,554 chars), complete file listing, no patch-selection truncation, no unavailable patches, and untruncated source text.terraform-github-issue-22468 was published 2019-08-14, has 1 body source of 2,827 chars, files_listing_complete: null, no patch-selection truncation, no unavailable patches, and untruncated source text.terraform-github-issue-34139 was published 2023-10-25, has 1 body source of 3,667 chars, files_listing_complete: null, no patch-selection truncation, no unavailable patches, and untruncated source text.opentofu-github-pr-2953: PR body says, verbatim, “Updated references and moved governance stuff to a new repo opentofu/org.” PR metadata reports base_sha: "3c170157023ac1290c89567ce432c35aa185099a", head_sha: "5f5705b8947cd62834733e6c20635d8d13a616dd", merge_commit_sha: "75bf1c2f65ad4baabd51a5e88873f805f5b2a1c7", changed_files: 43, draft: false, merged: true, merged_at: "2025-06-25T17:50:10Z", and state: "closed".opentofu-github-pr-2953 patch:0 (CHARTER.md) removes the repository-local 140-line OpenTofu Technical Charter and replaces it with [opentofu/org/CHARTER.md](https://github.com/opentofu/org/blob/main/CHARTER.md). The removed charter showed revisions “Initial Adoption | September 15, 2023” and “Amendment | May 20, 2025.”CHARTER.md provisions observed in opentofu-github-pr-2953 include: the TSC is responsible for all technical oversight; TSC members serve until resignation or replacement by the TSC; contributors may become committers by TSC approval and committers may be removed by majority TSC approval; the TSC may define roles, elect a chair, approve or remove subprojects, create working groups, appoint representatives, establish contribution/release/security norms, vote on technical matters, and coordinate marketing/events/communications.CHARTER.md voting provisions observed in opentofu-github-pr-2953: consensus is primary; each TSC member has one vote subject to an employer-group TSC Cap of 2 when the TSC has at least 5 members and 1 when it has 4 or fewer; in-meeting votes require at least 50% attendance and majority of votes cast; asynchronous motions require affirmative votes from at least 50% of all voting members; supermajority requires two-thirds of all voting members; and unresolved votes may be referred by any voting member to the Series Manager.CHARTER.md provisions observed in opentofu-github-pr-2953 also require supermajority voting for charter amendments, legal matters, and alternative-license approval; asynchronous voting must allow at least 14 calendar days’ verifiable notice; public decisions must be documented no later than 14 days after a vote; and charter amendments require a two-thirds TSC vote plus LF Projects approval.CHARTER.md institutional asset/licensing provisions observed in opentofu-github-pr-2953: LF Projects holds title to Project Trademarks; the Project develops and owns Project GitHub/social-media accounts and domain registrations as permitted by the LF Projects license; inbound and outbound code uses Mozilla Public License Version 2.0 by default; documentation uses Creative Commons Attribution 4.0 International; and alternative-license exceptions require approval by two-thirds of the entire TSC.opentofu-github-pr-2953 patch:1 (GOVERNANCE.md) removes local governance text and replaces it with [opentofu/org/GOVERNANCE.md](https://github.com/opentofu/org/blob/main/GOVERNANCE.md). Removed text included a TSC-membership process: nomination by an existing TSC member, significant contribution criteria, two-thirds approval for addition, majority removal for 3 consecutive months of inactivity, and two-thirds removal for cause excluding the member concerned.GOVERNANCE.md text observed in opentofu-github-pr-2953 stated: “The TSC has ultimate authority over all projects in the OpenTofu organization” and “While maintainers of specific projects may have decision-making authority, the TSC retains the right to overrule decisions as necessary, though it should show restraint in doing so.”opentofu-github-pr-2953 patch:5 removes TSC/2023-12-05_NOTES.md. Recorded decisions included: unanimously changing the default registry namespace to OpenTofu; not prioritizing registry UI/docs that quarter while inviting RFCs; unanimously accepting and increasing priority for the client-side state-encryption RFC; not prioritizing first-party OpenTofu VS Code Language Server support; unanimously accepting PR #799 for gunzipbase64; and unanimously accepting PR #579 to speed up the filesystem state backend.opentofu-github-pr-2953 patch:6 removes TSC/2023-12-11_NOTES.md. The notes record a unanimous decision to leave the registry namespace unchanged for the time being and mention it in documentation “in the softest way possible”; a unanimous decision for option (c), releasing GA on January 10 rather than soft-launching December 20; and an unresolved discussion about workspace dependencies and first-party core support.opentofu-github-pr-2953 patch:7 removes TSC/2024-01-07_NOTES.md, which recorded votes from Roger, Roni, Oleksandr, Zach, and Woj to push Ephemeral until after version 1.10, plus confirmation that the 1.9 release was expected that week.opentofu-github-pr-2953 patch:8 removes TSC/2024-01-22_NOTES.md. The notes list 3 historical-release-support alternatives in order: 1. support only the most recent release; 2. support the most recent and one prior release; 3. follow HashiCorp’s approach and support the most recent plus up to two prior releases. The vote was unanimous for option 3.TSC/2024-01-22_NOTES.md also lists 4 non-exclusive certification/security alternatives in order: 1. SOC2 / ISO 27001; 2. external code/security audit; 3. security-scanning tools such as Snyk, DependaBot, and Go Report Card; 4. a written security-disclosure process covering disclosure, escalation/resolution, community notification, and patch rollout. The vote was unanimous for security-scanning tools and a security-disclosure process; Yevgeniy Brikman additionally voted for a code audit.