Dashboard › institutional-transition-lab › Distillation
e4f46311-18e9-4503-890c-f1ee82ef88ac["lore_tm_v1_NIWBnxMo4Op04rLRqs0VntvspwqoDQ_MA6dTqObv1DI","lore_tm_v1_58vdLWkfGsvkOsPxt1eiI7_7ZEEyFMDH56l2n3LqdGk","lore_tm_v1_VfhawUDAeLEJtAe_1UJehWQQfIc0UdVxL4MAzH0ioFQ","lore_tm_v1_XW8y1V7hhVYr_bJXVd7D1ZM2rsRPAqyWrwURk52y2xM","lore_tm_v1_HAlQAC_sMEn874L0CoANqOQbUdeuRW_37W-S8vpE2yI","lore_tm_v1_5Eiw8donhFa3gUJU354YD1bJdzD7z8T6vNLrv6SLX04","lore_tm_v1_XJvd4YMIS4USf315nVKzHZmnEqQxVM_VsUbnCRenOgU"]
opentofu-github-pr-2953: Luna A and Luna B both classified it abstain/reorganization, describing governance-document relocation with no established organizational-rights change and warning that the 43-file patch selection was truncated; Terra also classified it abstain, with event_kind: null, announced_on: null, effective_on: null, body_patch_relation: unclear, confidence 0.42, and the same truncation limitation.opentofu-github-pr-2959: Luna A, Luna B, and Terra all classified it abstain/control_rights because the merged CODEOWNERS change lacked an implementing patch from which granted or removed rights could be verified. Luna A confidence was 0.72, Luna B 0.86, and Terra 0.45; each used effective_on: null.opentofu-github-pr-3473: Luna A and Luna B classified the Databricks backend-with-locking RFC as control_event/product, announced_on: 2025-11-05, effective_on: null, body_patch_relation: consistent, with confidence 0.97 and 0.98 respectively; terra_advisory was null.opentofu-github-pr-3559: Luna A classified the support-policy update as no_event with event_kind: null, no dates, body_patch_relation: unclear, confidence 0.7; Luna B classified it control_event/product, effective_on: 2025-12-09, confidence 0.78; Terra classified it control_event/product, announced_on: 2025-12-09, effective_on: null, body_patch_relation: body_only, confidence 0.68, noting that no implementing patch or policy terms established an organizational-rights change or effective revision.opentofu-github-pr-4018: Luna A and Luna B classified official-build detection related to a forthcoming 32-bit warning as control_event/product, announced_on: 2026-04-09, effective_on: 2026-08-11, with confidence 0.9 and 0.84; Terra classified it proposal_only/control_rights, announced_on: 2026-04-09, effective_on: null, confidence 0.84, with a proposed removal edge: actor OpenTofu project, right release, target 32-bit CPU architectures, scope official release packages, citing “ending official support for 32-bit CPU architectures” and “The maintainers have not discussed this yet, and so we might decide to do something quite different in the end.”opentofu-github-pr-727: Luna A and Luna B classified adding # SPDX-License-Identifier: MPL-2.0 to compare-release-versions.sh as effective_institutional_change/license, with an effective added-license edge and confidence 0.98; Luna A used announced_on: 2023-10-14, effective_on: 2023-10-15, and body quote “This change adds a license I missed when writing the compare-release-versions script”; Luna B used the same dates and body quote “Add the license to compare-release-versions.sh.” Terra classified it no_event, event_kind: null, body_patch_relation: consistent, confidence 0.99, scope .github/scripts/compare-release-versions.sh, and no power changes.opentofu-github-pr-823: Luna A and Luna B classified the TSC’s registry-RFC selection as control_event/strategy, body_patch_relation: patch_only, no effective date, confidence 0.94 and 0.95, but differed on announced_on (2023-11-05 vs. 2023-11-02); Terra classified it control_event/strategy, body_patch_relation: consistent, confidence 0.9, no dates, noting that the strategy decisions did not demonstrate a change in organizational rights or authority.opentofu-github-pr-990: all three responses classified the documented TSC decision concerning the default registry namespace as a control_event, with announced_on: 2023-12-10, no effective date, and body_patch_relation: consistent; Luna A used event_kind: strategy, confidence 0.94, and broader scope covering registry namespace, RFCs, issues, and pull requests, while Luna B and Terra used event_kind: product, confidence 0.88 and 0.91, noting that the supplied documentation did not show implementation.terraform-github-issue-22468: Luna A and Luna B both classified the secure-targeting request as no_event, with event_kind: null, all dates and scope null, body_patch_relation: not_applicable, and confidence 0.96 and 0.98; terra_advisory was null.terraform-github-issue-34139: Luna A classified the Azure access-package association authorization error as control_event/product, confidence 0.98; Luna B and Terra classified it no_event with event_kind: null, confidence 0.99; all used null dates and body_patch_relation: not_applicable.2023-11-02 listed attendees Igor Savchenko (@DiscyDel, linked URL spelling DicsyDel), Marcin Wyszynski (@marcinwyszynski), Roger Simms (@allofthesepeople), and Roni Frantchi (@roni-frantchi); absent were Yevgeniy Brikman (@brikis98) and Omry Hary (@omry-hay).2023-11-02 TSC summary recorded unanimous selection of the “Homebrew-like artifact resolution registry component” RFC (opentofu/opentofu issue 741) for resolving providers/modules. Stated drivers were: keep the core team focused on the CLI and avoid maintaining a highly available mission-critical SaaS; maximize availability using GitHub/AWS; retain transparency through a git repository; and decouple artifact resolution from documentation serving and artifact signing so components could satisfy separate non-functional requirements and evolve independently.@RLRabinowitz and @cube2222: announce the selected RFC to the community ASAP; investigate scraping or not scraping existing modules/providers and keys; design key submission; design version bumps; share the detailed design document; and define the scope and task breakdown for the core team.7:30PM CET, with the exact time pending as an action item for @allofthesepeople; agenda suggestions had to be posted at least 24h in advance, otherwise the meeting would be canceled.2 dedicated maintainers and built a Tofu-specific hiring profile and pipeline to share with companies interested in hiring dedicated personnel./home/byk/Code/institutional-transition-lab/src/institution_lab/governance_adjudication.py 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; and response sources luna_a, luna_b, and terra_advisory.governance_adjudication.py requires input-manifest keys workflow_run_id, artifact_id, artifact_sha256, documents_sha256, documents_file_sha256, coding_package_file_sha256, protocol_sha256, coding_schema_sha256, and adjudication_schema_sha256. Frozen pins shown were workflow_run_id: 33063470968, artifact_id: 9642983578, artifact_sha256: 1f6be91fcd98e43e99d82d5f274536f6c23616e7e6c711e26324a2cc4b06ef06, documents_sha256: d70f7f795847968339a645b6dbd6d4428af6bd6044de44fa2602d4c4343b0ee9, documents_file_sha256: 2a62ab05687982c112a29f6126227c26c3ff8defc89ca64662753aaf85c3c0ce, coding_package_file_sha256: 14644759f53071adfe1173d4e25bb01931b8c1591fa8a48295dbd0556a754769, protocol_sha256: 06d4b3407677fe7fb23046f70164a366db06638e8a29af3daf7661f00d565933, and coding_schema_sha256: bfc735a7d8602d1f236a88c2d23b195f0600a8bae86fb8c8936afe7883a41b8e.verify_input_manifest() in governance_adjudication.py rejects missing or unexpected manifest keys, invalid IDs, departures from frozen pins, file-hash mismatches, absent/mismatched ZIP members, and a canonical documents_sha256 mismatch. It verifies ZIP members documents.json and v1.2-adjudication-package.json against durable files.governance_adjudication.py builds source text by source_id, adds serialized record_metadata, and requires evidence objects to contain exactly source_id and quote, or additionally field for claim evidence. Claim fields are record_class, event_kind, title, announced_on, effective_on, affected_scope, and body_patch_relation; every quote must be a literal substring of its referenced frozen source.graph_edge_diff() in governance_adjudication.py compares baseline and final power_changes using _edge_key() canonical JSON and returns deterministically sorted added and removed edge arrays./home/byk/Code/institutional-transition-lab/schema/governance-coding-v1.schema.json is a Draft 2020-12 schema titled “Performance-blinded governance coding v1”; it disallows additional properties and requires record_class, event_kind, title, announced_on, effective_on, affected_scope, body_patch_relation, power_changes, confidence, and ambiguity.record_class values effective_institutional_change, announced_institutional_change, proposal_only, control_event, no_event, and abstain; event_kind values leadership, board_or_steering, control_rights, reorganization, foundation_transfer, license, fork, reunification, strategy, product, external, or null; and body_patch_relation values consistent, patch_supersedes_body, body_only, patch_only, conflict, not_applicable, and unclear.power_changes item must contain exactly actor, right_kind, target, direction, change_status, scope, and evidence_refs. right_kind may be 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 may be added, removed, or modified; change_status may be effective, announced, proposed, rejected, or unclear; each evidence reference requires non-empty source_id and quote.confidence to the inclusive range 0–1, treats announced_on and effective_on as date-formatted strings or null, and allows title, affected_scope, and ambiguity to be strings or null.