Organisation: Comutability
Version: 0.1
Status: Proposal pending human approval
Drafted: 15 November 2026
Applies to: Comutability's Open Collective finances, once a fiscal host and authorised reviewers are confirmed
Not yet adopted. This policy is a proposal, subordinate to the approved Founding Charter v1.1 and to applicable law, Open Collective terms and fiscal-host requirements.
Built together. Open to everyone.
Purpose
Each Open Collective expense should have a clear, accurate, plain-English title so supporters can understand the purpose of community spending without opening private invoices or receipts.
Recommended format
Project | Expense type | Description | Period
Examples:
Secure Net | Invoice | Rust development | November 2026CommonVeil | Reimbursement | Hosting | November 2026Comutability | Invoice | Website accessibility reviewSecure Net | Grant | Independent security researchComutability | Reimbursement | Domain renewal
Use Comutability where an expense is shared or organisational rather than linked to one application.
Requirements
- Identify the project or activity and the expense type.
- Describe what was supplied, purchased or funded without exaggeration.
- Add a month or period when relevant, especially for recurring invoices.
- Keep descriptions short, accessible and consistent across expenses.
- Do not publish full names that are unnecessary, private addresses, passwords, access tokens, banking details, undisclosed vulnerabilities or other sensitive information.
Titles such as “Miscellaneous”, “Payment” and “Stuff” are too vague. Misleading or deliberately obscured descriptions are not acceptable.
Review
An authorised human reviewer may request a more precise or safer title before approving an expense. AI may suggest wording but cannot authorise the expense. Titles remain subject to the relevant Invoice, Reimbursement or Grant Expenses Policy and fiscal-host terms.
This policy becomes effective only after recorded human approval.
