Path 04 · The allies
Most of this ecosystem is makers and listeners. Plenty of what decides how it goes, though, happens away from the stage: in export screens, event listings, submission windows and version histories. If you build tools, run an organisation, shape policy or study the data, this page is your door.
For toolmakers
The Maker's Mark records three things: the shares (roughly how much of each part of a work came from human hands), the tools used, and the choices a person made along the way. If your service exports music, those fields belong in your export flow (the screen where a finished song leaves your service), filled in at the moment of making, while the facts are fresh.
Then map them to the AI credit fields in DDEX (the data standard music releases ship in, like a barcode system for song information). Mapped that way, a maker's record travels with the file to every service downstream, instead of living in a screenshot on someone's phone.
Four lines. Each one is a mechanism, not a promise.
State on the upload page which kinds of work your service takes, in the same words the mark uses, so nobody finds out at rejection time.
When a member asks, export everything they made and everything they filled in, in an open format, without a waiting period attached.
Off by default. A switch the maker sets, not a clause the maker missed on page forty.
One page, every charge, linked before checkout. The Terms Table already puts services side by side with sources linked; a fee page makes your row easy to fill.
None of the four needs new technology. Each is a decision about what your pages say, made once.
For organisations and venues
Festivals, stations, councils, industry bodies: two adoptions, both small, both visible to your audience.
When a show or a release appears in your program, or an act appears on a bill, carry its mark next to the name: the same short line the poster carries. It says how the work was made; your audience decides what that means to them.
The Stage page sets out a fair-fee comparison for ticketing: every charge on one line, side by side with the alternatives. Run your next event's fees through it and publish the result on the event page, where a punter can read it before they buy.
For policy people
Positions go in writing, in public, with sources linked. The processes below are running now here today; this ecosystem's first submissions are being drafted taking shape.
In October 2025 the Australian Government ruled out a copyright exception for AI training, and it is consulting on paid licensing models instead. Those consultations are where a record of making, filled in by makers themselves, can do useful public work.
A federal Office of AI was announced in July 2026. As its work program opens to input, the ecosystem will put its material in front of it: the mark's field lists and the chart's counting rules, as they stand at the time.
The federal live music inquiry reported in March 2025 with 20 recommendations. The follow-ups are where the venue-side ideas, fair-fee ticketing among them, get argued in the open.
Each state runs its music strategy on its own clock. As each one opens for comment, the same position goes in, adjusted for the state, with the same sources linked.
Each submission will be published on this site when it is lodged, so anyone can read what was argued and check it against what was cited.
For researchers and data partners
The chart's counting method, the mark's schemas (the field lists that define a mark) and the results they produce will be versioned in public on GitHub. taking shape A researcher will be able to check any number against the exact rules that produced it, as those rules stood on the day.
Collaboration is a pull request (a proposed change, offered publicly) away. Question a method, propose a field, add a test case: the discussion happens where anyone can read it, and the outcome is public.
Data partnerships work the same way. A station or a service that shares play data does it under rules published beforehand, and what comes of it goes back out in the open.
Where your piece fits
An export field, a line on a listing, a submission, a pull request: each is a small piece, and the ecosystem is the machine they add up to. The mark feeds the chart, the chart feeds the awards, and every layer leans on work like yours.