Where we stand against our own Charter, in numbers we measured ourselves. Where a number is missing, we say so rather than guess.
Sections 11.1 and the Accountability row of Schedule A.
Every Known Exception shall be listed in Schedule A with its reason, its plan, and its target date. No new Known Exception may be created without a public explanation.
| No. | Status | Exception | Section | Plan | Target |
|---|---|---|---|---|---|
| A.4.1 | Known exception | Our first mobile app includes a third-party analytics and crash-reporting service, with an opt-out in settings | 4.3 | Remove usage analytics; make crash reports opt-in, one at a time | Next major release |
| A.4.2 | Known exception | Apps are distributed mainly through dominant app stores whose rules and fees we do not control | 10.8 | Disclose store fees; offer a direct download where store rules permit | Reviewed each year |
| A.4.3 | Known exception | Some AI work still runs on remote services in large data centers | 5.9 | Move work onto our own hardware; report the share each year | Reviewed each year |
| A.4.4 | Known exception | Our websites, accounts, email, and payments rely on large commercial cloud providers | 4.2, 5.9 | Prefer providers that publish energy data; keep stored data minimal; self-host where practical | Reviewed each year |
| A.4.5 | Known exception | Our computers run on grid electricity with no renewable supply contract | 5.8 | Renewable supply or community solar, then solar for computing | Within 12 months |
| A.4.6 | Known exception | The Charter is not yet written into our legal documents | 10.1, 10.2 | Amend the operating agreement; elect benefit status | Within 12 months |
| A.4.7 | Known exception | Support Periods and sunset plans are not yet published for products already in testing | 4.9, 4.10 | Publish both | Before general release |
We're a small team, and we're not there yet. Our first app still includes an outside analytics tool (you can switch it off), which we're removing. We rely on big app stores and cloud companies, some of our AI work still runs in large data centers, and our computers run on ordinary grid power. Our plan to fix each of these is public, with target dates.
Each year the Company shall measure the electricity its own computing uses and estimate the emissions of its operations, using published methods such as the Software Carbon Intensity specification (ISO/IEC 2024). It shall publish the results with their method and their uncertainty.
The total annual compensation of the Company's highest-paid person shall not exceed five times that of its lowest-paid full-time-equivalent Worker. The Company shall publish its pay ranges for every role and its actual ratio each year.
After meeting its legal obligations and debts, the Company shall use its money in this order: 1. fair pay under Article VI; 2. a Continuity Reserve large enough to honor the Support Periods and Sunset duties of every Product it then supports; 3. at least one percent of gross revenue each year to an Access and Commons Fund, which pays for free and discounted access, community repair and teaching, and gifts to environmental and community organizations, with every recipient published; 4. reinvestment in the purpose of this Charter; and 5. limited returns on capital, as set in Schedule A, together with any distributions Members need to pay taxes on the Company's income.
Each year the Company shall publish a summary of its revenue, its costs by major category, its Continuity Reserve, its giving, and its pay ratio.
Because the Company holds as little User Data as possible, it has little to produce. It shall respond only to legally valid process, as narrowly as the law permits; notify affected Users unless the law forbids it; and publish each year the number and kind of requests it received.
If User Data the Company holds is exposed, the Company shall tell affected Users promptly, within 72 hours of confirming it wherever possible, and publish what happened and what it changed.
| Product | Status | Supported until | Sunset plan | Product Test |
|---|---|---|---|---|
| MIDI Sketch | beta | Known exception· A.4.7 Support Periods and sunset plans are not yet published for products already in testing | Known exception· A.4.7 Support Periods and sunset plans are not yet published for products already in testing | Badge held: 16 of 18 answered yes today |
Concerns received
[COUNT]
Answered in public
[COUNT]
Still open
[COUNT]
Each answer is published in this form
Concern received [date]: [summary]. What we found: [finding]. What we changed: [change].
Any person may send the Company a concern that it is not keeping this Charter. The Company shall acknowledge each concern within 7 days and answer publicly within 30, saying what it found and what it changed, while protecting the privacy of the person who raised it.
Published once a year
Requests for user data received in [year]: [n]. Answered: [n], as narrowly as the law allows. People notified: [n].