Approved, 28 October 2026
Founding Charter v1.1
Our mission, vision, ten founding principles and founding promise. The only approved governance document so far.
Community handbook
The rules we have agreed, and the ones still being discussed.
Only the Founding Charter is approved. Everything else here is a proposal, open for anyone to read and comment on. The documents themselves live on GitHub, which is always the authority.
Approved and published
Approved, 28 October 2026
Decision 0001: adopt the Founding Charter
Adopts the name Comutability and the charter. It is explicitly not the formation of a company or legal entity, a governance mechanism or a software release.
Approved, 28 October 2026
Decision 0002: FileGuide selected for discovery
Chooses FileGuide as the first concept to research. The need is not yet validated, development has not begun and no release is approved.
Published working document
Project 001: FileGuide brief
The problem, proposed read-only first version, research plan and go or no-go gate for FileGuide.
Proposals, not ratified
These are open pull requests. None of them is in force yet. Reviewing them is one of the most useful ways to help right now.
Proposal, not ratified
Governance, contribution, conduct and security guidance
Community pull request #1
Proposed roles, how decisions are recorded, contributor guidance, a code of conduct, security reporting guidance and a founding roadmap. It leaves maintainer selection, consensus, disputes and AI permissions as open questions.
Proposal, not ratified
AI-assisted development and release policy
Community pull request #3
Proposed safeguards for AI-assisted work: humans stay accountable, AI cannot approve or merge its own changes, permissions are tiered by risk, and every release has a named human approver and checklist.
Proposal, not ratified
Existing project intake
Community pull request #4
How five pre-existing Base44 projects could move into the organisation, with risk checks for each. It is not an adopted project list.
Proposal, not ratified
Unified operating handbook and AI agent rules
Community pull request #5
How ChatGPT, Claude, Base44 and GitHub fit together, rules for AI agents, website and hosting rules, and templates for new projects.
Proposal, not ratified
Organisation-wide contributor templates
.github pull request #1
Default contributing, conduct, security, support and accessibility files, a pull request template and agent instructions for every repository.
Proposal, not ratified
Public website blueprint
Community pull request #8
The product brief, design system, content rules, Stripe support plan and launch checklist this website was built from.
How a proposal becomes a rule
As described in the draft operating handbook (pull request #5).
- Discuss it in its pull request or a public issue.
- Address the comments, including any gaps in security or privacy contacts.
- Make an explicit decision, with a date, scope, changes and owners.
- Merge it and publish a numbered record in the decisions folder.
- Apply the matching GitHub settings and checks. Documentation alone is not enforcement.
If a proposal ever conflicts with the Founding Charter, the charter wins.
Licensing
- The Community repository contains an Apache-2.0 licence file.
- Each future software project will choose a recognised open-source licence after reviewing its dependencies. Different projects may choose different licences.
- No licence has been chosen yet for this website's own code. The blueprint suggests Apache-2.0 as a candidate, subject to review.
- ChatGPT, Claude and Base44 are proprietary services run by separate companies. Using them to help build something does not make them open source, and you never need them to contribute.