Dashboard › institutional-transition-lab › Distillation
4e1948cd-a9c0-41b5-9793-9e26240a5e5c["lore_tm_v1_4MWJ5C5ehI8_4xskIVmoO7FszG58Yd-prPynxH0zH-w","lore_tm_v1_K4pVCWRNijM8lGBILk8MYBguLFe0P_uTX59LAde9gGc","lore_tm_v1_NCaqNbwhgacMmTfsqJQ0cjdiNZXSeaJBK4ytvfbL50Q","lore_tm_v1_2AQ6vGGUWyBjVJe-BuCf7eOW2SdsUu1GZnDR_nstsn8"]
/home/byk/Code/institutional-transition-lab/research/oss-governance-coding-protocol-v1.md, titled “Performance-blinded OSS governance coding protocol v1,” frozen on 2026-08-27 and designated a pre-run, model-informed development protocol rather than holdout evidence. (meaning Aug 27, 2026)schema/governance-coding-v1.schema.json; its SHA-256 is embedded in every coding bundle and response; the runner refuses execution when checked-in schema and bundle hashes differ.gpt-5.6-luna sessions at medium reasoning independently code all 40 records with the same frozen schema and prompt but without shared session state or access to the other model’s output.0.8; 4. truncated source/patch evidence or unavailable patch.gpt-5.6-terra advisory coding at xhigh reasoning; Terra is additional evidence, not an automatic tiebreaker, because prior comparison did not establish greater Terra accuracy.provisional_exact_agreement; every output sets canonical_ledger_eligible to false; the run summary must report zero canonical-ledger records; human/source adjudication and later actor normalization remain separate stages.canonical_ledger_eligible, full_response_agreement, luna_a, luna_b, provisional_core_agreement, record_id, route_reasons, source_url, and terra_advisory.terraform-github-issue-35563: luna_a classified “Terraform crashes on Azure Container Apps” as no_event with confidence 0.99; luna_b classified it as a product control_event affecting Terraform versions below 0.15.0 on Azure Container Apps, also at 0.99; Terra agreed with no_event at 0.99. All three responses were schema-valid.terraform-github-pr-21175: all coders treated the merged development-guide addition—“All Terraform providers are required to contain a MPL-2.0 open source license.”—as an effective license-related institutional change, announced 2019-05-01 and effective 2019-05-02; luna_a modeled Terraform adding the requirement, while luna_b and Terra modeled all Terraform providers as subject to it. (meaning May 1–2, 2019)terraform-github-pr-21175 coding had confidence 0.72 and ambiguity that the evidence establishes the merged guide requirement but not enforcement beyond the guide; luna_a and luna_b confidences were 0.94 and 0.96, respectively.terraform-github-pr-21345 evidence that Terraform Habitat provisioning added a required accept_license (bool) setting that must be true to accept the Habitat end-user license agreement; the source announced the requirement on 2019-05-17, and the PR merged/effectively implemented it on 2019-08-05T16:40:34Z. (meaning Aug 5, 2019)terraform-github-pr-21345: luna_a classified it as an effective_institutional_change and added an effective Chef Software license edge; luna_b classified it as a control_event with no power changes; Terra classified it as an effective license change with a modified Chef Software edge.terraform-github-pr-21345: implemented enforcement is evidenced for Terraform’s Habitat provisioner installations, not for every Habitat installation method.terraform-github-pr-22332 as the merged 2019-08-05 revert of Habitat license-acceptance changes. luna_a attempted to code an effective removed license edge but was schema-invalid because two patch evidence quotes were not grounded; luna_b and Terra both classified the revert as a control_event with no power changes. (meaning Aug 5, 2019)luna_a scoped terraform-github-pr-22332 to the Terraform Habitat provisioner and noted that the patch also removes Chef license documentation without a corresponding Chef implementation patch; luna_b scoped it to Terraform Habitat and Chef provisioners, while Terra scoped it to the Habitat provisioner and provisioner documentation.terraform-github-pr-22745: “Going forward Habitat installation will require users to accept Chef EULA.”terraform-github-pr-22745 merged on 2019-09-09T19:40:20Z and effectively reinstated Terraform Habitat provisioner enforcement: “Habitat end user license agreement needs to be accepted, set the accept_license argument to true to accept.” (meaning Sep 9, 2019)terraform-github-pr-22745: luna_a classified an effective license change adding a Chef Software edge, confidence 0.97; luna_b returned invalid JSON with Extra data: line 1 column 680 (char 679) and no response; Terra classified an effective license change modifying users’ license relation, confidence 0.95.terraform-github-pr-22745: the record establishes merged Terraform enforcement of EULA acceptance but not the effective date of Chef Software’s underlying EULA change.terraform-github-pr-33661: Terraform’s license changed from MPL 2.0 to Business Source License 1.1 on 2023-08-10, with Change License: MPL 2.0; all coders classified it as an effective license-related institutional change. (meaning Aug 10, 2023)terraform-github-pr-33661 license terms quoted by Terra: users may copy, modify, create derivative works, redistribute, and make non-production use; production use is permitted by an Additional Use Grant unless it offers the Licensed Work to third parties on a hosted or embedded basis competitive with HashiCorp products.terraform-github-pr-33661: luna_a confidence 0.99 but schema-invalid due to one ungrounded evidence reference; luna_b confidence 0.98 and schema-valid, explicitly noting truncated patch selection; Terra confidence 0.94, schema-valid, likewise noting truncation but stating the complete LICENSE replacement establishes the change.terraform-github-pr-34096: both Luna coders classified updating Terraform’s HCL dependency to HCL v2.19.0 as a schema-valid product control_event, announced 2023-10-16 and effective 2023-10-17, with no power changes; no Terra advisory was present. (meaning Oct 16–17, 2023)terraform-github-pr-34103: all models classified the HCL v2.19.0 backport into Terraform v1.6 as a product control_event with no power changes; luna_a and Terra assigned effective date 2023-10-17, while luna_b left effective_on null. (meaning Oct 17, 2023)terraform-github-pr-34103: no implementing patch content was supplied; merged PR metadata supports completion of the described backport but not its detailed contents.terraform-github-pr-34847: both Luna coders classified Terraform taking control of historical module-source shorthand interpretation from go-getter as an effective control_rights institutional change on 2024-03-14; Terra classified the work as a product control_event with no organizational power edges. (meaning Mar 14, 2024)terraform-github-pr-34847 edge differences: luna_a used right_kind: steward for added Terraform and removed go-getter responsibility but was schema-invalid due to one ungrounded quote; schema-valid luna_b used right_kind: set_policy for the same two-sided transfer and explicitly preserved go-getter’s responsibility for actual module installation.terraform-github-pr-34847 ambiguity: patch selection was truncated, supplied patches aligned with the described source-address refactoring and remote-backend dependency pruning, and Terra found no organizational-rights change.terraform-github-pr-38385: both Luna coders classified the closed, unmerged AI-agent-governance PR as a proposal_only control_rights event proposing a set_policy edge from terraform to AI coding tools, but both responses were schema-invalid because the body quote “This PR adds governance configs generated from your existing CI pipeline — no manual authoring needed.” was not grounded.terraform-github-pr-38385 alternative: classify a proposed delegate edge from terraform to “AI coding tools (Claude Code, Cursor, Copilot, Codex, Gemini)” for autonomous commits after gates pass, based on ## Autonomy / Auto-commit after gates pass; confidence 0.82, announced 2026-04-15, no effective date because "merged": false. (meaning Apr 15, 2026)