GitLaw Standards Committee Charter

1. Purpose

The GitLaw Standards Committee exists to produce open, plain-language legal templates and standards that any business can use. Committee members — primarily in-house counsel and general counsel — contribute their expertise to build legal infrastructure that is structured, versioned, and publicly available.

The committee's work addresses a specific gap: millions of small businesses sign contracts they don't fully understand, or skip them entirely, because legal help is inaccessible. The templates and standards produced here are designed to close that gap — not one client at a time, but as infrastructure available to everyone.

2. Scope

The committee's scope is:

  • Reviewing and verifying legal document templates for accuracy, completeness, and plain-language clarity
  • Proposing new templates and standards where gaps exist in common business agreements
  • Defining clause standards — encoding legal intent, fallback logic, and dispute resolution in structured formats
  • Maintaining published templates — flagging when legal or regulatory changes require updates

The committee does not:

  • Provide legal advice to GitLaw users, GitLaw Inc., or any third party
  • Create an attorney-client relationship between members and any person or entity
  • Represent clients or practise law through GitLaw

GitLaw is a technology platform, not a law firm. Committee members contribute to open, public legal infrastructure — the same way contributors to the W3C, IETF, or Linux Foundation contribute to open technical standards.

3. Membership

Eligibility

Committee membership is open to qualified legal professionals, including:

  • In-house counsel and general counsel
  • Practising attorneys, solicitors or barristers
  • Legal academics with relevant expertise
  • Retired legal professionals

All members must hold (or have held) a recognised legal qualification in at least one jurisdiction.

Application and Acceptance

Prospective members apply through the GitLaw Standards Committee application form. Applications are reviewed by the GitLaw team. Acceptance is based on:

  • Relevant legal qualification and experience
  • Practice area alignment with active or planned working groups
  • Jurisdictional coverage needs
  • Capacity to meet the minimum time commitment

GitLaw reserves the right to accept, defer, or decline applications at its discretion.

Time Commitment

The minimum commitment is 1 hour per year. In practice, active participation in template reviews and working group discussions will typically require more — but the bar to remain a member in good standing is deliberately low. The committee values quality of contribution over quantity.

Voluntary Participation

Membership is voluntary and unpaid. Committee members contribute their expertise to open legal infrastructure, comparable to participation in standards bodies and open-source governance organisations. This is professional volunteer leadership, not billable client work.

Resignation

Members may resign at any time by notifying GitLaw in writing. There is no penalty for resignation.

4. Working Groups

The committee operates through working groups organised by practice area and, where appropriate, jurisdiction. Each working group focuses on templates and standards within its domain. Members may participate in more than one working group.

Working Group Formation

A new working group requires a minimum of two members with relevant expertise. GitLaw may propose new groups based on user demand. Members may also propose new groups.

5. How Templates Are Produced

GitLaw Template Creation

Assembly

Templates are assembled primarily from verified clause sources — existing verified contracts, public filings (e.g., SEC EDGAR), and established open standards — rather than generated from scratch by AI. Where verified sources do not exist for a given clause, AI-generated drafts are used and clearly flagged for closer review. This approach reduces hallucination risk and ensures every clause in a published template has traceable provenance.

Benchmarking

Before dual review, templates are compared against publicly available legal standards and, where accessible, legal research tools to validate completeness and accuracy.

Committee Template Selection

Any user of GitLaw is able to upload a new template. Committee members are also able to suggest any template (their own, or someone else's) for verification by the Committee. Verified Templates are then automatically given priority for discovery by users.

Committee Review Process

Every template undergoes a dual review before publication:

  1. First reviewer — One or more working group member reviews the draft, makes changes, and marks it ready for approval.
  2. Second reviewer — A different working group member reviews the updated draft and either approves or requests further changes.

Both reviewers must be members of the relevant working group, with expertise in the template's practice area and jurisdiction.

Publication

Once a template passes dual review, it is given a "Verified" tag. This means the template:

  • Is available for selection by GitLaw's AI agent
  • Appears higher in GitLaw's library and search

Ongoing Maintenance

Published templates are living documents. Updates are sometimes required due to:

  • Changes in applicable law or regulation
  • User-reported issues
  • Significant time elapsed since last review

There are two triggers for Maintenance:

  1. Committee members flag templates that need re-review
  2. GitLaw's AI Agent identifies need to re-review (e.g. due to detected change in laws or new standards in reviewed documents on the platform)

Re-review follows the same dual review process.

6. Attribution

Committee Attribution

All published template reviews are attributed to the Committee as a whole, not to individual members. A published template carries the label:

Reviewed by the GitLaw Standards Committee

This is a deliberate design decision. Committee attribution allows lawyers to contribute without putting their individual professional reputation on the line for any single document, while still providing meaningful provenance to end users.

Individual Contribution Records

Every comment, edit, and approval by a committee member is logged in GitLaw's version control system. Members' contributions are visible on their committee profile. Contributions compound over time — the more you contribute, the more visible your record becomes. If you wish to anonymously contribute you are able to create a profile under any username you wish and GitLaw is able to verify your username.

Use of Committee Credentials

Members may reference their committee membership in professional contexts (e.g., LinkedIn profiles, CVs). E.g.

  • "Member, GitLaw Standards Committee"
  • "Member, [Practice Area] Working Group — GitLaw Standards Committee"

7. Intellectual Property

Templates, standards, and clause libraries produced by the committee are published as open resources available to any GitLaw user. By contributing to the committee, members agree that:

  • Their contributions (edits, comments, proposed clauses) become part of the committee's collective output
  • Published templates are made available through the GitLaw platform under GitLaw's standard terms
  • Members retain no individual intellectual property claim over collective committee output
  • Members retain full ownership of any pre-existing intellectual property they bring to the committee and are not required to contribute proprietary materials

All committee-produced templates are licensed under the Creative Commons Attribution-ShareAlike 4.0 International (CC BY-SA 4.0) licence. This means anyone is free to:

  • Share — copy and redistribute templates in any medium or format, for any purpose, including commercially
  • Adapt — remix, transform, and build upon templates for any purpose, including commercially

Subject to the following terms:

  • Attribution — Users must give appropriate credit and indicate if changes were made
  • ShareAlike — Derivative works must be distributed under the same licence
  • No additional restrictions — Users may not apply legal terms or technological measures that restrict others from exercising the rights the licence grants

8. Liability and Legal Protections

No Individual Liability

Committee members bear no individual professional liability for templates published by the committee. Published templates are attributed to the working group collectively, not to any individual reviewer.

No Attorney-Client Relationship

Nothing in this charter, and no activity undertaken as a committee member, creates an attorney-client relationship between any member and any GitLaw user or third party.

No Practice of Law

Committee participation does not constitute the practice of law. Members contribute to open legal infrastructure and public standards. GitLaw is a technology platform that provides legal document templates, not a law firm and not a legal services provider.

Conflicts of Interest

Members should disclose any material conflict of interest relevant to a specific template or standard under review (e.g., a member's employer is a direct competitor in the space the template covers). Disclosure is made to the working group and to GitLaw. Where a conflict exists, the member should recuse themselves from that specific review.

9. Communication and Ways of Working

Async-First

The committee operates async-first. Working group discussions, reviews, and approvals happen through GitLaw's platform (fork, edit, review, merge) and designated communication channels. Members participate on their own schedule.

Live Sessions

Working groups may hold occasional live sessions for complex discussions or template kickoffs. These are optional and may be recorded for members who cannot attend.

Transparency

All committee activity — discussions, edits, reviews, approvals — is logged and visible to other committee members. The committee operates in the open, consistent with its mission of building public legal infrastructure.

10. Conduct

Members are expected to:

  • Engage respectfully and constructively with other members
  • Provide substantive, good-faith feedback during reviews
  • Disclose conflicts of interest as described in Section 8
  • Respect the confidentiality of any pre-publication drafts or internal discussions not yet made public

GitLaw may remove a member who violates these expectations, after notice and an opportunity to respond.

11. Governance and Amendments

Decision-Making

Day-to-day decisions within working groups (template edits, review approvals) are made by the members involved in that review, following the dual review process.

Structural decisions — forming new working groups, changing the review process, amending this charter — are made by GitLaw in consultation with committee members.

Amendments to This Charter

GitLaw may amend this charter. Material changes will be communicated to all members with reasonable notice. Members who disagree with a material change may resign under Section 3.

Feedback

Members are encouraged to propose improvements to the committee's processes, structure, and this charter. Proposals can be submitted through the committee's communication channels.


This charter is a living document. Version 1.0 — 1st February 2026.