Dashboard › institutional-transition-lab › Distillation
fbcc4b05-d211-4b71-a3fe-4b805dae3364["lore_tm_v1_bTncjkNgMbSYoa3E8FhhSN3JqvOjXYp43Z9t-uS6dzM"]
Date: Sep 8, 2026
terraform-github-pr-22332: luna_a was schema-invalid because evidence quotes -\t\t\t"accept_license": &schema.Schema{ and -\t// Accept the license were not grounded; it proposed an effective removal of license authority by hashicorp/terraform. luna_b was schema-valid and classified the merged revert as a control_event with no power changes. terra_advisory was schema-valid and likewise classified it as a control_event with no power changes, announced_on=null, effective_on=2019-08-05, and title “Revert license-acceptance requirements.” (meaning Aug 5, 2019)terraform-github-pr-22745: luna_a assigned Chef Software an effective added license power targeting users, while terra_advisory modeled users’ license position as effectively modified through the Terraform Habitat provisioner. (meaning Sep 9, 2019)terraform-github-pr-22745: luna_a was schema-valid with record_class=effective_institutional_change, event_kind=license, effective_on=2019-09-09, and an added Chef Software license edge over Habitat installation; luna_b was invalid JSON due to Extra data: line 1 column 680 (char 679); terra_advisory was schema-valid with the same record class/event kind/date but a modified users-license edge and ambiguity that merged Terraform enforcement does not establish the effective date of Chef Software’s underlying EULA change. (meaning Sep 9, 2019)terraform-github-pr-33661: luna_a was schema-invalid because its third evidence quote was not grounded; luna_b was schema-valid and coded HashiCorp, Inc.’s effective modification of the license governing “The Licensed Work,” supported by Business Source License 1.1, Licensor: HashiCorp, Inc., and Change License: MPL 2.0; terra_advisory was schema-valid but instead named actor You and target The Licensed Work. Both valid candidates classified the merged replacement of MPL 2.0 with Business Source License 1.1 as an effective_institutional_change. (meaning Aug 10, 2023)terraform-github-pr-34096: both luna_a and luna_b were schema-valid and classified “Update HCL to v2.19.0” as a control_event, event_kind=product, with no power changes, announced_on=2023-10-16, and effective_on=2023-10-17; terra_advisory returned null. (meaning Oct 16-17, 2023)terraform-github-pr-34103: all three candidates were schema-valid and classified the HCL v2.19.0 backport as a product control_event with no power changes. luna_a used body_patch_relation=not_applicable, confidence 0.99, and effective_on=2023-10-17; luna_b used body_patch_relation=not_applicable, confidence 0.98, and effective_on=null; terra_advisory used body_patch_relation=body_only, confidence 0.87, and effective_on=2023-10-17, noting that merged metadata supports completion but absent patch content cannot verify detailed implementation. (meaning Oct 17, 2023)terraform-github-pr-34847: luna_a was schema-invalid because the quote “We don't use go-getter's own detectors because Terraform needs to be in control of its own source address syntax” was not grounded; luna_b was schema-valid and treated the refactor as an effective control_rights transfer of set_policy authority over historical module-source shorthand interpretation from go-getter to Terraform; terra_advisory was schema-valid and instead classified it as a product control_event with no power changes because the patches describe technical source-address normalization and dependency pruning, not an organizational rights change. (meaning Mar 14, 2024)terraform-github-pr-38385: both luna_a and luna_b 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. terra_advisory was schema-valid and coded a proposal_only control-rights event: actor terraform proposed delegating autonomous commits after quality gates to “AI coding tools (Claude Code, Cursor, Copilot, Codex, Gemini),” supported by +## Autonomy\n+- Auto-commit after gates pass and "merged": false; confidence was 0.82, effective_on=null, and the closed, unmerged PR did not establish adoption. (meaning Apr 15, 2026)