You don’t need permission
You do not need permission to use, adapt, or build on the work stewarded by Common Trust for Music.
There is no application process.
There is no central approval.
There is no requirement to “join” anything.
If something here is useful to your local music ecosystem, you are free to use it.
What you can adopt as-is
Some Trust-stewarded assets are designed to be picked up and used with minimal change.
These may include:
- discovery tools for local artists and music events
- shared data schemas
- templates and playbooks
- design systems
- governance tools
If something works for your context, you can adopt it directly.
What you can adapt locally
Local music ecosystems differ.
Accordingly:
- tools may be customised
- data may be structured differently
- governance may be adjusted
- priorities may diverge
Adaptation is expected, not discouraged.
The Trust’s role is to provide a starting point, not a prescription.
What you can fork
Forking is a legitimate and supported option.
You may fork:
- codebases
- data structures
- design systems
- governance patterns
Forking does not require justification or approval.
It exists so that:
- local autonomy is preserved
- experimentation is possible
- disagreement does not become deadlock
How Bucks fits in (Prototype 01)
The Bucks Music Ecosystem is the Trust’s first live prototype.
It serves as:
- a testbed for tools and methods
- a source of learning
- a place where mistakes can be made and corrected
Bucks does not have special authority.
It is simply where the work started.
Examples of possible local use
Different places may use the Trust’s work in different ways.
For example:
- a county may adopt a discovery tool but not the data model
- a city may reuse governance templates without using any software
- a venue network may fork the codebase to suit its own needs
- a regional body may adapt the funding model while retaining local control
There is no “correct” configuration.
What the Trust asks in return (very little)
The Trust does not charge for permission.
It asks only that:
- reuse is acknowledged where appropriate
- improvements are shared back when possible
- divergence is documented so others can learn
There is no obligation to contribute financially or structurally.
How ecosystems stay autonomous
Local autonomy is a core principle.
Accordingly:
- participation is voluntary
- exit is protected
- no ecosystem is required to align its governance
- no central body can override local decisions
The Trust exists to reduce duplication and risk — not to centralise culture.
In summary
This infrastructure is here to be:
- used if helpful
- ignored if not
- adapted where needed
- forked when necessary
Common Trust for Music is a resource, not a ruler.