Distillation

Date: Sep 8, 2026

• 🟡 (21:40) Inspected /home/byk/Code/institutional-transition-lab/research/oss-governance-coding-protocol-v1.2.md, titled “Performance-blinded OSS governance coding protocol v1.2,” frozen on 2026-08-27 with status pre-adjudication evaluator correction; model-informed development protocol.
• 🟡 (21:40) Protocol v1.2 documents a V1.1 evaluator defect: the field called “strict edge agreement” compared actor, right, target, direction, and status but omitted edge scope and evidence references; it also failed to route disagreements in the separately coded body/patch relationship. Consequently, 6 records were labeled provisional_exact_agreement despite material differences.
• 🟡 (21:40) Protocol v1.2 corrections: strict edge signatures include scope and complete grounded evidence references; body/patch-relationship disagreement is an explicit route reason; the remaining non-routed state is renamed provisional_core_agreement; full-response agreement is reported separately and is not required because titles and numeric confidence are not canonical research fields.
• 🟡 (21:40) The corrected evaluator routes 35 records rather than 29. It reuses the byte-identical V1.1 coding bundle and both Luna response files from workflow run 33060493337; only the Terra advisory pass is repeated over the corrected route to isolate the evaluator change from model sampling variance.
• 🟡 (21:40) The protocol states that no model response, performance observation, transition date, or desired result influenced the correction. Terra remains advisory; all records remain ineligible for the canonical ledger; the response schema and frozen envelope remain unchanged.
• 🟡 (21:40) Inspected /home/byk/Code/institutional-transition-lab/schema/governance-coding-v1.schema.json, a JSON Schema 2020-12 object with $id https://github.com/BYK/institutional-transition-lab/schema/governance-coding-v1.schema.json, title “Performance-blinded governance coding v1,” and additionalProperties: false.
• 🟡 (21:40) governance-coding-v1.schema.json requires exactly these top-level fields: record_class, event_kind, title, announced_on, effective_on, affected_scope, body_patch_relation, power_changes, confidence, and ambiguity.
• 🟡 (21:40) Coding schema enums: record_class allows effective_institutional_change, announced_institutional_change, proposal_only, control_event, no_event, abstain; event_kind allows leadership, board_or_steering, control_rights, reorganization, foundation_transfer, license, fork, reunification, strategy, product, external, or null; body_patch_relation allows consistent, patch_supersedes_body, body_only, patch_only, conflict, not_applicable, or unclear.
• 🟡 (21:40) Each coding-schema power_changes item requires actor, right_kind, target, direction, change_status, scope, and evidence_refs, with additionalProperties: false. right_kind allows appoint, remove, elect, vote, delegate, override, approve, merge, write, release, veto, own, license, steward, fund, set_budget, set_strategy, set_policy, set_membership, set_terms, and inform; direction allows added, removed, modified; change_status allows effective, announced, proposed, rejected, unclear.
• 🟡 (21:40) Coding-schema evidence_refs requires at least 1 object containing nonempty source_id and quote; confidence is constrained to 0–1; announced_on and effective_on are nullable date strings; title, affected_scope, and ambiguity are nullable strings.
• 🟡 (21:41) Inspected /home/byk/Code/institutional-transition-lab/schema/governance-adjudication-v1.schema.json, a JSON Schema 2020-12 object titled “Performance-blinded governance adjudication v1,” with $id https://institutional-transition-lab.local/schema/governance-adjudication-v1.schema.json and additionalProperties: false.
• 🟡 (21:41) Adjudication schema top-level requirements are schema_version, adjudication_id, design_status, transition_dates_excluded, outcome_data_used, inputs, reviewers, and records. Constants are schema_version: 1, design_status: performance_blinded_llm_assisted_source_adjudication, transition_dates_excluded: true, and outcome_data_used: false.
• 🟡 (21:41) Adjudication inputs requires 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 are positive integers and each SHA-256 value must match ^[0-9a-f]{64}$.
• 🟡 (21:41) Adjudication reviewers requires at least 1 reviewer with reviewer_id, reviewer_type, model, role, and assistance. reviewer_type allows human, llm, or human_llm_assisted; role allows source_adjudicator, evidence_auditor, or synthesizer; model may be a nonempty string or null.
• 🟡 (21:41) Adjudication output requires exactly 40 records (minItems: 40, maxItems: 40). Each record requires 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.
• 🟡 (21:41) Adjudication record constraints: source_url must be a GitHub URI matching ^https://github\\.com/[^\\s]+$; decision allows accept, revise, reject, abstain; accepted_from allows luna_a, luna_b, terra_advisory, or null; reviewer_ids requires at least 1 unique nonempty string.
• 🟡 (21:41) Each source_audit requires inspected_before_codings: true, at least 1 unique source_id, and evidence_bounds. Required evidence-bound fields are source_text_truncated, files_listing_complete, patch_selection_truncated, and patch_unavailable_count, with the last constrained to an integer ≥0.
• 🟡 (21:41) claim_evidence_ref requires field, source_id, and quote; field may be record_class, event_kind, title, announced_on, effective_on, affected_scope, or body_patch_relation.
• 🟡 (21:41) graph_edge_revision may be an edge_revision object or null. An edge revision requires basis, added, and removed; basis allows luna_a, luna_b, terra_advisory, or null, while added and removed are arrays of full power_change objects.
• 🟡 (21:41) A search of /home/byk/Code/institutional-transition-lab/cases/review/oss-governance-adjudication-v1/documents.json found 9 OpenTofu records, in file order: 1. opentofu-github-pr-2830 (line 262), 2. opentofu-github-pr-2953 (line 308), 3. opentofu-github-pr-2959 (line 414), 4. opentofu-github-pr-3473 (line 442), 5. opentofu-github-pr-3559 (line 476), 6. opentofu-github-pr-4018 (line 504), 7. opentofu-github-pr-727 (line 544), 8. opentofu-github-pr-823 (line 578), 9. opentofu-github-pr-990 (line 612).
• 🟡 (21:42) Inspected record opentofu-github-pr-2830 in /home/byk/Code/institutional-transition-lab/cases/review/oss-governance-adjudication-v1/documents.json: entity opentofu, publisher opentofu/opentofu, source type github_pull_request, source URL https://github.com/opentofu/opentofu/pull/2830, and publication date 2025-05-20.
• 🟡 (21:42) opentofu-github-pr-2830 evidence bounds are files_listing_complete: true, patch_selection_truncated: true, patch_unavailable_count: 0, and source_text_truncated: false.
• 🟡 (21:42) The body source for opentofu-github-pr-2830 is titled “OpenTofu Charter and Governance.” It says the PR resulted from discussions between OpenTofu’s founding members and the Linux Foundation, defines a governance structure intended to suit and protect the project, identifies initial TSC members as those already serving the role plus the current Technical Lead, and characterizes the change as movement from the “Cathedral” toward the “Bazaar.”
• 🟡 (21:42) PR metadata for opentofu-github-pr-2830: base_sha 6f0d3d3a07a49309b30960d57225c9f7c701e9a9, head_sha da4ac00ca09d1d9e06e47efd77523a235d49f10c, merge_commit_sha 59d24390b712b87954ee175c38912e56d8f5d974, changed_files: 43, draft: false, merged: true, merged_at: 2025-05-23T12:18:56Z, state: closed.
• 🟡 (21:42) opentofu-github-pr-2830 includes patch sources patch:0 for CHARTER.md, patch:1 for GOVERNANCE.md, and patch:2 for CONTRIBUTING.md.
• 🟡 (21:42) The new CHARTER.md identifies an initial adoption date of September 15, 2023 and an amendment date of May 20, 2025; establishes OpenTofu as a Series of LF Projects, LLC; defines the mission as developing and preserving open-source infrastructure as code; and assigns the Technical Steering Committee responsibility for all technical oversight.
• 🟡 (21:42) The CHARTER.md patch says initial TSC voting members are Project Committers listed as “TSC Members” in CONTRIBUTING; members serve until resignation or replacement by the TSC; and the TSC may choose and document an alternative membership-selection approach in CONTRIBUTING.
• 🟡 (21:42) The new GOVERNANCE.md says the TSC has overall responsibility for OpenTofu’s technical direction and oversight. Adding a TSC member requires nomination by an existing TSC member, significant contributions, and a two-thirds supermajority vote; approval results in TSC-list inclusion and appropriate project-resource access.
• 🟡 (21:42) GOVERNANCE.md termination rules include: voluntary written resignation without a vote; possible removal after 3 consecutive months of inactivity by majority vote of active TSC members with at least 14 days’ notice; and removal for cause by a two-thirds supermajority excluding the member in question.
• 🟡 (21:42) The CONTRIBUTING.md patch changes contribution workflow: for a feature, bug fix, refactor, or CI tooling change, contributors should locate an issue carrying both accepted and help wanted, comment that they want to work on it, wait for maintainer assignment, and only then submit code.