Your career should remain portable, legible, and yours to direct.

An agency or platform may represent, administer, verify, or license within an agreed scope. That role should not become ownership of a person's identity, their whole career, or income unrelated to the work the representative actually helped create or administer.

Each asset can have its own author, depicted people, agreements, allowed uses, restrictions, economics, and history. Keeping those layers distinct makes collaboration clearer and exit less destructive.

The intended product is measured against these participant-facing rights. Final contracts and policies still require appropriate legal review, but the software should not quietly defeat the standard through defaults or access rules.

• You remain a person and the principal in decisions about your career.
• You can see who claims ownership or authority over each asset and why.
• Representation is limited to the signed scope; there is no hidden claim on unrelated future work.
• A proposed license identifies the use, media, territory, term, edits, and economics before approval.
• Consent can be specific, versioned, declined, or withdrawn where the governing agreement and law allow.
• AI training, digital replicas, and synthetic likeness uses require a separate, affirmative opt-in.
• You can see active licenses, restrictions, receipts, allocations, and payout status connected to your work.
• You can report misuse or a dispute without the platform automatically deciding the legal outcome.
• You can export permitted records and leave representation without forfeiting assets you own.
• Existing third-party licenses and authentic item records continue according to their actual terms after an exit.

A useful permission record answers concrete questions: which asset, which person, which buyer, which use, what duration, what territory, which edits, which sensitive categories, and whether AI is included. Silence should not be interpreted as consent.

Controlled AI permissions are not active in the founding build. A future workflow would need a separately approved purpose, source custody, revocation and expiration rules, output review, compensation, security, and a way to prove which consent version governed the use.

Leaving a representative should stop future authority outside any surviving contract terms. It should not erase authorship, past approvals, valid licenses, payment history, public item verification, or protection records that need to remain accurate.

A participant export is intended to package the records they are permitted to carry: assets and derivatives they own, agreements and attestations they may receive, license summaries, provenance, earnings, payout history, and status information. Other people's private records remain protected.