Dashboard › institutional-transition-lab › Distillation
a48423a4-a267-40d3-98f3-928f6ae8ce5e["lore_tm_v1_yE444OMKoAJJX9QgaxxN1tDk3IIqXr8dJQwW57sWj08","lore_tm_v1_uJA4tZn6M1I7smN-kFZRoo8yuMRm03NJyE3GicuXXY4","lore_tm_v1_zg8dTEmgkJ6H0ZK4mnUChIZ6EY9n_Z2tCyHkzQ9rwWM","lore_tm_v1_GACvXHm7n8LyepQp0pdS_CV_yiFRT1FzEa5INPs01fo","lore_tm_v1_x_5lV-ZCaoeGUwPLX5awXUHa5_9WKnjep0n5Wkr2VUQ","lore_tm_v1_p0wUU9LD09q05XOicSZDJIjVFUfGHi6UmcJvt9yNz0s","lore_tm_v1_xhvH-DmjmLdLzhYtCnJUctL7SUbrKfb4v5LWwFIVamY","lore_tm_v1_CRkmW5Lma7set-pgMd_cnRUFcV_L6-vIioRP8OoaRHU","lore_tm_v1_fUcbatTpk9G53jwN6sakVTarkqskm5MyLQYeCHQVwPk"]
documents.json SHA-256 plus each assigned record’s full metadata and ordered source envelope was completed; 2. verification of v1.2-coding-package.json SHA-256 plus inspection of only the ontology and direct frozen assigned-record responses was completed; 3. adjudication of all four records with exact evidence and graph-edge revisions was completed; 4. validation of IDs, dates, ontology completeness, quote grounding, and final record count remained in progress.record_class-related matches in /home/byk/Code/institutional-transition-lab/src/institution_lab/governance_coding.py, at lines 70, 245, 246, 247, 304, 313, 429, and 448.effective_institutional_change, proposal_only, and control_event across /home/byk/Code/institutional-transition-lab/tests/test_governance_adjudication.py, /home/byk/Code/institutional-transition-lab/tests/test_llm_triage_compare.py, /home/byk/Code/institutional-transition-lab/tests/test_llm_event_probe.py, /home/byk/Code/institutional-transition-lab/tests/test_governance_coding.py, /home/byk/Code/institutional-transition-lab/src/institution_lab/governance_adjudication.py, /home/byk/Code/institutional-transition-lab/src/institution_lab/llm_event_probe.py, and /home/byk/Code/institutional-transition-lab/src/institution_lab/governance_coding.py./home/byk/Code/institutional-transition-lab/schema/governance-adjudication-v1.schema.json is JSON Schema draft 2020-12 with $id https://institutional-transition-lab.local/schema/governance-adjudication-v1.schema.json, title Performance-blinded governance adjudication v1, root type object, and additionalProperties: false.schema_version, adjudication_id, design_status, transition_dates_excluded, outcome_data_used, inputs, reviewers, and records; it fixes schema_version to 1, design_status to performance_blinded_llm_assisted_source_adjudication, transition_dates_excluded to true, and outcome_data_used to false.records (minItems: 40, maxItems: 40) and at least one reviewer.inputs forbid additional properties and require workflow_run_id, artifact_id, artifact_sha256, documents_sha256, documents_file_sha256, coding_package_file_sha256, protocol_sha256, coding_schema_sha256, and adjudication_schema_sha256; IDs must be positive integers and each hash must match ^[0-9a-f]{64}$.reviewer_id, reviewer_type, model, role, and assistance; reviewer_type is one of human, llm, or human_llm_assisted, and role is one of source_adjudicator, evidence_auditor, or synthesizer.claim_evidence_ref.field permits only record_class, event_kind, title, announced_on, effective_on, affected_scope, and body_patch_relation; each claim reference also requires non-empty source_id and quote.source_audit requires inspected_before_codings: true, a unique non-empty source_ids array, and evidence_bounds; evidence bounds require source_text_truncated, files_listing_complete, patch_selection_truncated, and nonnegative integer patch_unavailable_count.record_id, source_url, decision, accepted_from, reviewer_ids, source_audit, rationale, evidence_limitations, unresolved_reason, claim_evidence_refs, final_coding, and graph_edge_revision; source_url must be a GitHub HTTPS URI matching ^https://github\\.com/[^\\s]+$.decision allows accept, revise, reject, or abstain; accepted_from and graph-revision basis allow luna_a, luna_b, terra_advisory, or null; final_coding and graph_edge_revision may each be null.basis, added, and removed; added and removed are arrays of fully specified power changes./home/byk/Code/institutional-transition-lab/cases/review/oss-governance-adjudication-v1/v1.2-coding-package.json, opentofu-github-issue-1353 is routed for body_patch_relation_disagreement, class_disagreement, edge_disagreement, and event_field_disagreement; its source URL is https://github.com/opentofu/opentofu/issues/1353.opentofu-github-issue-1353, Terra advisory (gpt-5.6-terra, xhigh, 8236 ms) returned schema-valid no_event coding with title Proposal for documentation and user interface writing style framework, announced date 2024-03-08, affected scope OpenTofu technical documentation and user interface writing, body_patch_relation: body_only, no event kind, no effective date, no power changes, confidence 0.98, and no ambiguity. (meaning March 8, 2024)opentofu-github-issue-2109 is not canonically ledger-eligible, lacks full-response and provisional-core agreement, is routed for edge_disagreement, and has source URL https://github.com/opentofu/opentofu/issues/2109.opentofu-github-issue-2109, Luna A (gpt-5.6-luna, medium, 5935 ms) returned schema-valid proposal_only / control_rights coding titled Proposal for direct GitHub provider installation, announced 2024-10-28, affected scope OpenTofu provider installation and distribution, body_patch_relation: body_only, no effective date, confidence 0.98, and one proposed added override edge from users to centralized registry within provider installation and access, grounded in body quote This would enable users to specify a GitHub repository as a provider source, allowing for more flexible and decentralized provider management. (meaning October 28, 2024)opentofu-github-issue-2109, Luna B (gpt-5.6-luna, medium, 5450 ms) returned schema-valid proposal_only / control_rights coding titled Proposal to install providers directly from GitHub, announced 2024-10-28, affected scope OpenTofu provider distribution, body_patch_relation: body_only, no effective date, confidence 0.98, and one proposed added steward edge from users to provider management within OpenTofu providers, using the same direct-GitHub-provider body quote as Luna A. (meaning October 28, 2024)opentofu-github-issue-2109, Terra advisory (gpt-5.6-terra, xhigh, 4089 ms) returned schema-valid no_event coding with body_patch_relation: body_only, all event fields null, no power changes, confidence 0.99, and no ambiguity.opentofu-github-issue-2573 is not canonically ledger-eligible, lacks full-response agreement, has provisional core agreement, has no route reasons, and has source URL https://github.com/opentofu/opentofu/issues/2573.opentofu-github-issue-2573, Luna A (gpt-5.6-luna, medium, 1903 ms) returned schema-valid no_event coding titled Correct year in TSC summaries, with body_patch_relation: not_applicable, all event dates and scope null, no power changes, confidence 0.99, and no ambiguity.opentofu-github-issue-2573, Luna B (gpt-5.6-luna, medium, 2070 ms) returned schema-valid no_event coding titled Use correct year in Technical Steering Committee (TSC) Summary, with body_patch_relation: not_applicable, all event dates and scope null, no power changes, confidence 0.99, and no ambiguity.opentofu-github-issue-258 is not canonically ledger-eligible, lacks full-response and provisional-core agreement, is routed only for body_patch_relation_disagreement, and has source URL https://github.com/opentofu/opentofu/issues/258.opentofu-github-issue-258, Luna A (gpt-5.6-luna, medium, 3398 ms) returned schema-valid control_event / product coding titled Homebrew-like registry design chosen for implementation, announced 2023-11-03, affected scope OpenTofu registry design, body_patch_relation: body_only, no effective date, no power changes, confidence 0.98, and no ambiguity. (meaning November 3, 2023)opentofu-github-issue-258, Luna B (gpt-5.6-luna, medium, 4202 ms) returned schema-valid control_event / product coding with the same title, announcement date, affected scope, and empty power changes as Luna A, but used body_patch_relation: not_applicable and confidence 0.96. (meaning November 3, 2023)opentofu-github-issue-258, Terra advisory (gpt-5.6-terra, xhigh, 5050 ms) returned schema-valid control_event / product coding titled Technical steering committee chose Homebrew-like registry design, announced 2023-11-03, affected scope OpenTofu stable registry design, body_patch_relation: body_only, no effective date, no power changes, confidence 0.98, and no ambiguity. (meaning November 3, 2023)opentofu-github-issue-340 is not canonically ledger-eligible, lacks full-response and provisional-core agreement, is routed for body_patch_relation_disagreement, class_disagreement, and event_field_disagreement, and has source URL https://github.com/opentofu/opentofu/issues/340.opentofu-github-issue-340, Luna A (gpt-5.6-luna, medium, 2922 ms) returned schema-valid control_event / product coding titled Proposal to enable GitHub Discussions, announced 2023-09-07, affected scope opentofu/opentofu repository, body_patch_relation: not_applicable, no effective date, no power changes, confidence 0.98, and no ambiguity. (meaning September 7, 2023)opentofu-github-issue-340, Luna B (gpt-5.6-luna, medium, 4421 ms) returned schema-valid no_event coding titled Proposal to enable GitHub Discussions, with affected scope opentofu/opentofu repository, body_patch_relation: body_only, null dates and event kind, no power changes, confidence 0.98, and no ambiguity.opentofu-github-issue-340, Terra advisory (gpt-5.6-terra, xhigh, 4641 ms) returned no_event, body_patch_relation: body_only, confidence 0.96, and ambiguity The issue proposes enabling GitHub Discussions and offers moderation, but does not evidence an implemented organizational rights change.