Dashboard › institutional-transition-lab › Distillation
a915e803-62a4-4c87-b06e-6539f5389c4f["lore_tm_v1_D2bRO6dXu4jFz995ZX88J40TgGGqFVLj07nUinXuYsg","lore_tm_v1_YnBnXysNo4iHtIeoB4RDkNyNe_gmEgqYOZCzIDMZPTo","lore_tm_v1_MEDoi6rI_WjeeReO4-5Qso05CwD-CvedMcc_CPmfA2s","lore_tm_v1_aws6A4fhMGVT4CXwXnmlWznUclG2NyIm4tMWZCJxigc","lore_tm_v1_tEKXAEMzwhsT5fPrEgkTWtzF9P9r91bbmazqLaHvj4s","lore_tm_v1_IgB8yL3YkCnvMj3UTCEoGZujtiUm6kXa1KvM6AkjVz4","lore_tm_v1_kjw3Jmk8u52pUE3Eos4aoDP424jCeWopRS5O7aHvwzg","lore_tm_v1_e7V4zZkx91X0Yzz5bKrsgsxyvnpiUA70cAcE_UPBxn8","lore_tm_v1_cmaJ65juxLQL93cFesfY6RgJ2FYPBTW_4S70ny_eDrg","lore_tm_v1_-VipQuqJSyMCXYp2itmPggEfpvoY0cHb6YS5zz7saAQ","lore_tm_v1_bko_cqa1b_dcBPjI715mz6e4XCVkte-2YK6xg1kI3JQ"]
v1.2-coding-package.json; its top-level keys were records, schema_version, and summary. Each record exposed canonical_ledger_eligible, full_response_agreement, luna_a, luna_b, provisional_core_agreement, record_id, route_reasons, source_url, and terra_advisory.opentofu-github-issue-1353 disagreed: luna_a classified the documentation/UI style framework as proposal_only, event_kind="control_rights", with a proposed set_policy right for OpenTofu over technical documentation and UI writing (confidence 0.97); luna_b and terra_advisory classified it as no_event with no power changes (confidence 0.98 each). All three responses were schema-valid with no validation errors.opentofu-github-issue-2109 disagreed: both Luna responses classified direct GitHub provider installation as proposal_only and event_kind="control_rights" for users, but luna_a labeled the proposed right override of the centralized registry while luna_b labeled it steward over provider management (confidence 0.98 each); terra_advisory classified it as no_event, with null title/scope/date and no power changes (confidence 0.99). All responses were schema-valid with no validation errors.opentofu-github-issue-2573 had full available-model agreement: luna_a and luna_b classified the year correction in TSC summaries as no_event, with no power changes and confidence 0.99; terra_advisory was null. Both Luna responses were schema-valid with no validation errors.opentofu-github-issue-258 had unanimous model agreement that the TSC’s Homebrew-like stable registry design choice was a control_event with event_kind="product", no power changes, and announcement date 2023-11-03; confidences were 0.98 (luna_a), 0.96 (luna_b), and 0.98 (terra_advisory). All responses were schema-valid with no validation errors.opentofu-github-issue-340 disagreed: luna_a treated the proposal to enable GitHub Discussions as a control_event with event_kind="product" and announcement date 2023-09-07 (confidence 0.98), while luna_b and terra_advisory classified it as no_event (confidences 0.98 and 0.96). Terra’s ambiguity stated that proposing Discussions and offering moderation did not evidence an implemented organizational-rights change. All responses were schema-valid with no validation errors.opentofu-github-pr-1010 unanimously classified the merged TSC summaries as a product control_event, but differed in framing: luna_a focused on the decision to release OpenTofu GA on January 10, used announced_on="2023-12-14", body_patch_relation="patch_only", and noted the source did not prove launch occurred (confidence 0.86); luna_b covered registry namespace and GA timing, used announced_on="2023-12-14" and body_patch_relation="consistent" (confidence 0.98); terra_advisory covered registry namespace, GA timing, and product priorities, used announced_on="2023-12-11", and noted differing December 5 and December 11 namespace decisions plus lack of implementation evidence (confidence 0.88). All responses were schema-valid with no validation errors.opentofu-github-pr-1107 disagreed: luna_a and luna_b classified static evaluation of locals and variables for module sources/backends as a product control_event, announced 2024-01-11 (confidences 0.97 and 0.98); luna_a explicitly noted that the PR was closed and unmerged, so implementation effectiveness was not shown. terra_advisory classified it as no_event, reasoning that a closed, unmerged draft containing product implementation work showed neither an organizational-rights change nor a demonstrated release (confidence 0.96). All responses were schema-valid with no validation errors.opentofu-github-pr-1152 had full available-model agreement: luna_a and luna_b classified the merged TSC governance-summary documentation as no_event, with no power changes (confidences 0.93 and 0.95); luna_a explained that documenting existing TSC authority and membership did not show an organizational-rights change. terra_advisory was null. Both Luna responses were schema-valid with no validation errors.opentofu-github-pr-1650 disagreed: luna_a and luna_b classified the added/missing TSC meeting summaries as no_event, with no power changes (confidences 0.98 and 0.99); terra_advisory classified the regular note-posting practice as an announced_institutional_change with event_kind="board_or_steering" and confidence 0.75. Terra encoded an added inform right for “TSC members who take notes,” scoped to TSC meetings and targeting public notes, while noting that the patch announced the practice but did not demonstrate implementation or compliance. All responses were schema-valid with no validation errors.luna_a, luna_b, and available terra_advisory responses had now been obtained for all 9 assigned records; terra_advisory was null only for opentofu-github-issue-2573 and opentofu-github-pr-1152.