Make the world.
Art, 3D, writing, video, animation, software, design, worldbuilding and production.
The work has to matter.
A contribution is not rewarded merely because somebody worked hard on it. Review can consider quality, usefulness, difficulty, impact, timing, originality, technical complexity, audience reached and how strongly the result moves MUTERRA forward.
The result matters more than activity around the result.
Four paths
Different people create value differently.
Choose the path closest to what you can deliver. A task should define what is needed, who reviews it and what reward applies.
Open Create path →
Create useful reach.
Distribution, partnerships, influencers, campaigns and introductions that produce a real result.
Support a defined system.
Selected ownership or ecosystem activities where a published programme defines useful participation.
Improve the product.
Testing, gameplay feedback, QA, records, competitions and experiments that make the game better.
The record
The first reward is that the project remembers.
Accepted work can enter a contributor record even when no financial reward is attached.
Provenance before promises.
A record can preserve the contribution, date, source, review status, public credit where appropriate and later connections to what the work influenced.
It can recordWhat was submitted, when it was accepted, public credit and later project connections.
It does not createAutomatic canon status, IP ownership, an NFT, payment or Crew status.
It can supportFuture task selection, larger work, scarce opportunities and a visible history of usefulness.
Source of truthThe published terms attached to the specific task or programme.
Review lifecycle
Accepted is a real status.
The future cabinet should expose this history directly. Until then, task owners must keep the review state explicit.
SubmittedReceived, not yet reviewed.
In reviewBeing evaluated.
AcceptedUseful work enters the project record.
RevisionPotentially useful, changes required.
Not usedReviewed but not accepted.
RewardedA defined reward is assigned or processed.
Reward types
Not every job pays in the same cargo.
Depending on the published task, accepted work can receive MUTA, digital assets, credit, access, priority, role-specific rewards, Crew consideration or another defined incentive.
A grant can arrive on a schedule.
If a programme awards MUTA, the grant can include an unlocked portion, cliff, gradual release or another published vesting schedule. The schedule attached to that grant is the one that matters.
Understand MUTA →Priority cannot fix bad work.
Ticket Weight or Founder priority applies only where a programme explicitly says so. A more expensive Ticket does not make the work better and does not multiply every contribution payment.
Ticket benefits →Work can become a formal place.
Repeated, scarce or unusually important contribution can lead to Crew consideration. Contribution does not automatically create a Pass; Crew is selected and earned.
How to earn Crew →Start
Create something that keeps giving back.
Choose a path. Take a task. Deliver something useful. If MUTERRA accepts it, the work can enter your contribution history. If the task defines a reward, that reward is handled under its rules.