One creative asset. A clear chain of decisions.

A prospective participant, photographer, buyer, or partner begins with a public application. Submitting interest does not create an account, approve a role, or grant access. An internal review and invitation would come first.

Onboarding is intended to establish the person or organization, the role they will hold, the scope of any representation, and the agreements that apply. Identity checks and signed documents support the record; the platform record does not replace them.

A session connects the participating people, purpose, date, and agreed working terms. A source asset and its approved derivatives can then be registered with lineage, file hashes, edit disclosures, and access controls.

Private source files are intended to remain private. Public verification, if later approved, should expose only a safe subset of facts about an asset or physical item—not releases, addresses, source files, or private economics.

• Application and internal review
• Invitation, onboarding, and scoped agreements
• Session record and private asset registration
• Source-to-derivative lineage and edit disclosure

The photographer key records authorship and the photographer's agreed permissions. The subject key records the depicted person's approval for the proposed scope. The platform can preserve both statements, their versions, and the evidence supporting them.

Neither key silently substitutes for the other. A subject's approval does not transfer a photographer's copyright, and a photographer's copyright does not by itself authorize every use of a person's likeness.

Before an asset becomes eligible for a license or product, the intended workflow checks ownership evidence, releases or other rights instruments, exclusivity conflicts, sensitive-use restrictions, disputes, and the exact proposed use.

A license should state the permitted media, territory, term, edits, audience, delivery, renewal, and AI restrictions. Project economics are versioned for that use. There is no universal split: the participating parties agree to the allocation for each project.

An approved buyer license or physical product can carry a traceable delivery or production record. A public verification page may later confirm limited facts such as item status, edition and serial information, and the scope of what was checked.

Revenue records are intended to show gross receipts, documented deductions, Net Creator Revenue, participant allocations, refunds, and payout status without rewriting history. Protection cases can place a hold on new uses while evidence is reviewed. Participants should also be able to export permitted career records and leave representation without losing assets they own.

Available today: this public website, sourced education, founding applications, partner inquiries, and one unmistakably fictional verification sample. These are real public services within a deliberately narrow launch scope.

Secure creator accounts, identity verification, asset onboarding, production rights signing, public licensing, payments, payouts, physical production, opt-in AI likeness permissions, marketplace functions, and tokenization remain disabled behind separate technical, legal, consent, security, and operating gates.