What sponsorship is
You fund an item. It moves to the front of the queue. You co-write the acceptance criteria, so “done” means done on your meetings. Your name goes on the release note. It ships upstream, where everyone gets it — including your competitors.What it is not
Not exclusivity. Not a private build. Not a feature-request board — demand without funding does not order anything, and funding does not buy work of your own design; it buys priority on this list. No dates are promised before an item is ordered and its acceptance criteria are written. Sizes are shown as S · M · L classes, never as durations.How sponsorship works
1
Pick an item
Anything marked sponsorable below. Open its Sponsor this door — fifteen minutes with the founder.
2
Agree the fee basis in writing
Per item or per stage, agreed before work begins. Prices are not published on this page.
3
Co-write the acceptance criteria
“Done” is written against your meetings, not ours. Only once an item is ordered and its criteria are written does it carry a date.
4
It ships upstream
Under Apache-2.0, to everyone, with your name on the release note.
Sponsorship buys the order of the queue — never exclusivity, never a private build, and never a date the work has not earned.
1 · Capture anywhere, owned by you
Measured by: platforms and routes covered.2 · Dependable capture
Measured by: served-transcript share and named-word share.Speaker separation separates speakers. Names come from a roster you supply. Nobody enrols a voice.
3 · Your data, your rules
Measured by: controls shipped with an API and an audit line.4 · Agents that act on meetings, safely
Measured by: verified delegated authority and tracing.5 · A project the community runs
Measured by: hours to first human validation, and sponsored items shipped. How change earns its way in is written down and enforced, not conventional: the delivery constitution governs the flow from intake to release, and the architecture book governs the artifact. Contributors keep their rights under contributor rights. Sponsored items are delivered through that same loop — no private branch, no separate process.Two doors on every item page
Sponsor this
Fifteen minutes. Bring the item and the constraint you are under.
Watch this
One email when it ships. Watch counts are how we see demand.
The rest of the roadmap
Approach
How we sequence the work — principles first, execution core before features.
Stages
The build in dependency order, each stage with the proof that closes it.
Status
Where we are now, honestly — built, mid-rebuild, next.