Dashboard › institutional-transition-lab › Distillation
ca2151d9-ccf1-41ed-8471-a4e5d5d12bc1["lore_tm_v1_mQmHkt4unwKMVDWapUDC9BqqdrRlQbix8UqgIDgbtUo","lore_tm_v1_gmSjYbbkbQzerJpVW9pbFGKypuL8Cd0OExROeoUc2Nc","lore_tm_v1_loPGwLqXmSVwi9fDt67Kc_03bRX1rKkPz5A0YZMMif8","lore_tm_v1_DhaZa5kfbpT14zrMAPWDW47872amyGIs5AkcI-c8lZs","lore_tm_v1_PG3G2efJR3AtDBuVLeSg41yXmvk2uFYILIJpXU1Kmfs","lore_tm_v1_RhTi_qx6aP_8RBJ3b7f5jbxMzVnLrILIwfaK0zWmkK4","lore_tm_v1_nKzJDmHL4P6Iit3h9UIAjUtfLZZx0a9tWNSY-cRBKVI"]
terraform-github-pr-33661, all three coders classified an effective_institutional_change, event_kind: "license", announced and effective 2023-08-10, body_patch_relation: "consistent", affecting the Terraform Licensed Work and modifying license rights from MPL 2.0 to Business Source License 1.1.terraform-github-pr-33661, luna_a was schema-invalid because power_changes[0].evidence_refs[2] is not grounded; its proposed edge had actor HashiCorp, Inc., target you, scope Terraform Licensed Work, right license, direction modified, status effective, confidence 0.99.terraform-github-pr-33661, schema-valid luna_b used actor HashiCorp, Inc., target you, scope The Licensed Work, right license, direction modified, status effective, confidence 0.98; evidence included This PR was generated as part of recent licensing changes., Licensor: HashiCorp, Inc., Business Source License 1.1, and Change License: MPL 2.0. Its ambiguity noted that patch selection was truncated but the LICENSE patch directly documented implementation.terraform-github-pr-33661, schema-valid terra_advisory used actor You, target and scope The Licensed Work, right license, direction modified, status effective, confidence 0.94; it grounded the changed rights in the removed MPL contributor grant, the added right to copy/modify/create derivatives/redistribute/make non-production use, the limited production-use grant excluding hosted or embedded offerings competitive with HashiCorp products, and merged metadata at 2023-08-10T22:58:09Z. Its ambiguity noted truncated patch selection but a complete LICENSE replacement.terraform-github-pr-34096, schema-valid luna_a and luna_b both coded control_event, event_kind: "product", announced 2023-10-16, effective 2023-10-17, body_patch_relation: "not_applicable", no power changes, title Update HCL to v2.19.0; affected scope differed as HCL v2.19.0 versus Terraform's HCL dependency, with confidence 0.98 versus 0.99. terra_advisory was absent.terraform-github-pr-34103, all three coders classified a product control_event affecting Terraform v1.6, announced 2023-10-17, with no power changes. luna_a used effective 2023-10-17, not_applicable, confidence 0.99; luna_b used effective_on: null, not_applicable, confidence 0.98; terra_advisory used effective 2023-10-17, body_only, confidence 0.87, and noted that no implementation patch was supplied, while merged metadata supported completion of the described HCL v2.19.0 backport but not its detailed contents.terraform-github-pr-34847, luna_a was schema-invalid because power_changes[1].evidence_refs[1] is not grounded; it and schema-valid luna_b classified an effective_institutional_change, event_kind: "control_rights", announced and effective 2024-03-14, body_patch_relation: "consistent", transferring control over Terraform module-source-address normalization from go-getter to Terraform.terraform-github-pr-34847, luna_a represented the transfer with two effective steward edges: an added Terraform edge over module-source syntax/historical shorthand handling and a removed go-getter edge over source parsing/detector logic; confidence 0.98. luna_b represented the same transfer with removed go-getter then added Terraform set_policy edges over interpretation of historical shorthand forms; confidence 0.96, with actual module installation explicitly remaining go-getter’s responsibility.terraform-github-pr-34847, schema-valid terra_advisory instead coded a product control_event, announced and effective 2024-03-14, consistent, no power changes, affected scope Terraform module source-address parsing and remote backend dependency graph, confidence 0.9; its ambiguity said the supplied truncated patches showed technical refactoring rather than an organizational-rights change.terraform-github-pr-38385, luna_a and luna_b were schema-invalid because power_changes[0].evidence_refs[0] is not grounded; both nevertheless proposed proposal_only, event_kind: "control_rights", announced 2026-04-15, no effective date, body_patch_relation: "consistent", confidence 0.98, with a proposed added set_policy edge governing AI coding tools in the terraform repository. Both noted the PR was closed and unmerged, so effectiveness was not established.terraform-github-pr-38385, schema-valid terra_advisory coded proposal_only, control_rights, announced 2026-04-15, no effective date, consistent, confidence 0.82, with a proposed added delegate edge from terraform to AI coding tools (Claude Code, Cursor, Copilot, Codex, Gemini) for autonomous commits in the terraform repository after quality gates pass; evidence included +## Autonomy\n+- Auto-commit after gates pass and "merged": false. Its ambiguity said the closed, unmerged PR did not establish implementation or actual adoption.no_event across research files, including /home/byk/Code/institutional-transition-lab/research/llm-event-triage-cost-frontier-protocol.md, /home/byk/Code/institutional-transition-lab/research/luna-terra-hard-case-comparison.md, /home/byk/Code/institutional-transition-lab/research/oss-governance-enriched-audit-envelope-v1.md, /home/byk/Code/institutional-transition-lab/research/luna-event-extraction-development-benchmark.md, /home/byk/Code/institutional-transition-lab/research/oss-governance-coding-results-v1.2.md, and /home/byk/Code/institutional-transition-lab/research/oss-governance-retrieval-development-v2.md./home/byk/Code/institutional-transition-lab/research/oss-governance-coding-protocol-v1.2.md is titled 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 despite material differences.provisional_core_agreement, and reported full-response agreement separately because titles and numeric confidence are not canonical research fields.33060493337, and repeated only the Terra advisory pass over the corrected route to isolate evaluator changes from model sampling variance./home/byk/Code/institutional-transition-lab/src/institution_lab/governance_adjudication.py, _evidence_errors() requires claim references to contain exactly source_id, quote, and field, non-claim references exactly source_id and quote; it rejects invalid claim fields, absent source IDs, empty values, and quotes not found verbatim in the indexed frozen source.governance_adjudication.py, _response_for() returns a coding response only when the source result is a dict with schema_valid is True; graph_edge_diff() compares complete JSON-sorted edge objects and returns deterministically sorted added and removed edges.governance_adjudication.py, reviewer validation requires exactly reviewer_id, reviewer_type, model, role, and assistance; human reviewers must have model: null, non-human reviewers must name a model, and any model name containing gemini is rejected with Gemini is restricted to event triage.governance_adjudication.py, an accept decision requires accepted_from to name a valid frozen response and final_coding to equal it exactly; revise and reject cannot set accepted_from; resolved decisions require valid final_coding; abstain requires null final_coding, a non-empty unresolved_reason, and null graph_edge_revision.governance_adjudication.py, reject cannot resolve to an institutional class. Institutional final codings require claim evidence for every non-null field in CLAIM_FIELDS. Resolved records require a graph_edge_revision whose basis is a frozen response source or null and whose added/removed arrays exactly equal graph_edge_diff() from that basis to the final coding.governance_adjudication.py, validate_adjudication() requires transition_dates_excluded: true, outcome_data_used: false, exact matches for all REQUIRED_INPUT_PINS, and equality between the coding package summary’s documents_sha256 and canonical_sha256(documents); it also requires a non-empty reviewer array and rejects duplicate reviewer IDs.d70f7f795847968339a645b6dbd6d4428af6bd6044de44fa2602d4c4343b0ee9 exactly matched the coding package’s embedded documents_sha256.terraform-github-pr-34847 has published_on: "2024-03-14" and evidence bounds files_listing_complete: true, patch_selection_truncated: true, patch_unavailable_count: 0, and source_text_truncated: false.terraform-github-pr-34847 body states the PR combined 3 changes to reduce indirect remote-backend dependencies and review noise: 1. Terraform assumed responsibility for historical module-source-address shorthand normalization; 2. SynthBody moved from package configs into configtesting; 3. dead code was pruned from legacy/terraform.terraform-github-pr-34847 body states Terraform had historically delegated module-source-address interpretation to go-getter, but the Terraform team did not directly maintain or control go-getter; Terraform therefore took ownership of historical shorthand recognition to protect Terraform v1.x compatibility from backward-incompatible upstream changes.terraform-github-pr-34847 body distinguishes parsing from installation: parsing source addresses no longer depends on go-getter, but the actual module installer remains dependent on go-getter for the foreseeable future because shared upstream ownership helps address security advisories across HashiCorp products.terraform-github-pr-34847 body gives the shorthand example github.com/hashicorp/terraform-cidr-subnets being normalized to git::https://github.com/hashicorp/terraform-cidr-subnets.git; copied detector code and tests were intended to preserve behavior.terraform-github-pr-34847 removed obsolete Bitbucket Mercurial detection and its hidden API call, because Bitbucket Mercurial support had been sunset since 2020.terraform-github-pr-34847 metadata reports changed_files: 86, merged: true, merged_at: "2024-03-14T16:58:30Z", state: "closed", base_sha: "ca2be46b0e4db9ab64e649da771d527dcd08c505", head_sha: "625b32501cd6f637b82cd6c537033b9c3c6cabf1", merge_commit_sha: "84df5562f21ae587bbb7e9b2a1c5ada582d0ba11", and draft: false.terraform-github-pr-34847 patch:9 adds package moduleaddrs, forcedRegexp, a backward-compatibility-only detectors list (detectGitHub, detectGit, detectBitBucket, detectGCS, detectS3, detectAbsFilePath), detectRemoteSourceShorthands(), and getForcedSourceType(); the code says Do not add any new detectors. All new source types should use the canonical source address syntax.