# Governance and licenses > Editor, contributor, and Task Force roles; rough consensus; CC BY 4.0 spec text and Apache-2.0 code; trademarks; and Grid 1 regulator relationship. - Repository: g2tf-org/g2tf-standards - GitHub: https://github.com/g2tf-org/g2tf-standards - Human docs: https://grok-wiki.com/public/docs/g2tf-org-g2tf-standards-436ba3f3e0ff - Complete Markdown: https://grok-wiki.com/public/docs/g2tf-org-g2tf-standards-436ba3f3e0ff/llms-full.txt ## Source Files - `GOVERNANCE.md` - `NOTICE.md` - `LICENSE` - `LICENSE-CODE` - `CONTRIBUTING.md` - `README.md` --- --- title: "Governance and licenses" description: "Editor, contributor, and Task Force roles; rough consensus; CC BY 4.0 spec text and Apache-2.0 code; trademarks; and Grid 1 regulator relationship." --- The Grid 2.0 Task Force (G2TF) maintains this repository as the canonical Grid 2 specification home and publishes progress at [g2tf.org](https://www.g2tf.org). Roles, rough consensus, the decision log, trademarks, and the Grid 1 regulator relationship live in `GOVERNANCE.md`. Copyright, inbound contribution licenses, and the dual outbound split live in `NOTICE.md`, `LICENSE` (CC BY 4.0 specification text), and `LICENSE-CODE` (Apache-2.0 code). The Task Force formed at the publication of RFC #1 (August 2026). Every living normative file lists **Editors** in its status header. As of the current tree those headers are `Editors: TBD`. The Task Force appoints editors; until named, two-editor review and merge authority still apply to the editor role as defined below. ## Canonical files :::files . ├── GOVERNANCE.md # roles, rough consensus, decision log, trademarks, regulators ├── NOTICE.md # © 2026 G2TF; inbound SPECS vs CODE licenses; trademark notice ├── LICENSE # Creative Commons Attribution 4.0 International (spec text) ├── LICENSE-CODE # Apache License 2.0 (code) ├── CONTRIBUTING.md # comment cycle, two-editor review, RFC acknowledgments ├── rfcs/ # immutable RFCs (RFC #1, August 2026) ├── architecture/ # living architecture (Draft / Informative) ├── specs/ # G2P, GCAP, DESP (Draft — seeking input) └── members/ # Use, Buffer, Source, Allocator (Draft — seeking input) ::: ## Task Force G2TF is a working group of individuals with electric-grid and market-development experience across organizations. It is modeled on the IETF: open individual participation, merit of contribution, time-limited milestones, and “get rough consensus, publish, then run.” Organizational affiliation confers no extra standing. The Task Force: - Maintains this repository - Appoints editors - Resolves cross-document conflicts - Sets milestone dates - Approves publication of new RFCs RFC publication is a Task Force act. Living files (`architecture/`, `specs/`, `members/`) evolve under editor-judged rough consensus; `rfcs/` snapshots are never modified after publication. ## Roles | Role | Authority | How standing is established | |---|---|---| | **Editor** | Maintains named documents; judges rough consensus on threads that affect those documents; merges PRs | Appointed by the Task Force; listed in each normative document header | | **Contributor** | Participates via Discussions, Issues, or PRs | Open to any individual; standing follows the merit of the contribution | | **Task Force** | Cross-document conflicts, editor appointments, milestone dates, new RFC approval | The working group that formed at RFC #1 | Normative pull requests require review by **two spec editors**. Normative changes must use RFC 2119 / RFC 8174 keywords and state compatibility impact. Merged decisions are written into the `GOVERNANCE.md` decision log with a one-paragraph rationale and a link to the originating thread. Comment-cycle mechanics, Discussion vs Issue vs PR routing, and the `errata` label for RFC #1 belong on the contributing and review pages. This page defines who may judge consensus and who may publish. ## Rough consensus The responsible editor judges consensus. The test is not unanimous agreement. It is whether every objection has been considered and either addressed or explicitly overruled with recorded rationale. Sustained objections stay in the decision log even when overruled. There is no vote. ```text Raise (Discussion or Issue) │ ▼ Converge (editor summary → rough consensus on direction) │ ▼ Review (PR; two editors on normative text) │ ▼ Record (GOVERNANCE.md decision log + thread link) │ ▼ Run (Phase 0+ implementation reports inform the next revision) ``` ## Decision log The log is the durable record of Task Force and editor decisions. Current entry: | Date | Decision | Rationale | Thread | |---|---|---|---| | 2026-08 | Publish RFC #1; decompose into living specs (this repository structure) | Separate the immutable narrative from evolving normative text; give the community focused surfaces for comment | — | Protocol versions use a **YY.N** scheme (26.0 is the first 2026 line). G2P, GCAP, and DESP version independently. Status headers on living files are `Draft — seeking input`, `Proposed`, or `Stable (vXX.Y)`. Compatibility statements are required when Stable text changes. ## Licenses © 2026 The Grid 2.0 Task Force. | Material | Outbound license | File | Inbound grant | |---|---|---|---| | Specification text and other non-code work | Creative Commons Attribution 4.0 International (CC BY 4.0) | `LICENSE` | Submitting an Issue, Discussion post, or pull request licenses that contribution under CC BY 4.0 and allows incorporation into G2TF publications with attribution | | Code | Apache License 2.0 | `LICENSE-CODE` | Any code that emerges in this work is Apache-2.0 | This tree is specification-only today: there is no implementation source under `LICENSE-CODE`. The Apache-2.0 file is the binding license for code when it appears. ### CC BY 4.0 on specification text `LICENSE` is the Creative Commons Attribution 4.0 International Public License. Recipients may reproduce and share the licensed material, and produce adapted material, worldwide and royalty-free, subject to attribution. Patent and trademark rights are **not** licensed under CC BY 4.0. The public license does not grant endorsement by the Licensor. When sharing licensed or adapted spec text, retain creator identification, the copyright notice, a reference to the public license, the warranty disclaimer, and a URI to the material when practicable; mark modifications. ### Apache-2.0 on code `LICENSE-CODE` is Apache License 2.0 (January 2004). It grants a copyright license to reproduce, prepare derivative works, display, perform, sublicense, and distribute, plus a patent license limited to claims necessarily infringed by a contributor’s contribution (alone or with the Work). Instituting patent litigation alleging the Work or a contribution infringes terminates that patent license. Redistribution must include a copy of the license, prominent change notices on modified files, retained notices, and a readable copy of attribution notices from `NOTICE.md` where that file is distributed. Apache-2.0 does **not** grant permission to use the licensor’s trade names, trademarks, service marks, or product names except for reasonable and customary description of origin and reproduction of NOTICE content. Both licenses deliver the work **AS IS**, without warranties of title, non-infringement, merchantability, or fitness. ### Attribution of contributors Substantive contributors are acknowledged in subsequent RFC publications, following RFC #1’s acknowledgments section. That is the `CONTRIBUTING.md` acknowledgment process referenced by `NOTICE.md`. ## Trademarks The following marks are trademarks of the Grid 2.0 Task Force: | Mark | Owner | |---|---| | "Grid 2.0"™ | Grid 2.0 Task Force | | "G2TF"™ | Grid 2.0 Task Force | | "G2P"™ | Grid 2.0 Task Force | | "GCAP"™ | Grid 2.0 Task Force | | "DESP"™ | Grid 2.0 Task Force | **No trademark rights are granted** by CC BY 4.0 or Apache-2.0. A trademark usage policy for describing conformant implementations is forthcoming from the Task Force and will be published in this repository. Until that policy exists, do not treat either copyright license as permission to brand a product as Grid 2.0, G2TF, G2P, GCAP, or DESP. ## Relationship to Grid 1 regulators and formal standards Grid 2 is **voluntary** and sits inside existing Grid 1 rules. G2TF coordinates with, and does **not** supersede, NERC, FERC, utility, and TSO/ISO requirements. Participating assets continue to meet those requirements in their Grid 1 context. Authority for constraint inputs is anchored in the utility transmission owner, not in the protocol. Alignment work with IEEE 2030.5 and related standards is tracked in GitHub Discussions. Design principles treat broader (for example FERC-level) recognition as something to pursue after a local path is proven (Phase 0 shadow mode → Phase 1 local integration → Phase 2 federation), not as a prerequisite for the overlay. A companion document covering detailed regulatory and engineering concerns is in development with focused stakeholder outreach, including: - Hyperscalers, utilities, and state regulators under committed contracts - Research labs including EPRI, Purdue, Duke, Emerald.ai, GridCare, Nvidia - ERCOT, SPP, PJM, MISO - NERC, FERC, DOE - The international community via the World Economic Forum Non-interference, “coordination without prices,” and the v26.0 energy-in-the-interval scope are protocol facts, not governance process. See Overlay and Grid 1 for those rules. ## Next Draft → Proposed → Stable → RFC, YY.N versions, compatibility statements, and the decision log. Open individual participation, comment-cycle steps, RFC 2119 and one-sentence-per-line conventions. Discussions vs Issues vs PRs, RFC #1 errata, two-editor review, and recording decisions. Overlay membership, NERC/FERC/TSO non-interference, and coordination without prices.