Dashboard › institutional-transition-lab › Distillation
eb6b4118-c6aa-4582-a0c8-eb18d586357d["lore_tm_v1_iVBD2z5hB3J6RJlWt7A2JqRvK_YQ7U600nJR7ra6epI","lore_tm_v1_E93Kj_Dv18LgxclUWEtn_WgTs4s3mb2TWLKKk9gm8gM","lore_tm_v1_uFrblJFMrN3XRHpQBAtAfx6LFCeZjF_kcQoH7apSXQI","lore_tm_v1_3-2LoZjYVBYLI6VSzlO2TUYPGfWpMGaQAqf-fpEb9A8","lore_tm_v1_GY9TVdsxprxP8cPehd3ESQdlc8UtQV8Z66Cfc3KXXM4","lore_tm_v1_upL4usMV9fOcjOeiG8RAY4Ki0L67dbqumoe4IDGEvws","lore_tm_v1_9Q49v_YaUbQsJ9HrqBuMkTWrrkJvSNwYnsJWzXSq6Dw","lore_tm_v1_AxcQY12tsX81jDoxu0bor6bgn46pEDpOJc_m-7ybayI","lore_tm_v1_W2Zjfr0qZklZEoEOna2X2Px0WzGS0mUOXvZ2-HRXqp8"]
/home/byk/Code/institutional-transition-lab/src/institution_lab/governance_adjudication.py lines 270-389 validate individual adjudication records: bounded evidence requires a non-empty evidence_limitations; accept requires accepted_from in RESPONSE_SOURCES, a valid frozen response, and final_coding exactly equal to that response; only accept may set accepted_from; resolved decisions require dictionary final_coding; abstain requires null final_coding, a non-empty unresolved_reason, and null graph_edge_revision; resolved decisions require null unresolved_reason and cannot use final class abstain; reject must resolve to a non-institutional class./home/byk/Code/institutional-transition-lab/src/institution_lab/governance_adjudication.py enforces temporal/class consistency: effective_institutional_change requires effective_on; announced_institutional_change requires announced_on; announced_institutional_change and proposal_only must not set effective_on; permitted edge statuses are effective for effective_institutional_change, announced for announced_institutional_change, and proposed, rejected, or unclear for proposal_only./home/byk/Code/institutional-transition-lab/src/institution_lab/governance_adjudication.py validates each claim_evidence_refs item through _evidence_errors(..., claim=True) and, for institutional classes, requires every non-null field in CLAIM_FIELDS to appear among grounded claim references./home/byk/Code/institutional-transition-lab/src/institution_lab/governance_adjudication.py requires every resolved decision to have graph_edge_revision; its basis must be a response source or null, an accepted record’s basis must equal accepted_from, and added/removed must exactly equal graph_edge_diff(baseline, final_coding).validate_adjudication() in /home/byk/Code/institutional-transition-lab/src/institution_lab/governance_adjudication.py begins at line 392 and requires transition_dates_excluded to be true and outcome_data_used to be false.opentofu-github-issue-1353, Luna A (gpt-5.6-luna, medium, 10610 ms) returned schema-valid proposal_only / control_rights coding titled Creating a style guide/framework for documentation and user interface, announced 2024-03-08, affected scope OpenTofu technical documentation and user interface writing, body_patch_relation: body_only, confidence 0.97, and one proposed added set_policy edge from OpenTofu to technical documentation and user interface writing within OpenTofu project; evidence quotes were I'm proposing a _framework_ for technical documentation and user interface writing. and getting all authors to set aside their pet styles and use the standard style for OpenTofu. (meaning March 8, 2024)opentofu-github-issue-1353, Luna B (gpt-5.6-luna, medium, 3792 ms) returned schema-valid no_event coding titled Creating a style guide/framework for documentation and user interface, announced 2024-03-08, affected scope OpenTofu documentation and user interface writing, body_patch_relation: not_applicable, no event kind, no effective date, no power changes, confidence 0.98, and no ambiguity. (meaning March 8, 2024)/home/byk/Code/institutional-transition-lab/cases/review/oss-governance-adjudication-v1/documents.json, opentofu-github-issue-1353 is an opentofu GitHub issue published by opentofu/opentofu on 2024-03-08; its source envelope contains only body, with source_text_truncated: false, patch_selection_truncated: false, patch_unavailable_count: 0, and files_listing_complete: null. (meaning March 8, 2024)opentofu-github-issue-1353 proposes a thought-and-style framework for technical documentation and UI writing, including a written style guide, guidance on when not to use prose, documentation formatting, amendment guidelines, initial creation/refinement, gradual application across documentation and CLI work, adaptation of under-defined rules and tooling, and eventual maturity where most new content follows the guide.documents.json, opentofu-github-issue-2109 is an opentofu GitHub issue published by opentofu/opentofu on 2024-10-28; its sole body source has source_text_truncated: false, patch_selection_truncated: false, patch_unavailable_count: 0, and files_listing_complete: null. (meaning October 28, 2024)opentofu-github-issue-2109 proposes direct provider installation from GitHub to bypass the centralized registry, including repository specification by URL or user/repo, private-repository access through GitHub token authentication, clearer error handling, user and provider documentation, and prescribed release-binary, checksum, and documentation formats.documents.json, opentofu-github-issue-2573 is an opentofu GitHub issue published by opentofu/opentofu on 2025-03-07; its complete sole body says TSC summaries since the beginning of 2025 were still dated 2024. Its evidence bounds are source_text_truncated: false, patch_selection_truncated: false, patch_unavailable_count: 0, and files_listing_complete: null. (meaning March 7, 2025)documents.json, opentofu-github-issue-258 is an opentofu GitHub issue published by opentofu/opentofu on 2023-09-04; its sole body source has source_text_truncated: false, patch_selection_truncated: false, patch_unavailable_count: 0, and files_listing_complete: null. (meaning September 4, 2023)opentofu-github-issue-258 body says OpenTF would replace the official registry after the Public Terraform Registry ToC change while preserving provider/module references; its 2023-10-12 update opened stable-registry design discussion, required backward compatibility, invited RFCs, and set an October 27 deadline before a Technical Steering Committee vote. (meaning October 12, 2023)/home/byk/Code/institutional-transition-lab/tests/test_governance_adjudication.py includes test_accept_edge_revision_uses_the_accepted_response(), which changes the first accepted record’s graph revision basis to luna_b and expects accept revision basis must equal accepted_from plus a closed canonicalization gate./home/byk/Code/institutional-transition-lab/tests/test_governance_adjudication.py includes test_institutional_claims_require_grounded_claim_and_edge_evidence(), which injects quote invented into claim and edge references and expects a not grounded error and closed canonicalization gate._institutional_adjudication(record_class) maps effective_institutional_change → effective, announced_institutional_change → announced, and proposal_only → proposed; it constructs a revised control_rights coding titled Council gains release approval, announced 2024-04-01, scoped to releases, with an added approve edge from The council to releases in project releases, evidenced by The council may approve releases. (meaning April 1, 2024)test_institutional_class_and_edge_status_must_agree() checks three invalid combinations: 1. effective_institutional_change with proposed; 2. announced_institutional_change with effective; 3. proposal_only with effective./home/byk/Code/institutional-transition-lab/src/institution_lab/governance_adjudication.py defines DECISIONS = {"accept", "revise", "reject", "abstain"}, INSTITUTIONAL_CLASSES = {"effective_institutional_change", "announced_institutional_change", "proposal_only"}, REVIEWER_TYPES = {"human", "llm", "human_llm_assisted"}, REVIEWER_ROLES = {"source_adjudicator", "evidence_auditor", "synthesizer"}, and RESPONSE_SOURCES = {"luna_a", "luna_b", "terra_advisory"}.FROZEN_INPUT_PINS in /home/byk/Code/institutional-transition-lab/src/institution_lab/governance_adjudication.py fixes workflow_run_id: 33063470968, artifact_id: 9642983578, artifact_sha256: 1f6be91fcd98e43e99d82d5f274536f6c23616e7e6c711e26324a2cc4b06ef06, documents_sha256: d70f7f795847968339a645b6dbd6d4428af6bd6044de44fa2602d4c4343b0ee9, and documents_file_sha256: 2a62ab05687982c112a29f6126227c26c3ff8defc89ca64662753aaf85c3c0ce.FROZEN_INPUT_PINS are coding_package_file_sha256: 14644759f53071adfe1173d4e25bb01931b8c1591fa8a48295dbd0556a754769, protocol_sha256: 06d4b3407677fe7fb23046f70164a366db06638e8a29af3daf7661f00d565933, coding_schema_sha256: bfc735a7d8602d1f236a88c2d23b195f0600a8bae86fb8c8936afe7883a41b8e, and adjudication_schema_sha256: 6181f5cb60a0462f83be00be301763daa89f11581e68ee1c46a84e8bf4e5be31.canonical_sha256(value) serializes with json.dumps(value, sort_keys=True, separators=(",", ":")).encode() before SHA-256 hashing; file_sha256(path) hashes a file in 1024 * 1024 byte blocks.validate_response() in /home/byk/Code/institutional-transition-lab/src/institution_lab/governance_coding.py requires confidence to be a finite non-boolean number from 0 through 1, validates dates as ISO dates or null, and validates body_patch_relation against BODY_PATCH_RELATIONS.validate_response() must have exactly POWER_KEYS; non-empty actor, target, and scope; allowed right_kind, direction, and change_status; and a non-empty list of exactly shaped evidence references whose quotes occur in the referenced source text.validate_response() requires institutional/proposal records to contain power changes, forbids power changes on non-institutional records, and requires non-null ambiguity for class abstain._validate_run() in governance_coding.py requires non-empty coding documents, valid unique raw response IDs exactly matching document IDs, matching coding_id, coding-schema hash, run_id, source URL, model-input allowlist, model, and reasoning effort, plus a nonnegative integer elapsed_ms; it parses response JSON and applies validate_response().opentofu-github-issue-1353 says there should be guidelines for amending the style guide after initial creation/refinement, describes creation as a messy “big bang,” proposes moving through documentation and then the CLI, adapting the guide and tooling as deficiencies are found, and identifies getting authors to abandon “pet styles” for the OpenTofu standard as a challenge.opentofu-github-issue-258 says the stable registry design would be implemented for OpenTofu production readiness and included in OpenTofu 1.6, must eventually provide a human-readable discovery/documentation UI, must be fully open source, and must implement V1 provider and module registry protocols.2023-11-03 update in opentofu-github-issue-258 states: The technical steering committee convened yesterday and has chosen the Homebrew-like registry design as the one to go with and implement. (meaning November 3, 2023)opencode-sol-opentofu-a1, reviewer type llm, model openai/gpt-5.6-sol, role source_adjudicator, assistance Source-first review of four frozen OpenTofu records, and record_count: 4.opentofu-github-issue-1353 as decision: accept, accepted_from: terra_advisory, with complete-body audit bounds, empty claim refs, Terra’s exact no_event final coding, and graph revision basis terra_advisory with no added or removed edges. Rationale: proposed guidance, tooling, and amendment process do not allocate organizational decision rights; limitation: no adoption or authority-assignment evidence.opentofu-github-issue-2109 as decision: accept, accepted_from: terra_advisory, with complete-body audit bounds, empty claim refs, Terra’s exact all-null no_event event fields except body_patch_relation: body_only and confidence 0.99, and graph revision basis terra_advisory with no added or removed edges. Rationale: bypassing a registry is a product capability rather than organizational authority, and implementation was not evidenced.opentofu-github-issue-2573 as decision: accept, accepted_from: luna_b, with complete-body audit bounds, empty claim refs, Luna B’s exact no_event final coding, and graph revision basis luna_b with no added or removed edges. Rationale: the incorrect year is a documentation correction, not an institutional or product-control event.opentofu-github-issue-258 as decision: accept, accepted_from: luna_a, with complete-body audit bounds, empty claim refs, Luna A’s exact control_event / product final coding, and graph revision basis luna_a with no added or removed edges. Rationale: the TSC selected a Homebrew-like registry design for implementation, exercising existing authority without adding, removing, or transferring organizational rights; limitation: linked issue 741 and implementation artifacts were absent, so no effective implementation date or broader authority change was supported.