Dashboard › institutional-transition-lab › Distillation
b8789cf7-c6d0-4927-af26-00da2ffa0d38["lore_tm_v1_mspRaOn6yvNKzEPiyqIY-KZP4iRPSllmm367UKHJgbc","lore_tm_v1_Fz1v6GHSN5QnTZ5qKzE9DeSNv3V_9NjpRW-zoUJ5Exw","lore_tm_v1_2DWEH0GbrgWCg3kVPuz7LjhMNlksQ2icNBCdzUHrVYU","lore_tm_v1_JxrgJmls6Zot2EaOWIXdgrvhv-00EwVX4BP_NZXRE7E","lore_tm_v1_o76iqq4WM-UZ59hfS2KbzOLMvgQsiQgIu2Zbde6mQOQ","lore_tm_v1_FZGvxqXyuBFioS_NeO8bwyofUzX8XcsF392q2848M3M","lore_tm_v1_Iz72JcdNRxIn7WqnPAiUmwTi9zxLiet3f2v9Y4hosqA"]
/home/byk/Code/institutional-transition-lab/cases/review/oss-governance-adjudication-v1/documents.json; it declares coding_id: oss-governance-enriched-coding-v1, coding_schema_sha256: bfc735a7d8602d1f236a88c2d23b195f0600a8bae86fb8c8936afe7883a41b8e, and design_status: performance_blinded_model_informed_development.documents.json, opentofu-github-issue-1353, is an OpenTofu issue titled “Creating a style guide/framework for documentation and user interface,” published by opentofu/opentofu at https://github.com/opentofu/opentofu/issues/1353; it proposes: a written technical-documentation style guide covering English variant, grammar, common phrasing, and heading case; guidance on replacing prose with clearer lists, tables, or images; and formatting optimized for scannability. The displayed body was truncated at 2,000 characters. (meaning Mar 8, 2024)/home/byk/Code/institutional-transition-lab/cases/review/oss-governance-adjudication-v1/v1.2-coding-package.json, terraform-github-pr-22332 is at line 1957 and has canonical_ledger_eligible: false, full_response_agreement: false, with route reasons ordered as: 1. class_disagreement, 2. edge_disagreement, 3. invalid_response.terraform-github-pr-22332, luna_a classified the revert as effective_institutional_change with title Revert Habitat license acceptance requirement, event_kind: license, confidence 0.98, announced_on: 2019-08-05, effective_on: 2019-08-05, and body_patch_relation: patch_supersedes_body; it modeled a removed power change by actor hashicorp/terraform affecting “Habitat provisioner license-acceptance validation and installation,” but the response was schema-invalid because power_changes[0].evidence_refs[1] and [2] were not grounded. (meaning Aug 5, 2019)terraform-github-pr-22332, luna_a recorded ambiguity that the patch also removes Chef license documentation but shows no corresponding Chef implementation patch.terraform-github-pr-22332, luna_b classified the record as a control_event titled Revert Habitat License Acceptance changes, with no power_changes, confidence 0.96, announced_on and effective_on both 2019-08-05, and body_patch_relation: consistent; its response was schema-valid. (meaning Aug 5, 2019)terraform-github-pr-22332, terra_advisory classified the record as a control_event titled Revert license-acceptance requirements, with no power_changes, confidence 0.98, announced_on: null, effective_on: 2019-08-05, body_patch_relation: consistent, and affected scope “Terraform Habitat provisioner and provisioner documentation”; its response was schema-valid. (meaning Aug 5, 2019)v1.2-coding-package.json, terraform-github-pr-22745 has canonical_ledger_eligible: false, full_response_agreement: false, with route reasons ordered as: 1. class_disagreement, 2. edge_disagreement, 3. invalid_response.terraform-github-pr-22745, luna_a classified the record as an effective_institutional_change titled Habitat installation requires Chef EULA acceptance, with confidence 0.97, announced_on: null, effective_on: 2019-09-09, event_kind: license, and body_patch_relation: consistent; it modeled an added, effective license power change by actor Chef Software, targeting users in the scope Habitat installation. The response was schema-valid. (meaning Sep 9, 2019)terraform-github-pr-22745, luna_b produced no usable response: response: null, schema_valid: false, with validation error invalid JSON: Extra data: line 1 column 680 (char 679).terraform-github-pr-22745, terra_advisory classified the record as an effective_institutional_change titled Require Chef EULA acceptance for Habitat provisioning, with confidence 0.95, announced_on and effective_on both 2019-09-09, event_kind: license, and body_patch_relation: consistent; it modeled a modified, effective license power change by actor users, targeting Habitat installation within “Habitat installation through the Terraform Habitat provisioner.” The response was schema-valid. (meaning Sep 9, 2019)terra_advisory’s ambiguity for terraform-github-pr-22745 states that the record establishes merged Terraform enforcement of EULA acceptance but does not establish the effective date of Chef Software’s underlying EULA change.high, in exact order: 1. “Verify pinned artifact hashes and inspect the protocol and schema” — completed; 2. “Adjudicate terraform-github-pr-22332 source-first” — completed; 3. “Adjudicate terraform-github-pr-22745 source-first” — in_progress; 4. “Adjudicate terraform-github-pr-33661 source-first, including supplied recovered evidence” — pending; 5. “Adjudicate terraform-github-pr-34096 source-first” — pending; 6. “Adjudicate terraform-github-pr-34103 source-first” — pending; 7. “Validate all five final objects against schema and evidence requirements” — pending.