Session 1cFm9D7Id1Wo

[
  {
    "content": "Read protocol and coding schema; identify all decision and evidence requirements",
    "status": "in_progress",
    "priority": "high"
  },
  {
    "content": "Inspect complete frozen source body, metadata, and patch for all 10 records without using model summaries",
    "status": "pending",
    "priority": "high"
  },
  {
    "content": "Inspect and validate frozen model codings against source and schema",
    "status": "pending",
    "priority": "high"
  },
  {
    "content": "Produce complete final codings, rationales, and graph-edge revisions for all records",
    "status": "pending",
    "priority": "high"
  },
  {
    "content": "Validate output completeness, exact quotes, source IDs, and protocol compliance",
    "status": "pending",
    "priority": "high"
  }
]

<path>/home/byk/Code/institutional-transition-lab/research/oss-governance-coding-protocol-v1.2.md</path>
<type>file</type>
<content>
1: # Performance-blinded OSS governance coding protocol v1.2
2: 
3: Date frozen: 2026-08-27  
4: Status: pre-adjudication evaluator correction; model-informed development protocol
5: 
6: ## Correction
7: 
8: The V1.1 run used the intended frozen 40-record manifest and unchanged coders.
9: Its mandatory artifact audit found that the evaluator's field named “strict
10: edge agreement” compared actor, right, target, direction, and status but omitted
11: edge scope and evidence references. It also did not route disagreements in the
12: separately coded body/patch relationship. Six records were consequently called
13: `provisional_exact_agreement` despite material differences.
14: 
15: V1.2 corrects the evaluator before any source adjudication or canonical graph
16: construction:
17: 
18: - strict edge signatures now include scope and the complete grounded ...

<path>/home/byk/Code/institutional-transition-lab/schema/governance-coding-v1.schema.json</path>
<type>file</type>
<content>
1: {
2:   "$schema": "https://json-schema.org/draft/2020-12/schema",
3:   "$id": "https://github.com/BYK/institutional-transition-lab/schema/governance-coding-v1.schema.json",
4:   "title": "Performance-blinded governance coding v1",
5:   "type": "object",
6:   "additionalProperties": false,
7:   "required": ["record_class", "event_kind", "title", "announced_on", "effective_on", "affected_scope", "body_patch_relation", "power_changes", "confidence", "ambiguity"],
8:   "properties": {
9:     "record_class": {"enum": ["effective_institutional_change", "announced_institutional_change", "proposal_only", "control_event", "no_event", "abstain"]},
10:     "event_kind": {"type": ["string", "null"], "enum": ["leadership", "board_or_steering", "control_rights", "reorganization", "foundation_transfer", "license", "fork", "reunification", "strategy", "product", "external", ...

<path>/tmp/opencode/institutional-transition-adjudication-9642983578/documents.json</path>
<type>file</type>
<content>
1: {
2:   "coding_id": "oss-governance-enriched-coding-v1",
3:   "coding_schema_sha256": "bfc735a7d8602d1f236a88c2d23b195f0600a8bae86fb8c8936afe7883a41b8e",
4:   "design_status": "performance_blinded_model_informed_development",
5:   "documents": [
6:     {
7:       "entity_id": "opentofu",
8:       "evidence_bounds": {
9:         "files_listing_complete": null,
10:         "patch_selection_truncated": false,
11:         "patch_unavailable_count": 0,
12:         "source_text_truncated": false
13:       },
14:       "published_on": "2024-03-08",
15:       "publisher": "opentofu/opentofu",
16:       "record_id": "opentofu-github-issue-1353",
17:       "source_type": "github_issue",
18:       "source_url": "https://github.com/opentofu/opentofu/issues/1353",
19:       "sources": [
20:         {
21:           "filename": null,
22:           "kind": "github_body",
23:       ...

{"record_id":"opentofu-github-issue-1353","entity_id":"opentofu","evidence_bounds":{"files_listing_complete":null,"patch_selection_truncated":false,"patch_unavailable_count":0,"source_text_truncated":false},"published_on":"2024-03-08","publisher":"opentofu/opentofu","source_type":"github_issue","source_url":"https://github.com/opentofu/opentofu/issues/1353","sources":[{"source_id":"body","kind":"github_body","filename":null,"text_length":7254}]}
{"record_id":"opentofu-github-issue-2109","entity_id":"opentofu","evidence_bounds":{"files_listing_complete":null,"patch_selection_truncated":false,"patch_unavailable_count":0,"source_text_truncated":false},"published_on":"2024-10-28","publisher":"opentofu/opentofu","source_type":"github_issue","source_url":"https://github.com/opentofu/opentofu/issues/2109","sources":[{"source_id":"body","kind":"github_body","filename":null,"text_length":4102}]}
{"record_id":"opentofu-github-issue-2573","entity_id":"opentofu","evidence_bounds":{"files_listing_c...

{
  "record_id": "opentofu-github-issue-1353",
  "entity_id": "opentofu",
  "evidence_bounds": {
    "files_listing_complete": null,
    "patch_selection_truncated": false,
    "patch_unavailable_count": 0,
    "source_text_truncated": false
  },
  "published_on": "2024-03-08",
  "publisher": "opentofu/opentofu",
  "source_type": "github_issue",
  "source_url": "https://github.com/opentofu/opentofu/issues/1353"
}
{
  "source_id": "body",
  "kind": "github_body",
  "filename": null,
  "text": "Creating a style guide/framework for documentation and user interface\n\n### Summary\r\n\r\nHaving a consistent written style across multiple authors can help a large project maintain a uniform voice. A written-down style guide, along with linters (and other automation) and human reviews can help take the guess-work out of what that voice should be, and how to maintain it.\r\n\r\n### Problem Statement\r\n\r\nThe written word is how we communicate with our customers. ...

{
  "record_id": "opentofu-github-issue-2109",
  "entity_id": "opentofu",
  "evidence_bounds": {
    "files_listing_complete": null,
    "patch_selection_truncated": false,
    "patch_unavailable_count": 0,
    "source_text_truncated": false
  },
  "published_on": "2024-10-28",
  "publisher": "opentofu/opentofu",
  "source_type": "github_issue",
  "source_url": "https://github.com/opentofu/opentofu/issues/2109"
}
{
  "source_id": "body",
  "kind": "github_body",
  "filename": null,
  "text": "Add an ability to install providers directly from GitHub\n\n### The problem in your OpenTofu project\r\n\r\nThe current provider registry model, inherited from Terraform and designed by HashiCorp, centralizes control over provider distribution. While this model was effective initially, the registry has now become a potential point of restriction for some users due to political, security, and accessibility concerns. ...

{
  "record_id": "opentofu-github-issue-2573",
  "entity_id": "opentofu",
  "evidence_bounds": {
    "files_listing_complete": null,
    "patch_selection_truncated": false,
    "patch_unavailable_count": 0,
    "source_text_truncated": false
  },
  "published_on": "2025-03-07",
  "publisher": "opentofu/opentofu",
  "source_type": "github_issue",
  "source_url": "https://github.com/opentofu/opentofu/issues/2573"
}
{
  "source_id": "body",
  "kind": "github_body",
  "filename": null,
  "text": "Use correct year in Technical Steering Committee (TSC) Summary\n\nMinor issue, but it looks like the TSC summaries since the beginning of 2025 are still dated in 2024 for [example](https://github.com/opentofu/opentofu/blame/7bb5da582c3930574ede1c3054a372d7c52e5b77/TSC_SUMMARY.md#L11)"
}

{
  "record_id": "opentofu-github-issue-258",
  "entity_id": "opentofu",
  "evidence_bounds": {
    "files_listing_complete": null,
    "patch_selection_truncated": false,
    "patch_unavailable_count": 0,
    "source_text_truncated": false
  },
  "published_on": "2023-09-04",
  "publisher": "opentofu/opentofu",
  "source_type": "github_issue",
  "source_url": "https://github.com/opentofu/opentofu/issues/258"
}
{
  "source_id": "body",
  "kind": "github_body",
  "filename": null,
  "text": "Replace Official Registry\n\nDue to the Public Terraform Registry ToC change, OpenTF will not use it as the default registry.\r\n\r\nHowever, we still want OpenTF to be a drop-in replacement, so all references to providers and modules should work as-is. This is esp. important because people can use modules which themselves reference other modules, and those indirect references are hard to change.\r\n\r\nThis means we need to replace the official registry in OpenTF.\r\n\r\nIt's worth noting that the ...

{
  "record_id": "opentofu-github-issue-340",
  "entity_id": "opentofu",
  "evidence_bounds": {
    "files_listing_complete": null,
    "patch_selection_truncated": false,
    "patch_unavailable_count": 0,
    "source_text_truncated": false
  },
  "published_on": "2023-09-07",
  "publisher": "opentofu/opentofu",
  "source_type": "github_issue",
  "source_url": "https://github.com/opentofu/opentofu/issues/340"
}
{
  "source_id": "body",
  "kind": "github_body",
  "filename": null,
  "text": "Open up github discussions on this repo\n\n### Summary\r\n\r\nEnable github discussions for this repo.\r\n\r\n### Problem Statement\r\n\r\nThere are a lot of questions around the project/code/governance/... especially in the early moments of this project. We could enable github discussions to have a sort of forum with minimal effort from the admin and great value to the community/maintainers. ...

{
  "record_id": "opentofu-github-pr-1010",
  "entity_id": "opentofu",
  "evidence_bounds": {
    "files_listing_complete": true,
    "patch_selection_truncated": false,
    "patch_unavailable_count": 0,
    "source_text_truncated": false
  },
  "published_on": "2023-12-14",
  "publisher": "opentofu/opentofu",
  "source_type": "github_pull_request",
  "source_url": "https://github.com/opentofu/opentofu/pull/1010"
}
{
  "source_id": "body",
  "kind": "github_body",
  "filename": null,
  "text": "Add Technical Steering Committee Summary for 2023-12-11"
}
{
  "source_id": "pr_metadata",
  "kind": "github_pr_metadata",
  "filename": null,
  "text": "{\"base_sha\": \"fff368d2ee8750de01e8f3f1118a8af8dd650797\", \"changed_files\": 1, \"draft\": false, \"head_sha\": \"61eb05ef4910237a6386431f98d008a7f8574234\", \"merge_commit_sha\": \"2d55e6fcde77959a5c3cdbbbdd041eca9715a512\", \"merged\": true, \"merged_at\": \"2023-12-14T10:19:23Z\", \"state\": \"closed\"}"
}
{
  "source_id": "patch:0",
  ...

{
  "record_id": "opentofu-github-pr-1107",
  "entity_id": "opentofu",
  "evidence_bounds": {
    "files_listing_complete": true,
    "patch_selection_truncated": false,
    "patch_unavailable_count": 0,
    "source_text_truncated": false
  },
  "published_on": "2024-01-11",
  "publisher": "opentofu/opentofu",
  "source_type": "github_pull_request",
  "source_url": "https://github.com/opentofu/opentofu/pull/1107"
}
{
  "source_id": "body",
  "kind": "github_body",
  "filename": null,
  "text": "Allow static evaluation of locals and variables for module sources and backends\n\nThis is the initial implementation of a static evaluation context that can be used to evaluate expression that do not rely on any state data (vars/locals only). \r\n\r\nThis pretty closely follows the plan detailed in RFC #1042 as I had already started experimenting with this code and knew roughly what I needed to change.  All of the examples detailed in the RFC should be functional with this PR.\r\n\r\nCurrent ...

{
  "record_id": "opentofu-github-pr-1152",
  "entity_id": "opentofu",
  "evidence_bounds": {
    "files_listing_complete": true,
    "patch_selection_truncated": false,
    "patch_unavailable_count": 0,
    "source_text_truncated": false
  },
  "published_on": "2024-01-19",
  "publisher": "opentofu/opentofu",
  "source_type": "github_pull_request",
  "source_url": "https://github.com/opentofu/opentofu/pull/1152"
}
{
  "source_id": "body",
  "kind": "github_body",
  "filename": null,
  "text": "Add details on who/what/why the TSC is and list of current members\n\nThis information has been referenced in a few places, but it is good to have a clear description in the repo to help explain the issue flow and governance.\r\n\r\nAlso fixed the spelling of Omry Hay's name."
}
{
  "source_id": "pr_metadata",
  "kind": "github_pr_metadata",
  "filename": null,
  "text": "{\"base_sha\": \"86e18c0ec3dcb392633a03cd7036b8c44417ad27\", \"changed_files\": 1, \"draft\": false, \"head_sha\": ...

{
  "record_id": "opentofu-github-pr-1650",
  "entity_id": "opentofu",
  "evidence_bounds": {
    "files_listing_complete": true,
    "patch_selection_truncated": false,
    "patch_unavailable_count": 0,
    "source_text_truncated": false
  },
  "published_on": "2024-05-15",
  "publisher": "opentofu/opentofu",
  "source_type": "github_pull_request",
  "source_url": "https://github.com/opentofu/opentofu/pull/1650"
}
{
  "source_id": "body",
  "kind": "github_body",
  "filename": null,
  "text": "Add Technical Steering Committee missing Summarries through 2024 May\n\n- Added last TSC meeting summary\r\n- Tracked through older meeting minutes that were not posted and added their summaries here - TSC members who take notes will now post these regularly"
}
{
  "source_id": "pr_metadata",
  "kind": "github_pr_metadata",
  "filename": null,
  "text": "{\"base_sha\": \"da1471b8ce5042ce93ffb762800e94f94fb3a6d2\", \"changed_files\": 1, \"draft\": false, \"head_sha\": ...

{
  "record_id": "opentofu-github-pr-2830",
  "entity_id": "opentofu",
  "evidence_bounds": {
    "files_listing_complete": true,
    "patch_selection_truncated": true,
    "patch_unavailable_count": 0,
    "source_text_truncated": false
  },
  "published_on": "2025-05-20",
  "publisher": "opentofu/opentofu",
  "source_type": "github_pull_request",
  "source_url": "https://github.com/opentofu/opentofu/pull/2830"
}
{
  "source_id": "body",
  "kind": "github_body",
  "filename": null,
  "text": "OpenTofu Charter and Governance\n\nThis PR is the result of a long discussion between the founding members  of the OpenTofu project and the Linux Foundation.  We have iterated back and forth to define a governance structure that suits the OpenTofu project and best enables and protects the project.\r\n\r\nThe initial TSC Members are those who have been serving the role prior to the current charter and represent the organizations heavily invested in the future of the OpenTofu project, as well as ...

{
  "source_id": "patch:0",
  "kind": "github_pr_patch",
  "filename": "CHARTER.md",
  "text": "@@ -0,0 +1,140 @@\n+# Technical Charter (the “Charter”) for OpenTofu a Series of LF Projects, LLC\n+\n+| Revision |  Date  |\n+|---|---|\n+| Initial Adoption | September 15, 2023 |\n+| Amendment | May 20, 2025 |\n+\n+This Charter sets forth the responsibilities and procedures for technical contribution to, and oversight of, the OpenTofu open source project, which has been established as OpenTofu, a Series of LF Projects, LLC (the “Project”).  LF Projects, LLC (“LF Projects”) is a Delaware series limited liability company. All contributors and participants (including committers, maintainers, and other technical positions) in the Project (collectively, “Contributors”) must comply with the terms of this Charter.\n+\n+1. **Mission and Scope of the Project**\n+\n+   a. The mission of the Project is to develop and preserve open source infrastructure as code.\n+\n+   b. ...

{
  "source_id": "patch:1",
  "kind": "github_pr_patch",
  "filename": "GOVERNANCE.md",
  "text": "@@ -0,0 +1,73 @@\n+# OpenTofu Governance\n+\n+This document outlines the governance structure for the OpenTofu project, particularly focusing on the Technical Steering Committee (TSC) which has overall responsibility for the technical direction and oversight of the project as defined in the [CHARTER](CHARTER.md).\n+\n+## Technical Steering Committee (TSC)\n+\n+### TSC Membership Addition and Termination\n+#### Adding New TSC Members\n+New TSC members may be added to the TSC by the following process:\n+1. A candidate must be nominated by an existing TSC member\n+2. The candidate must have demonstrated significant contributions to the project, such as:\n+   - Code contributions\n+   - Documentation contributions\n+   - Community engagement and support\n+   - Technical leadership\n+3. The addition of a new TSC member requires a supermajority vote (two-thirds) of the existing TSC ...

{
  "source_id": "patch:2",
  "kind": "github_pr_patch",
  "filename": "CONTRIBUTING.md",
  "text": "@@ -1,490 +1,50 @@\n # Contributing to OpenTofu\n \n-Welcome and thank you for wanting to contribute! \n+Welcome and thank you for wanting to contribute!\n \n ## Get started\n \n - Have a question? Post it in [GitHub Discussions ➡️](https://github.com/orgs/opentofu/discussions) or on the [OpenTofu Slack ➡️](https://opentofu.org/slack/)!\n - Found a bug? [Report it here ➡️](https://github.com/opentofu/opentofu/issues/new?assignees=&labels=bug%2Cpending-decision&projects=&template=bug_report.yml)\n - Have a feature idea? [Submit it here ➡️](https://github.com/opentofu/opentofu/issues/new?assignees=&labels=enhancement%2Cpending-decision&projects=&template=feature_request.yml)\n - Want to help define a complex feature or bug fix? [Write an RFC here ➡️](./rfc/README.md)\n-- Want to provide a proof-of-concept for an issue? Please [submit a draft PR here ...

[
  {
    "content": "Read protocol and coding schema; identify all decision and evidence requirements",
    "status": "completed",
    "priority": "high"
  },
  {
    "content": "Inspect complete frozen source body, metadata, and patch for all 10 records without using model summaries",
    "status": "completed",
    "priority": "high"
  },
  {
    "content": "Inspect and validate frozen model codings against source and schema",
    "status": "in_progress",
    "priority": "high"
  },
  {
    "content": "Produce complete final codings, rationales, and graph-edge revisions for all records",
    "status": "pending",
    "priority": "high"
  },
  {
    "content": "Validate output completeness, exact quotes, source IDs, and protocol compliance",
    "status": "pending",
    "priority": "high"
  }
]

[
  "records",
  "schema_version",
  "summary"
]

"array"

[
  "canonical_ledger_eligible",
  "full_response_agreement",
  "luna_a",
  "luna_b",
  "provisional_core_agreement",
  "record_id",
  "route_reasons",
  "source_url",
  "terra_advisory"
]

{
  "luna_a_type": "object",
  "luna_a_keys": [
    "elapsed_ms",
    "model",
    "reasoning_effort",
    "response",
    "schema_valid",
    "validation_errors"
  ],
  "luna_b_type": "object",
  "luna_b_keys": [
    "elapsed_ms",
    "model",
    "reasoning_effort",
    "response",
    "schema_valid",
    "validation_errors"
  ],
  "terra_type": "object",
  "terra_keys": [
    "elapsed_ms",
    "model",
    "reasoning_effort",
    "response",
    "schema_valid",
    "validation_errors"
  ]
}

[
  {
    "record_id": "opentofu-github-issue-1353",
    "luna_a": {
      "response": {
        "affected_scope": "OpenTofu technical documentation and user interface writing",
        "ambiguity": null,
        "announced_on": "2024-03-08",
        "body_patch_relation": "body_only",
        "confidence": 0.97,
        "effective_on": null,
        "event_kind": "control_rights",
        "power_changes": [
          {
            "actor": "OpenTofu",
            "change_status": "proposed",
            "direction": "added",
            "evidence_refs": [
              {
                "quote": "I'm proposing a _framework_ for technical documentation and user interface writing.",
                "source_id": "body"
              },
              {
                "quote": "getting all authors to set aside their pet styles and use the standard style for OpenTofu.",
                "source_id": "body"
              }
            ],
            "right_kind": "set_policy",
            ...

[
  {
    "record_id": "opentofu-github-pr-1010",
    "luna_a": {
      "response": {
        "affected_scope": "OpenTofu GA release",
        "ambiguity": "The source records a launch-date decision, not evidence that the GA release occurred.",
        "announced_on": "2023-12-14",
        "body_patch_relation": "patch_only",
        "confidence": 0.86,
        "effective_on": null,
        "event_kind": "product",
        "power_changes": [],
        "record_class": "control_event",
        "title": "TSC decides to release OpenTofu GA on January 10"
      },
      "schema_valid": true,
      "validation_errors": []
    },
    "luna_b": {
      "response": {
        "affected_scope": "OpenTofu registry namespace and GA launch timing",
        "ambiguity": null,
        "announced_on": "2023-12-14",
        "body_patch_relation": "consistent",
        "confidence": 0.98,
        "effective_on": null,
        "event_kind": "product",
        "power_changes": [],
        "record_class": ...

[
  {
    "record_id": "opentofu-github-issue-1353",
    "route_reasons": [
      "body_patch_relation_disagreement",
      "class_disagreement",
      "edge_disagreement",
      "event_field_disagreement"
    ],
    "provisional_core_agreement": false,
    "full_response_agreement": false
  },
  {
    "record_id": "opentofu-github-issue-2109",
    "route_reasons": [
      "edge_disagreement"
    ],
    "provisional_core_agreement": false,
    "full_response_agreement": false
  },
  {
    "record_id": "opentofu-github-issue-2573",
    "route_reasons": [],
    "provisional_core_agreement": true,
    "full_response_agreement": false
  },
  {
    "record_id": "opentofu-github-issue-258",
    "route_reasons": [
      "body_patch_relation_disagreement"
    ],
    "provisional_core_agreement": false,
    "full_response_agreement": false
  },
  {
    "record_id": "opentofu-github-issue-340",
    "route_reasons": [
      "body_patch_relation_disagreement",
      "class_disagreement",
      ...

<path>/home/byk/Code/institutional-transition-lab/research/oss-governance-coding-protocol-v1.2.md</path>
<type>file</type>
<content>
1: # Performance-blinded OSS governance coding protocol v1.2
2: 
3: Date frozen: 2026-08-27  
4: Status: pre-adjudication evaluator correction; model-informed development protocol
5: 
6: ## Correction
7: 
8: The V1.1 run used the intended frozen 40-record manifest and unchanged coders.
9: Its mandatory artifact audit found that the evaluator's field named “strict
10: edge agreement” compared actor, right, target, direction, and status but omitted
11: edge scope and evidence references. It also did not route disagreements in the
12: separately coded body/patch relationship. Six records were consequently called
13: `provisional_exact_agreement` despite material differences.
14: 
15: V1.2 corrects the evaluator before any source adjudication or canonical graph
16: construction:
17: 
18: - strict edge signatures now include scope and the complete grounded ...

[
  {
    "content": "Read protocol and coding schema and identify all decision/evidence requirements",
    "status": "completed",
    "priority": "high"
  },
  {
    "content": "Inspect complete frozen source body, metadata, and patch for all 10 records without model summaries",
    "status": "in_progress",
    "priority": "high"
  },
  {
    "content": "Inspect and validate frozen model codings against source and schema",
    "status": "pending",
    "priority": "high"
  },
  {
    "content": "Produce complete final codings, rationales, and graph-edge revisions",
    "status": "pending",
    "priority": "high"
  },
  {
    "content": "Validate output completeness, exact quotes, source IDs, and protocol compliance",
    "status": "pending",
    "priority": "high"
  }
]

<path>/tmp/opencode/institutional-transition-adjudication-9642983578/documents.json</path>
<type>file</type>
<content>
1: {
2:   "coding_id": "oss-governance-enriched-coding-v1",
3:   "coding_schema_sha256": "bfc735a7d8602d1f236a88c2d23b195f0600a8bae86fb8c8936afe7883a41b8e",
4:   "design_status": "performance_blinded_model_informed_development",
5:   "documents": [
6:     {
7:       "entity_id": "opentofu",
8:       "evidence_bounds": {
9:         "files_listing_complete": null,
10:         "patch_selection_truncated": false,
11:         "patch_unavailable_count": 0,
12:         "source_text_truncated": false
13:       },
14:       "published_on": "2024-03-08",
15:       "publisher": "opentofu/opentofu",
16:       "record_id": "opentofu-github-issue-1353",
17:       "source_type": "github_issue",
18:       "source_url": "https://github.com/opentofu/opentofu/issues/1353",
19:       "sources": [
20:         {
21:           "filename": null,
22:           "kind": "github_body",
23:       ...

RECORD_ID: opentofu-github-issue-1353
PUBLISHED_ON: 2024-03-08
SOURCE_URL: https://github.com/opentofu/opentofu/issues/1353
EVIDENCE_BOUNDS: {"files_listing_complete":null,"patch_selection_truncated":false,"patch_unavailable_count":0,"source_text_truncated":false}
SOURCE_ID: body
KIND: github_body
FILENAME: null
TEXT:
Creating a style guide/framework for documentation and user interface

### Summary

Having a consistent written style across multiple authors can help a large project maintain a uniform voice. A written-down style guide, along with linters (and other automation) and human reviews can help take the guess-work out of what that voice should be, and how to maintain it.

### Problem Statement

The written word is how we communicate with our customers. In places where communication is more formal (e.g., the official website, the `tofu` tool itself), having a consistent voice across multiple writers helps lend subconscious legitimacy to the project. ...

RECORD_ID: opentofu-github-pr-1010
PUBLISHED_ON: 2023-12-14
SOURCE_URL: https://github.com/opentofu/opentofu/pull/1010
EVIDENCE_BOUNDS: {"files_listing_complete":true,"patch_selection_truncated":false,"patch_unavailable_count":0,"source_text_truncated":false}
SOURCE_ID: body
KIND: github_body
FILENAME: null
TEXT:
Add Technical Steering Committee Summary for 2023-12-11
END_SOURCE
END_RECORD

RECORD_ID: opentofu-github-pr-1010
PUBLISHED_ON: 2023-12-14
SOURCE_URL: https://github.com/opentofu/opentofu/pull/1010
EVIDENCE_BOUNDS: {"files_listing_complete":true,"patch_selection_truncated":false,"patch_unavailable_count":0,"source_text_truncated":false}
SOURCE_ID: pr_metadata
KIND: github_pr_metadata
FILENAME: null
TEXT:
{"base_sha": "fff368d2ee8750de01e8f3f1118a8af8dd650797", "changed_files": 1, "draft": false, "head_sha": "61eb05ef4910237a6386431f98d008a7f8574234", "merge_commit_sha": "2d55e6fcde77959a5c3cdbbbdd041eca9715a512", "merged": true, "merged_at": "2023-12-14T10:19:23Z", "state": ...

RECORD_ID: opentofu-github-pr-1650
PUBLISHED_ON: 2024-05-15
SOURCE_URL: https://github.com/opentofu/opentofu/pull/1650
EVIDENCE_BOUNDS: {"files_listing_complete":true,"patch_selection_truncated":false,"patch_unavailable_count":0,"source_text_truncated":false}
SOURCE_ID: body
KIND: github_body
FILENAME: null
TEXT:
Add Technical Steering Committee missing Summarries through 2024 May

- Added last TSC meeting summary
- Tracked through older meeting minutes that were not posted and added their summaries here - TSC members who take notes will now post these regularly
END_SOURCE
END_RECORD

RECORD_ID: opentofu-github-pr-1650
PUBLISHED_ON: 2024-05-15
SOURCE_URL: https://github.com/opentofu/opentofu/pull/1650
EVIDENCE_BOUNDS: {"files_listing_complete":true,"patch_selection_truncated":false,"patch_unavailable_count":0,"source_text_truncated":false}
SOURCE_ID: pr_metadata
KIND: github_pr_metadata
FILENAME: null
TEXT:
{"base_sha": "da1471b8ce5042ce93ffb762800e94f94fb3a6d2", "changed_files": 1, ...

RECORD_ID: opentofu-github-pr-2830
PUBLISHED_ON: 2025-05-20
PUBLISHER: opentofu/opentofu
SOURCE_TYPE: github_pull_request
SOURCE_URL: https://github.com/opentofu/opentofu/pull/2830
EVIDENCE_BOUNDS: {"files_listing_complete":true,"patch_selection_truncated":true,"patch_unavailable_count":0,"source_text_truncated":false}
SOURCE_ID: body
KIND: github_body
FILENAME: null
TEXT:
OpenTofu Charter and Governance

This PR is the result of a long discussion between the founding members  of the OpenTofu project and the Linux Foundation.  We have iterated back and forth to define a governance structure that suits the OpenTofu project and best enables and protects the project.

The initial TSC Members are those who have been serving the role prior to the current charter and represent the organizations heavily invested in the future of the OpenTofu project, as well as myself as the current Technical Lead. ...

SOURCE_ID: patch:0
KIND: github_pr_patch
FILENAME: CHARTER.md
TEXT:
@@ -0,0 +1,140 @@
+# Technical Charter (the “Charter”) for OpenTofu a Series of LF Projects, LLC
+
+| Revision |  Date  |
+|---|---|
+| Initial Adoption | September 15, 2023 |
+| Amendment | May 20, 2025 |
+
+This Charter sets forth the responsibilities and procedures for technical contribution to, and oversight of, the OpenTofu open source project, which has been established as OpenTofu, a Series of LF Projects, LLC (the “Project”).  LF Projects, LLC (“LF Projects”) is a Delaware series limited liability company. All contributors and participants (including committers, maintainers, and other technical positions) in the Project (collectively, “Contributors”) must comply with the terms of this Charter.
+
+1. **Mission and Scope of the Project**
+
+   a. The mission of the Project is to develop and preserve open source infrastructure as code.
+
+   b. ...

SOURCE_ID: patch:1
KIND: github_pr_patch
FILENAME: GOVERNANCE.md
TEXT:
@@ -0,0 +1,73 @@
+# OpenTofu Governance
+
+This document outlines the governance structure for the OpenTofu project, particularly focusing on the Technical Steering Committee (TSC) which has overall responsibility for the technical direction and oversight of the project as defined in the [CHARTER](CHARTER.md).
+
+## Technical Steering Committee (TSC)
+
+### TSC Membership Addition and Termination
+#### Adding New TSC Members
+New TSC members may be added to the TSC by the following process:
+1. A candidate must be nominated by an existing TSC member
+2. The candidate must have demonstrated significant contributions to the project, such as:
+   - Code contributions
+   - Documentation contributions
+   - Community engagement and support
+   - Technical leadership
+3. The addition of a new TSC member requires a supermajority vote (two-thirds) of the existing TSC members
+4. ...

SOURCE_ID: patch:2
KIND: github_pr_patch
FILENAME: CONTRIBUTING.md
TEXT:
@@ -1,490 +1,50 @@
 # Contributing to OpenTofu
 
-Welcome and thank you for wanting to contribute! 
+Welcome and thank you for wanting to contribute!
 
 ## Get started
 
 - Have a question? Post it in [GitHub Discussions ➡️](https://github.com/orgs/opentofu/discussions) or on the [OpenTofu Slack ➡️](https://opentofu.org/slack/)!
 - Found a bug? [Report it here ➡️](https://github.com/opentofu/opentofu/issues/new?assignees=&labels=bug%2Cpending-decision&projects=&template=bug_report.yml)
 - Have a feature idea? [Submit it here ➡️](https://github.com/opentofu/opentofu/issues/new?assignees=&labels=enhancement%2Cpending-decision&projects=&template=feature_request.yml)
 - Want to help define a complex feature or bug fix? [Write an RFC here ➡️](./rfc/README.md)
-- Want to provide a proof-of-concept for an issue? Please [submit a draft PR here ➡️](https://github.com/opentofu/opentofu/compare)
-- Want to add a feature, ...

[
  {
    "content": "Read protocol and coding schema and identify all decision/evidence requirements",
    "status": "completed",
    "priority": "high"
  },
  {
    "content": "Inspect complete frozen source body, metadata, and patch for all 10 records without model summaries",
    "status": "completed",
    "priority": "high"
  },
  {
    "content": "Inspect and validate frozen model codings against source and schema",
    "status": "in_progress",
    "priority": "high"
  },
  {
    "content": "Produce complete final codings, rationales, and graph-edge revisions",
    "status": "pending",
    "priority": "high"
  },
  {
    "content": "Validate output completeness, exact quotes, source IDs, and protocol compliance",
    "status": "pending",
    "priority": "high"
  }
]

<path>/tmp/opencode/institutional-transition-adjudication-9642983578/v1.2-adjudication-package.json</path>
<type>file</type>
<content>
1: {
2:   "records": [
3:     {
4:       "canonical_ledger_eligible": false,
5:       "full_response_agreement": false,
6:       "luna_a": {
7:         "elapsed_ms": 10610,
8:         "model": "gpt-5.6-luna",
9:         "reasoning_effort": "medium",
10:         "response": {
11:           "affected_scope": "OpenTofu technical documentation and user interface writing",
12:           "ambiguity": null,
13:           "announced_on": "2024-03-08",
14:           "body_patch_relation": "body_only",
15:           "confidence": 0.97,
16:           "effective_on": null,
17:           "event_kind": "control_rights",
18:           "power_changes": [
19:             {
20:               "actor": "OpenTofu",
21:               "change_status": "proposed",
22:               "direction": "added",
23:               "evidence_refs": [
24:                 {
25:            ...

{
  "record_id": "opentofu-github-issue-1353",
  "luna_a": {
    "affected_scope": "OpenTofu technical documentation and user interface writing",
    "ambiguity": null,
    "announced_on": "2024-03-08",
    "body_patch_relation": "body_only",
    "confidence": 0.97,
    "effective_on": null,
    "event_kind": "control_rights",
    "power_changes": [
      {
        "actor": "OpenTofu",
        "change_status": "proposed",
        "direction": "added",
        "evidence_refs": [
          {
            "quote": "I'm proposing a _framework_ for technical documentation and user interface writing.",
            "source_id": "body"
          },
          {
            "quote": "getting all authors to set aside their pet styles and use the standard style for OpenTofu.",
            "source_id": "body"
          }
        ],
        "right_kind": "set_policy",
        "scope": "OpenTofu project",
        "target": "technical documentation and user interface writing"
      }
    ],
    ...

{
  "record_id": "opentofu-github-issue-2109",
  "luna_a": {
    "affected_scope": "OpenTofu provider installation and distribution",
    "ambiguity": null,
    "announced_on": "2024-10-28",
    "body_patch_relation": "body_only",
    "confidence": 0.98,
    "effective_on": null,
    "event_kind": "control_rights",
    "power_changes": [
      {
        "actor": "users",
        "change_status": "proposed",
        "direction": "added",
        "evidence_refs": [
          {
            "quote": "This would enable users to specify a GitHub repository as a provider source, allowing for more flexible and decentralized provider management.",
            "source_id": "body"
          }
        ],
        "right_kind": "override",
        "scope": "provider installation and access",
        "target": "centralized registry"
      }
    ],
    "record_class": "proposal_only",
    "title": "Proposal for direct GitHub provider installation"
  },
  "luna_b": {
    "affected_scope": "OpenTofu ...

{
  "record_id": "opentofu-github-issue-258",
  "luna_a": {
    "affected_scope": "OpenTofu registry design",
    "ambiguity": null,
    "announced_on": "2023-11-03",
    "body_patch_relation": "body_only",
    "confidence": 0.98,
    "effective_on": null,
    "event_kind": "product",
    "power_changes": [],
    "record_class": "control_event",
    "title": "Homebrew-like registry design chosen for implementation"
  },
  "luna_b": {
    "affected_scope": "OpenTofu registry design",
    "ambiguity": null,
    "announced_on": "2023-11-03",
    "body_patch_relation": "not_applicable",
    "confidence": 0.96,
    "effective_on": null,
    "event_kind": "product",
    "power_changes": [],
    "record_class": "control_event",
    "title": "Homebrew-like registry design chosen for implementation"
  },
  "terra_advisory": {
    "affected_scope": "OpenTofu stable registry design",
    "ambiguity": null,
    "announced_on": "2023-11-03",
    "body_patch_relation": "body_only",
    ...

{
  "record_id": "opentofu-github-pr-1010",
  "luna_a": {
    "affected_scope": "OpenTofu GA release",
    "ambiguity": "The source records a launch-date decision, not evidence that the GA release occurred.",
    "announced_on": "2023-12-14",
    "body_patch_relation": "patch_only",
    "confidence": 0.86,
    "effective_on": null,
    "event_kind": "product",
    "power_changes": [],
    "record_class": "control_event",
    "title": "TSC decides to release OpenTofu GA on January 10"
  },
  "luna_b": {
    "affected_scope": "OpenTofu registry namespace and GA launch timing",
    "ambiguity": null,
    "announced_on": "2023-12-14",
    "body_patch_relation": "consistent",
    "confidence": 0.98,
    "effective_on": null,
    "event_kind": "product",
    "power_changes": [],
    "record_class": "control_event",
    "title": "TSC summary covering registry namespace and GA launch decisions"
  },
  "terra_advisory": {
    "affected_scope": "OpenTofu registry namespace, GA launch timing, ...

{
  "record_id": "opentofu-github-pr-1152",
  "luna_a": {
    "affected_scope": "OpenTofu Technical Steering Committee documentation",
    "ambiguity": "The merged patch documents the TSC's existing decision authority and membership but does not show that organizational rights changed.",
    "announced_on": null,
    "body_patch_relation": "consistent",
    "confidence": 0.93,
    "effective_on": null,
    "event_kind": null,
    "power_changes": [],
    "record_class": "no_event",
    "title": "TSC governance summary added"
  },
  "luna_b": {
    "affected_scope": "OpenTofu Technical Steering Committee documentation",
    "ambiguity": null,
    "announced_on": null,
    "body_patch_relation": "consistent",
    "confidence": 0.95,
    "effective_on": null,
    "event_kind": null,
    "power_changes": [],
    "record_class": "no_event",
    "title": "Added TSC summary and current members"
  },
  "terra_advisory": null
}
{
  "record_id": "opentofu-github-pr-1650",
  "luna_a": {
    ...

<path>/home/byk/Code/institutional-transition-lab/schema/governance-coding-v1.schema.json</path>
<type>file</type>
<content>
1: {
2:   "$schema": "https://json-schema.org/draft/2020-12/schema",
3:   "$id": "https://github.com/BYK/institutional-transition-lab/schema/governance-coding-v1.schema.json",
4:   "title": "Performance-blinded governance coding v1",
5:   "type": "object",
6:   "additionalProperties": false,
7:   "required": ["record_class", "event_kind", "title", "announced_on", "effective_on", "affected_scope", "body_patch_relation", "power_changes", "confidence", "ambiguity"],
8:   "properties": {
9:     "record_class": {"enum": ["effective_institutional_change", "announced_institutional_change", "proposal_only", "control_event", "no_event", "abstain"]},
10:     "event_kind": {"type": ["string", "null"], "enum": ["leadership", "board_or_steering", "control_rights", "reorganization", "foundation_transfer", "license", "fork", "reunification", "strategy", "product", "external", ...

jq: error: Could not open file /tmp/opencode/institutional-transition-adjudication-9642983578/v1.2-adjudication-package.json: No such file or directory

No files found

No files found

<path>/home/byk/Code/institutional-transition-lab/research/oss-governance-coding-protocol-v1.2.md</path>
<type>file</type>
<content>
1: # Performance-blinded OSS governance coding protocol v1.2
2: 
3: Date frozen: 2026-08-27  
4: Status: pre-adjudication evaluator correction; model-informed development protocol
5: 
6: ## Correction
7: 
8: The V1.1 run used the intended frozen 40-record manifest and unchanged coders.
9: Its mandatory artifact audit found that the evaluator's field named “strict
10: edge agreement” compared actor, right, target, direction, and status but omitted
11: edge scope and evidence references. It also did not route disagreements in the
12: separately coded body/patch relationship. Six records were consequently called
13: `provisional_exact_agreement` despite material differences.
14: 
15: V1.2 corrects the evaluator before any source adjudication or canonical graph
16: construction:
17: 
18: - strict edge signatures now include scope and the complete grounded ...

2a62ab05687982c112a29f6126227c26c3ff8defc89ca64662753aaf85c3c0ce  cases/review/oss-governance-adjudication-v1/documents.json
14644759f53071adfe1173d4e25bb01931b8c1591fa8a48295dbd0556a754769  cases/review/oss-governance-adjudication-v1/v1.2-coding-package.json

[
  "coding_id",
  "coding_schema_sha256",
  "design_status",
  "documents",
  "model_input_fields",
  "outcome_data_used",
  "schema_version",
  "transition_dates_excluded"
]
[
  "entity_id",
  "evidence_bounds",
  "published_on",
  "publisher",
  "record_id",
  "source_type",
  "source_url",
  "sources"
]

{
  "record_id": "opentofu-github-pr-1650",
  "published_on": "2024-05-15",
  "evidence_bounds": {
    "files_listing_complete": true,
    "patch_selection_truncated": false,
    "patch_unavailable_count": 0,
    "source_text_truncated": false
  },
  "sources": [
    {
      "source_id": "body",
      "source_type": null,
      "path": null,
      "text_keys": [
        "filename",
        "kind",
        "source_id",
        "text"
      ]
    },
    {
      "source_id": "pr_metadata",
      "source_type": null,
      "path": null,
      "text_keys": [
        "filename",
        "kind",
        "source_id",
        "text"
      ]
    },
    {
      "source_id": "patch:0",
      "source_type": null,
      "path": null,
      "text_keys": [
        "filename",
        "kind",
        "source_id",
        "text"
      ]
    }
  ]
}

body	- Tracked through older meeting minutes that were not posted and added their summaries here - TSC members who take notes will now post these regularly
patch:0	+    - From now on, whomever takes notes during the TSC meeting will also open the PR posting the public notes

pr_metadata	{"base_sha": "6f0d3d3a07a49309b30960d57225c9f7c701e9a9", "changed_files": 43, "draft": false, "head_sha": "da4ac00ca09d1d9e06e47efd77523a235d49f10c", "merge_commit_sha": "59d24390b712b87954ee175c38912e56d8f5d974", "merged": true, "merged_at": "2025-05-23T12:18:56Z", "state": "closed"}
patch:0	+   a. The Technical Steering Committee (the “TSC”) will be responsible for all technical oversight of the open source Project.	+      * iii. A Contributor may become a Committer by approval of the TSC. A Committer may be removed by a majority approval of the TSC.
patch:1	+3. **Removal for Cause**:	+The TSC is responsible for all technical oversight of the OpenTofu project, including, but not limited to:	+1. The TSC has ultimate authority over all projects in the OpenTofu organization.	+2. The TSC may delegate decision-making authority to maintainers of specific projects:	+3. ...

137:+- @Roger Simms similar
138:+- @Wojciech Barczyński similar but we should reconsider again for next version.
139:+- @Roni Frantchi similar
140:+
141:+#### Decision:
142:+
143:+Reconsider in 6 months
144:+
145:+### The TSC never posted on GitHub summary since February
146:+
147:+- We should discuss who owns this
148:+    - AI: @Roni Frantchi will backtrack and post the summaries of all meetings dating back to Feb
149:+    - From now on, whomever takes notes during the TSC meeting will also open the PR posting the public notes
150:+
151:+### Change docs license in the charter to Mozilla as asked by Linux Foundation
152:+
153:+#### Decision:
154:+
155:+Yes.
156:+

{
  "schema_version": 1,
  "coding_id": "oss-governance-enriched-coding-v1",
  "model_input_fields": [
    "entity_id",
    "publisher",
    "published_on",
    "source_type",
    "sources",
    "evidence_bounds"
  ],
  "outcome_data_used": false,
  "transition_dates_excluded": true,
  "design_status": "performance_blinded_model_informed_development"
}

opentofu-github-issue-1353	2024-03-08	github_issue	body	false	false
opentofu-github-issue-2109	2024-10-28	github_issue	body	false	false
opentofu-github-issue-2573	2025-03-07	github_issue	body	false	false
opentofu-github-issue-258	2023-09-04	github_issue	body	false	false
opentofu-github-issue-340	2023-09-07	github_issue	body	false	false
opentofu-github-pr-1010	2023-12-14	github_pull_request	body,pr_metadata,patch:0	false	false
opentofu-github-pr-1107	2024-01-11	github_pull_request	body,pr_metadata,patch:0	false	false
opentofu-github-pr-1152	2024-01-19	github_pull_request	body,pr_metadata,patch:0	false	false
opentofu-github-pr-1650	2024-05-15	github_pull_request	body,pr_metadata,patch:0	false	false
opentofu-github-pr-2830	2025-05-20	github_pull_request	body,pr_metadata,patch:0,patch:1,patch:2	true	false

@@ -8,6 +8,323 @@ The Technical Steering Committee is a group comprised of people from companies a
 - Wojciech Barczynski ([@wojciech12](https://github.com/wojciech12)) representing Spacelift Inc.
 - Yevgeniy Brikman ([@brikis98](https://github.com/brikis98)) representing Gruntwork, Inc.
 
+## 2024-05-07
+
+## Agenda
+
+### RFC: Init-time Constant Evaluation Proposal
+
+https://github.com/opentofu/opentofu/issues/1042
+This feature is a composable language addition that idiomatically solves many common top user requests (see linked issues):
+
+- Module sources using variables/locals https://github.com/opentofu/opentofu/issues/286https://github.com/opentofu/opentofu/issues/1017
+- Providers for_each support https://github.com/opentofu/opentofu/issues/300
+- Module provider mappings from variables/for_each https://github.com/opentofu/opentofu/issues/300
+- Backend configurations using variables/locals https://github.com/opentofu/opentofu/issues/388
+- Lifecycle attributes must be known ...

OpenTofu Charter and Governance

This PR is the result of a long discussion between the founding members  of the OpenTofu project and the Linux Foundation.  We have iterated back and forth to define a governance structure that suits the OpenTofu project and best enables and protects the project.

The initial TSC Members are those who have been serving the role prior to the current charter and represent the organizations heavily invested in the future of the OpenTofu project, as well as myself as the current Technical Lead.

Our goal is that this change will allow the community to interact with the OpenTofu project at a deeper level.  Due to necessity, we started in the "Cathedral"[1], with the goal to move toward the "Bazaar".  This is a large step in following through on that vision.

[1] http://www.catb.org/esr/writings/cathedral-bazaar/

17:+3. The addition of a new TSC member requires a supermajority vote (two-thirds) of the existing TSC members
21:+1. **Voluntary Resignation**: A TSC member may resign at any time by notifying the TSC in writing. No vote is required to accept a resignation.
22:+2. **Removal for Inactivity**:
26:+3. **Removal for Cause**:
28:+   - Removal for cause requires a supermajority vote (two-thirds) of the TSC, excluding the member in question
74:+This governance document may be amended by a two-thirds vote of the entire TSC and is subject to approval by LF Projects.

@@ -0,0 +1,73 @@
+# OpenTofu Governance
+
+This document outlines the governance structure for the OpenTofu project, particularly focusing on the Technical Steering Committee (TSC) which has overall responsibility for the technical direction and oversight of the project as defined in the [CHARTER](CHARTER.md).
+
+## Technical Steering Committee (TSC)
+
+### TSC Membership Addition and Termination
+#### Adding New TSC Members
+New TSC members may be added to the TSC by the following process:
+1. A candidate must be nominated by an existing TSC member
+2. The candidate must have demonstrated significant contributions to the project, such as:
+   - Code contributions
+   - Documentation contributions
+   - Community engagement and support
+   - Technical leadership
+3. The addition of a new TSC member requires a supermajority vote (two-thirds) of the existing TSC members
+4. ...

@@ -0,0 +1,140 @@
+# Technical Charter (the “Charter”) for OpenTofu a Series of LF Projects, LLC
+
+| Revision |  Date  |
+|---|---|
+| Initial Adoption | September 15, 2023 |
+| Amendment | May 20, 2025 |
+
+This Charter sets forth the responsibilities and procedures for technical contribution to, and oversight of, the OpenTofu open source project, which has been established as OpenTofu, a Series of LF Projects, LLC (the “Project”).  LF Projects, LLC (“LF Projects”) is a Delaware series limited liability company. All contributors and participants (including committers, maintainers, and other technical positions) in the Project (collectively, “Contributors”) must comply with the terms of this Charter.
+
+1. **Mission and Scope of the Project**
+
+   a. The mission of the Project is to develop and preserve open source infrastructure as code.
+
+   b. ...

76:+
77:+#### Discussion:
78:+
79:+- @Igor Savchenko thinks we should move forward - but we should have consider performance testing on large configurations and how those are impacted by the change. Also imported to note - this ***will*** break Terraform support.
80:+- @Wojciech Barczyński reinforces that
81:+- @Roger Simms 👍
82:+- @Roni Frantchi asks - considering this is extending language features, and linters/language servers may raise errors or warnings if one uses this configuration - does that mean we will support that on .otf files only?
83:+
84:+#### Decision:
85:+
86:+- RFC accepted
87:+- Ask core team to be mindful and rigorously test performance
88:+- Strong recommendation to core team for consideration: if possible, the TSC’s preference is to roll out support for the above in iterations to limit the blast radius:
89:+    1. Module source resolution
90:+    2. Dynamic provider config
91:+    3. …
92:+
93:+### Alternate file extension .OTF for OpenTofu Specific ...

[
  {
    "content": "Read protocol and coding schema and identify all decision/evidence requirements",
    "status": "completed",
    "priority": "high"
  },
  {
    "content": "Inspect complete frozen source body, metadata, and patch for all 10 records without model summaries",
    "status": "completed",
    "priority": "high"
  },
  {
    "content": "Inspect and validate frozen model codings against source and schema",
    "status": "completed",
    "priority": "high"
  },
  {
    "content": "Produce complete final codings, rationales, and graph-edge revisions",
    "status": "in_progress",
    "priority": "high"
  },
  {
    "content": "Validate output completeness, exact quotes, source IDs, and protocol compliance",
    "status": "pending",
    "priority": "high"
  }
]

<path>/home/byk/Code/institutional-transition-lab/research/oss-governance-coding-protocol-v1.2.md</path>
<type>file</type>
<content>
1: # Performance-blinded OSS governance coding protocol v1.2
2: 
3: Date frozen: 2026-08-27  
4: Status: pre-adjudication evaluator correction; model-informed development protocol
5: 
6: ## Correction
7: 
8: The V1.1 run used the intended frozen 40-record manifest and unchanged coders.
9: Its mandatory artifact audit found that the evaluator's field named “strict
10: edge agreement” compared actor, right, target, direction, and status but omitted
11: edge scope and evidence references. It also did not route disagreements in the
12: separately coded body/patch relationship. Six records were consequently called
13: `provisional_exact_agreement` despite material differences.
14: 
15: V1.2 corrects the evaluator before any source adjudication or canonical graph
16: construction:
17: 
18: - strict edge signatures now include scope and the complete grounded ...

<path>/home/byk/Code/institutional-transition-lab/schema/governance-coding-v1.schema.json</path>
<type>file</type>
<content>
1: {
2:   "$schema": "https://json-schema.org/draft/2020-12/schema",
3:   "$id": "https://github.com/BYK/institutional-transition-lab/schema/governance-coding-v1.schema.json",
4:   "title": "Performance-blinded governance coding v1",
5:   "type": "object",
6:   "additionalProperties": false,
7:   "required": ["record_class", "event_kind", "title", "announced_on", "effective_on", "affected_scope", "body_patch_relation", "power_changes", "confidence", "ambiguity"],
8:   "properties": {
9:     "record_class": {"enum": ["effective_institutional_change", "announced_institutional_change", "proposal_only", "control_event", "no_event", "abstain"]},
10:     "event_kind": {"type": ["string", "null"], "enum": ["leadership", "board_or_steering", "control_rights", "reorganization", "foundation_transfer", "license", "fork", "reunification", "strategy", "product", "external", ...

No files found

<path>/tmp/opencode/institutional-transition-adjudication-9642983578/v1.2-adjudication-package.json</path>
<type>file</type>
<content>
1: {
2:   "records": [
3:     {
4:       "canonical_ledger_eligible": false,
5:       "full_response_agreement": false,
6:       "luna_a": {
7:         "elapsed_ms": 10610,
8:         "model": "gpt-5.6-luna",
9:         "reasoning_effort": "medium",
10:         "response": {
11:           "affected_scope": "OpenTofu technical documentation and user interface writing",
12:           "ambiguity": null,
13:           "announced_on": "2024-03-08",
14:           "body_patch_relation": "body_only",
15:           "confidence": 0.97,
16:           "effective_on": null,
17:           "event_kind": "control_rights",
18:           "power_changes": [
19:             {
20:               "actor": "OpenTofu",

(Showing lines 1-20 of 4085. Use offset=21 to continue.)
</content>

[
  {
    "record_id": "opentofu-github-issue-1353",
    "luna_a": {
      "affected_scope": "OpenTofu technical documentation and user interface writing",
      "ambiguity": null,
      "announced_on": "2024-03-08",
      "body_patch_relation": "body_only",
      "confidence": 0.97,
      "effective_on": null,
      "event_kind": "control_rights",
      "power_changes": [
        {
          "actor": "OpenTofu",
          "change_status": "proposed",
          "direction": "added",
          "evidence_refs": [
            {
              "quote": "I'm proposing a _framework_ for technical documentation and user interface writing.",
              "source_id": "body"
            },
            {
              "quote": "getting all authors to set aside their pet styles and use the standard style for OpenTofu.",
              "source_id": "body"
            }
          ],
          "right_kind": "set_policy",
          "scope": "OpenTofu project",
          "target": "technical ...

...output truncated...

Full output saved to: /home/byk/.local/share/opencode/tool-output/tool_082c4317c001zJ22xj3BqiftCN

            {
              "quote": "the TSC retains the right to overrule decisions as necessary",
              "source_id": "patch:1"
            },
            {
              "quote": "\"merged\": true, \"merged_at\": \"2025-05-23T12:18:56Z\"",
              "source_id": "pr_metadata"
            }
          ],
          "right_kind": "override",
          "scope": "all projects in the OpenTofu organization",
          "target": "decisions"
        }
      ],
      "record_class": "effective_institutional_change",
      "title": "OpenTofu Charter and Governance"
    }
  },
  {
    "record_id": "opentofu-github-pr-2953",
    "luna_a": {
      "affected_scope": "OpenTofu governance documents",
      "ambiguity": "The merged patch implements relocation of governance documents, but the supplied evidence does not establish a corresponding organizational rights ...

{
  "record_id": "opentofu-github-pr-1010",
  "luna_a": {
    "affected_scope": "OpenTofu GA release",
    "ambiguity": "The source records a launch-date decision, not evidence that the GA release occurred.",
    "announced_on": "2023-12-14",
    "body_patch_relation": "patch_only",
    "confidence": 0.86,
    "effective_on": null,
    "event_kind": "product",
    "power_changes": [],
    "record_class": "control_event",
    "title": "TSC decides to release OpenTofu GA on January 10"
  },
  "luna_b": {
    "affected_scope": "OpenTofu registry namespace and GA launch timing",
    "ambiguity": null,
    "announced_on": "2023-12-14",
    "body_patch_relation": "consistent",
    "confidence": 0.98,
    "effective_on": null,
    "event_kind": "product",
    "power_changes": [],
    "record_class": "control_event",
    "title": "TSC summary covering registry namespace and GA launch decisions"
  },
  "terra_advisory": {
    "affected_scope": "OpenTofu registry namespace, GA launch timing, ...

{
  "record_id": "opentofu-github-pr-1107",
  "luna_a": {
    "affected_scope": "module sources and backends",
    "ambiguity": "The pull request is closed and unmerged, so implementation effectiveness is not shown.",
    "announced_on": "2024-01-11",
    "body_patch_relation": "consistent",
    "confidence": 0.97,
    "effective_on": null,
    "event_kind": "product",
    "power_changes": [],
    "record_class": "control_event",
    "title": "Allow static evaluation of locals and variables for module sources and backends"
  },
  "luna_b": {
    "affected_scope": "OpenTofu module sources and backends",
    "ambiguity": null,
    "announced_on": "2024-01-11",
    "body_patch_relation": "not_applicable",
    "confidence": 0.98,
    "effective_on": null,
    "event_kind": "product",
    "power_changes": [],
    "record_class": "control_event",
    "title": "Allow static evaluation of locals and variables for module sources and backends"
  },
  "terra_advisory": {
    "affected_scope": ...

{
  "record_id": "opentofu-github-pr-2830",
  "luna_a": {
    "affected_scope": "OpenTofu project",
    "ambiguity": "The patch selection is marked truncated, but the supplied merged patch contains the charter and governance provisions implementing the rights changes.",
    "announced_on": "2025-05-20",
    "body_patch_relation": "consistent",
    "confidence": 0.98,
    "effective_on": "2025-05-23",
    "event_kind": "control_rights",
    "power_changes": [
      {
        "actor": "The Technical Steering Committee (the “TSC”)",
        "change_status": "effective",
        "direction": "added",
        "evidence_refs": [
          {
            "quote": "The Technical Steering Committee (the “TSC”) will be responsible for all technical oversight of the open source Project.",
            "source_id": "patch:0"
          }
        ],
        "right_kind": "set_strategy",
        "scope": "technical oversight and direction of the OpenTofu project",
        "target": "OpenTofu project"
 ...

Add Technical Steering Committee missing Summarries through 2024 May

- Added last TSC meeting summary
- Tracked through older meeting minutes that were not posted and added their summaries here - TSC members who take notes will now post these regularly

2a62ab05687982c112a29f6126227c26c3ff8defc89ca64662753aaf85c3c0ce  cases/review/oss-governance-adjudication-v1/documents.json
14644759f53071adfe1173d4e25bb01931b8c1591fa8a48295dbd0556a754769  cases/review/oss-governance-adjudication-v1/v1.2-coding-package.json

@@ -8,6 +8,323 @@ The Technical Steering Committee is a group comprised of people from companies a
 - Wojciech Barczynski ([@wojciech12](https://github.com/wojciech12)) representing Spacelift Inc.
 - Yevgeniy Brikman ([@brikis98](https://github.com/brikis98)) representing Gruntwork, Inc.
 
+## 2024-05-07
+
+## Agenda
+
+### RFC: Init-time Constant Evaluation Proposal
+
+https://github.com/opentofu/opentofu/issues/1042
+This feature is a composable language addition that idiomatically solves many common top user requests (see linked issues):
+
+- Module sources using variables/locals https://github.com/opentofu/opentofu/issues/286https://github.com/opentofu/opentofu/issues/1017
+- Providers for_each support https://github.com/opentofu/opentofu/issues/300
+- Module provider mappings from variables/for_each https://github.com/opentofu/opentofu/issues/300
+- Backend configurations using variables/locals https://github.com/opentofu/opentofu/issues/388
+- Lifecycle attributes must be known ...

+      * iii. A Contributor may become a Committer by approval of the TSC. A Committer may be removed by a majority approval of the TSC.
+   e. The TSC may elect a TSC Chair, who will preside over meetings of the TSC and will serve until their resignation or replacement by the TSC.  
+   a. LF Projects will hold title to all trade or service marks used by the Project (“Project Trademarks”), whether based on common law or registered rights.  Project Trademarks will be transferred and assigned to LF Projects to hold on behalf of the Project. Any use of any Project Trademarks by Contributors in the Project will be in accordance with the license from LF Projects and inure to the benefit of LF Projects.  

+1. The TSC has ultimate authority over all projects in the OpenTofu organization.
+2. The TSC may delegate decision-making authority to maintainers of specific projects:
+3. While maintainers of specific projects may have decision-making authority, the TSC retains the right to overrule decisions as necessary, though it should show restraint in doing so.

{"base_sha": "6f0d3d3a07a49309b30960d57225c9f7c701e9a9", "changed_files": 43, "draft": false, "head_sha": "da4ac00ca09d1d9e06e47efd77523a235d49f10c", "merge_commit_sha": "59d24390b712b87954ee175c38912e56d8f5d974", "merged": true, "merged_at": "2025-05-23T12:18:56Z", "state": "closed"}

{"base_sha": "da1471b8ce5042ce93ffb762800e94f94fb3a6d2", "changed_files": 1, "draft": false, "head_sha": "0e5a064c6eef77f22205ae307352ecb141515e63", "merge_commit_sha": "2ef3047ec6bb266e8d91c55519967212c1a0975d", "merged": true, "merged_at": "2024-05-16T06:28:54Z", "state": "closed"}

+      * i. Amending this Charter (subject to approval by LF Projects) as outlined in Section 8.
+   e. The TSC will document its decisions in a public file in the main Project repository no later than 14 days after the vote was taken. For decisions not including confidential information, the TSC will include detailed notes on the discussion taken prior to the vote.
+   a. This charter may be amended by a two-thirds vote of the entire TSC and is subject to approval by LF Projects.

Replace Official Registry

Due to the Public Terraform Registry ToC change, OpenTF will not use it as the default registry.

However, we still want OpenTF to be a drop-in replacement, so all references to providers and modules should work as-is. This is esp. important because people can use modules which themselves reference other modules, and those indirect references are hard to change.

This means we need to replace the official registry in OpenTF.

It's worth noting that the registry is mostly a redirector to GitHub, and is heavily coupled with GitHub concepts like Releases. Only HashiCorp provider binaries (not modules) are hosted directly from the registry.

# UPDATE 2023-10-12

Alright, now that we have the alpha release behind us and a working alpha registry, it's time to start the discussion around the stable registry design! This is a design that we'll implement to make OpenTofu production-ready, and will be included in the OpenTofu 1.6 stable release. ...

@@ -0,0 +1,140 @@
+# Technical Charter (the “Charter”) for OpenTofu a Series of LF Projects, LLC
+
+| Revision |  Date  |
+|---|---|
+| Initial Adoption | September 15, 2023 |
+| Amendment | May 20, 2025 |
+
+This Charter sets forth the responsibilities and procedures for technical contribution to, and oversight of, the OpenTofu open source project, which has been established as OpenTofu, a Series of LF Projects, LLC (the “Project”).  LF Projects, LLC (“LF Projects”) is a Delaware series limited liability company. All contributors and participants (including committers, maintainers, and other technical positions) in the Project (collectively, “Contributors”) must comply with the terms of this Charter.
+
+1. **Mission and Scope of the Project**
+
+   a. The mission of the Project is to develop and preserve open source infrastructure as code.
+
+   b. ...

{
  "record_id": "opentofu-github-issue-1353",
  "luna_a": {
    "affected_scope": "OpenTofu technical documentation and user interface writing",
    "ambiguity": null,
    "announced_on": "2024-03-08",
    "body_patch_relation": "body_only",
    "confidence": 0.97,
    "effective_on": null,
    "event_kind": "control_rights",
    "power_changes": [
      {
        "actor": "OpenTofu",
        "change_status": "proposed",
        "direction": "added",
        "evidence_refs": [
          {
            "quote": "I'm proposing a _framework_ for technical documentation and user interface writing.",
            "source_id": "body"
          },
          {
            "quote": "getting all authors to set aside their pet styles and use the standard style for OpenTofu.",
            "source_id": "body"
          }
        ],
        "right_kind": "set_policy",
        "scope": "OpenTofu project",
        "target": "technical documentation and user interface writing"
      }
    ],
    ...

<path>/home/byk/Code/institutional-transition-lab/research/oss-governance-coding-protocol-v1.2.md</path>
<type>file</type>
<content>
1: # Performance-blinded OSS governance coding protocol v1.2
2: 
3: Date frozen: 2026-08-27  
4: Status: pre-adjudication evaluator correction; model-informed development protocol
5: 
6: ## Correction
7: 
8: The V1.1 run used the intended frozen 40-record manifest and unchanged coders.
9: Its mandatory artifact audit found that the evaluator's field named “strict
10: edge agreement” compared actor, right, target, direction, and status but omitted
11: edge scope and evidence references. It also did not route disagreements in the
12: separately coded body/patch relationship. Six records were consequently called
13: `provisional_exact_agreement` despite material differences.
14: 
15: V1.2 corrects the evaluator before any source adjudication or canonical graph
16: construction:
17: 
18: - strict edge signatures now include scope and the complete grounded ...

137-+- @Roger Simms similar
138-+- @Wojciech Barczyński similar but we should reconsider again for next version.
139-+- @Roni Frantchi similar
140-+
141-+#### Decision:
142-+
143-+Reconsider in 6 months
144-+
145:+### The TSC never posted on GitHub summary since February
146-+
147-+- We should discuss who owns this
148-+    - AI: @Roni Frantchi will backtrack and post the summaries of all meetings dating back to Feb
149:+    - From now on, whomever takes notes during the TSC meeting will also open the PR posting the public notes
150-+
151-+### Change docs license in the charter to Mozilla as asked by Linux Foundation
152-+
153-+#### Decision:
154-+
155-+Yes.
156-+
157-+## 2024-04-03

OpenTofu Charter and Governance

This PR is the result of a long discussion between the founding members  of the OpenTofu project and the Linux Foundation.  We have iterated back and forth to define a governance structure that suits the OpenTofu project and best enables and protects the project.

The initial TSC Members are those who have been serving the role prior to the current charter and represent the organizations heavily invested in the future of the OpenTofu project, as well as myself as the current Technical Lead.

Our goal is that this change will allow the community to interact with the OpenTofu project at a deeper level.  Due to necessity, we started in the "Cathedral"[1], with the goal to move toward the "Bazaar".  This is a large step in following through on that vision.

[1] http://www.catb.org/esr/writings/cathedral-bazaar/

Creating a style guide/framework for documentation and user interface

### Summary

Having a consistent written style across multiple authors can help a large project maintain a uniform voice. A written-down style guide, along with linters (and other automation) and human reviews can help take the guess-work out of what that voice should be, and how to maintain it.

### Problem Statement

The written word is how we communicate with our customers. In places where communication is more formal (e.g., the official website, the `tofu` tool itself), having a consistent voice across multiple writers helps lend subconscious legitimacy to the project. There are many people for whom a misspelled word, or poor grammar, can reduce their trust in the thing being presented.

There is also the issue of _clarity_. Technical documentation is a different medium with a different form from things like creative writing, or even writing for user interface (the `tofu` CLI tool is a user interface). ...

55--6. When you commit, use `git commit -s` to sign off your commits.
56--7. Complete the checklist below before you submit your PR (or submit a draft PR).
57--8. Your PR will be reviewed by the core team once it is marked as ready to review.
58-+## Maintainers
59- 
60-----
61-+Maintainers are anyone who is a "Committer" (as defined in the Charter) to one or more repositories.
62- 
63--## PR checklist
64-+The list of current maintainers and their responsibilities can be found in [MAINTAINERS.md](MAINTAINERS.md).
65- 
66--<!-- Make sure to keep this in sync with the PR template. -->
67:+## TSC Members
68- 
69--Please make sure you complete the following checklist before you mark your PR ready for review. If you cannot complete the checklist but want to submit a PR, please submit it as a draft PR. Please note, the core team will only review your PR if you have completed the checklist and marked your PR as ready to review. ...

<path>/home/byk/Code/institutional-transition-lab/schema/governance-coding-v1.schema.json</path>
<type>file</type>
<content>
1: {
2:   "$schema": "https://json-schema.org/draft/2020-12/schema",
3:   "$id": "https://github.com/BYK/institutional-transition-lab/schema/governance-coding-v1.schema.json",
4:   "title": "Performance-blinded governance coding v1",
5:   "type": "object",
6:   "additionalProperties": false,
7:   "required": ["record_class", "event_kind", "title", "announced_on", "effective_on", "affected_scope", "body_patch_relation", "power_changes", "confidence", "ambiguity"],
8:   "properties": {
9:     "record_class": {"enum": ["effective_institutional_change", "announced_institutional_change", "proposal_only", "control_event", "no_event", "abstain"]},
10:     "event_kind": {"type": ["string", "null"], "enum": ["leadership", "board_or_steering", "control_rights", "reorganization", "foundation_transfer", "license", "fork", "reunification", "strategy", "product", "external", ...

{
  "record_id": "opentofu-github-pr-1010",
  "luna_a": {
    "affected_scope": "OpenTofu GA release",
    "ambiguity": "The source records a launch-date decision, not evidence that the GA release occurred.",
    "announced_on": "2023-12-14",
    "body_patch_relation": "patch_only",
    "confidence": 0.86,
    "effective_on": null,
    "event_kind": "product",
    "power_changes": [],
    "record_class": "control_event",
    "title": "TSC decides to release OpenTofu GA on January 10"
  },
  "luna_b": {
    "affected_scope": "OpenTofu registry namespace and GA launch timing",
    "ambiguity": null,
    "announced_on": "2023-12-14",
    "body_patch_relation": "consistent",
    "confidence": 0.98,
    "effective_on": null,
    "event_kind": "product",
    "power_changes": [],
    "record_class": "control_event",
    "title": "TSC summary covering registry namespace and GA launch decisions"
  },
  "terra_advisory": {
    "affected_scope": "OpenTofu registry namespace, GA launch timing, ...

Add Technical Steering Committee missing Summarries through 2024 May

- Added last TSC meeting summary
- Tracked through older meeting minutes that were not posted and added their summaries here - TSC members who take notes will now post these regularly

40-  - Implementation of the registry must be fully open-source.
41-- Strong nice-to-have's
42-  - Download stats for each provider/module.
43-    - This is very useful for discoverability purposes.
44-  - Implements the V1 registry protocol for [providers](https://opentofu.org/docs/internals/provider-registry-protocol) and [modules](https://opentofu.org/docs/internals/module-registry-protocol).
45-    - This means it will work with legacy Terraform and will not require CLI-side changes in OpenTofu.
46-  - It should be easy to host mirrors of this registry.
47-
48:# UPDATE 2023-11-03
49-
50-Important news!
51-
52:The technical steering committee convened yesterday and has chosen the [Homebrew-like registry design](https://github.com/opentofu/opentofu/issues/741) as the one to go with and implement. ...

@@ -0,0 +1,73 @@
+# OpenTofu Governance
+
+This document outlines the governance structure for the OpenTofu project, particularly focusing on the Technical Steering Committee (TSC) which has overall responsibility for the technical direction and oversight of the project as defined in the [CHARTER](CHARTER.md).
+
+## Technical Steering Committee (TSC)
+
+### TSC Membership Addition and Termination
+#### Adding New TSC Members
+New TSC members may be added to the TSC by the following process:
+1. A candidate must be nominated by an existing TSC member
+2. The candidate must have demonstrated significant contributions to the project, such as:
+   - Code contributions
+   - Documentation contributions
+   - Community engagement and support
+   - Technical leadership
+3. The addition of a new TSC member requires a supermajority vote (two-thirds) of the existing TSC members
+4. ...

5:+## 2024-05-07
7:+## Agenda
9:+### RFC: Init-time Constant Evaluation Proposal
93:+### Alternate file extension .OTF for OpenTofu Specific Features
107:+### Next version of OpenTofu - what should it be? 1.8? 2.0?
129:+### Backends as Plugins
145:+### The TSC never posted on GitHub summary since February
151:+### Change docs license in the charter to Mozilla as asked by Linux Foundation
157:+## 2024-04-03
159:+### Attendees:
164:+### Absent:
167:+### Agenda
195:+## 2024-03-06
240:+## 2024-02-27
285:+## 2024-02-21
287:+### Attendees
294:+### Agenda

{
  "record_id": "opentofu-github-issue-1353",
  "luna_a": {
    "affected_scope": "OpenTofu technical documentation and user interface writing",
    "ambiguity": null,
    "announced_on": "2024-03-08",
    "body_patch_relation": "body_only",
    "confidence": 0.97,
    "effective_on": null,
    "event_kind": "control_rights",
    "power_changes": [
      {
        "actor": "OpenTofu",
        "change_status": "proposed",
        "direction": "added",
        "evidence_refs": [
          {
            "quote": "I'm proposing a _framework_ for technical documentation and user interface writing.",
            "source_id": "body"
          },
          {
            "quote": "getting all authors to set aside their pet styles and use the standard style for OpenTofu.",
            "source_id": "body"
          }
        ],
        "right_kind": "set_policy",
        "scope": "OpenTofu project",
        "target": "technical documentation and user interface writing"
      }
    ],
    ...

143-+Reconsider in 6 months
144-+
145-+### The TSC never posted on GitHub summary since February
146-+
147-+- We should discuss who owns this
148-+    - AI: @Roni Frantchi will backtrack and post the summaries of all meetings dating back to Feb
149:+    - From now on, whomever takes notes during the TSC meeting will also open the PR posting the public notes
150-+
151-+### Change docs license in the charter to Mozilla as asked by Linux Foundation
152-+
153-+#### Decision:
154-+
155-+Yes.

@@ -0,0 +1,140 @@
+# Technical Charter (the “Charter”) for OpenTofu a Series of LF Projects, LLC
+
+| Revision |  Date  |
+|---|---|
+| Initial Adoption | September 15, 2023 |
+| Amendment | May 20, 2025 |
+
+This Charter sets forth the responsibilities and procedures for technical contribution to, and oversight of, the OpenTofu open source project, which has been established as OpenTofu, a Series of LF Projects, LLC (the “Project”).  LF Projects, LLC (“LF Projects”) is a Delaware series limited liability company. All contributors and participants (including committers, maintainers, and other technical positions) in the Project (collectively, “Contributors”) must comply with the terms of this Charter.
+
+1. **Mission and Scope of the Project**
+
+   a. The mission of the Project is to develop and preserve open source infrastructure as code.
+
+   b. ...

15:I'm proposing a _framework_ for technical documentation and user interface writing. It is not a framework of code, but rather of _thought_ and _style_ to help us make decisions about documentation and user interface writing. Its goal is to lead to more consistent written word, and (hopefully) let that lead to better user interface writing as well.
65:* getting all authors to set aside their pet styles and use the standard style for OpenTofu.

Creating a style guide/framework for documentation and user interface

### Summary

Having a consistent written style across multiple authors can help a large project maintain a uniform voice. A written-down style guide, along with linters (and other automation) and human reviews can help take the guess-work out of what that voice should be, and how to maintain it.

### Problem Statement

The written word is how we communicate with our customers. In places where communication is more formal (e.g., the official website, the `tofu` tool itself), having a consistent voice across multiple writers helps lend subconscious legitimacy to the project. There are many people for whom a misspelled word, or poor grammar, can reduce their trust in the thing being presented.

There is also the issue of _clarity_. Technical documentation is a different medium with a different form from things like creative writing, or even writing for user interface (the `tofu` CLI tool is a user interface). ...

opentofu-github-pr-1650
{"base_sha": "da1471b8ce5042ce93ffb762800e94f94fb3a6d2", "changed_files": 1, "draft": false, "head_sha": "0e5a064c6eef77f22205ae307352ecb141515e63", "merge_commit_sha": "2ef3047ec6bb266e8d91c55519967212c1a0975d", "merged": true, "merged_at": "2024-05-16T06:28:54Z", "state": "closed"}
opentofu-github-pr-2830
{"base_sha": "6f0d3d3a07a49309b30960d57225c9f7c701e9a9", "changed_files": 43, "draft": false, "head_sha": "da4ac00ca09d1d9e06e47efd77523a235d49f10c", "merge_commit_sha": "59d24390b712b87954ee175c38912e56d8f5d974", "merged": true, "merged_at": "2025-05-23T12:18:56Z", "state": "closed"}

1-@@ -1,490 +1,50 @@
2- # Contributing to OpenTofu
3- 
4--Welcome and thank you for wanting to contribute! 
5:+Welcome and thank you for wanting to contribute!
6- 
7- ## Get started
8- 
9- - Have a question? Post it in [GitHub Discussions ➡️](https://github.com/orgs/opentofu/discussions) or on the [OpenTofu Slack ➡️](https://opentofu.org/slack/)!
--
12- - Want to help define a complex feature or bug fix? [Write an RFC here ➡️](./rfc/README.md)
13--- Want to provide a proof-of-concept for an issue? Please [submit a draft PR here ➡️](https://github.com/opentofu/opentofu/compare)
14--- Want to add a feature, fix a linter error, refactor something, or add CI tooling?
15--  1. Check if there is an [open issue with the `accepted` label](https://github.com/opentofu/opentofu/issues?q=is%3Aopen+is%3Aissue+label%3Aaccepted),
16:+- Want to add a feature, fix bug, refactor something, or add CI tooling?
17:+  1. ...

...output truncated...

Full output saved to: /home/byk/.local/share/opencode/tool-output/tool_082f550a4001NHCkfbhsGvtvPL

          "change_status": "effective",
          "direction": "added",
          "evidence_refs": [
            {
              "quote": "The Technical Steering Committee (the “TSC”) will be responsible for all technical oversight of the open source Project.",
              "source_id": "patch:0"
            }
          ],
          "right_kind": "set_strategy",
          "scope": "technical oversight and direction of the OpenTofu project",
          "target": "OpenTofu project"
        },
        {
          "actor": "The Technical Steering Committee (the “TSC”)",
          "change_status": "effective",
          "direction": "added",
          "evidence_refs": [
            {
              "quote": "A Contributor may become a Committer by approval of the TSC.",
              "source_id": "patch:0"
            }
          ],
          "right_kind": "approve",
   ...

{"record_id":"opentofu-github-issue-1353","luna_a":{"affected_scope":"OpenTofu technical documentation and user interface writing","ambiguity":null,"announced_on":"2024-03-08","body_patch_relation":"body_only","confidence":0.97,"effective_on":null,"event_kind":"control_rights","power_changes":[{"actor":"OpenTofu","change_status":"proposed","direction":"added","evidence_refs":[{"quote":"I'm proposing a _framework_ for technical documentation and user interface writing.","source_id":"body"},{"quote":"getting all authors to set aside their pet styles and use the standard style for OpenTofu.","source_id":"body"}],"right_kind":"set_policy","scope":"OpenTofu project","target":"technical documentation and user interface writing"}],"record_class":"proposal_only","title":"Creating a style guide/framework for documentation and user interface"},"luna_b":{"affected_scope":"OpenTofu documentation and user interface ...