Creator Value Map

Make every contribution traceable.
Make every payment explainable.

Explore how creative work connects to evidence, deployment, measurable value, and compensation under agreed terms.

11 linked records

3 decision checkpoints

1 traceable story

Interactive guide Conceptual model

GOVERNING RULE
APPLIES UPSTREAM

Agree on rights, eligibility, and payment terms before use. Agreement appears at step 09 when calculating shares. Its terms govern the work from the start.

Traceability path · Follow 01 → 11 A linked record model, not a universal timeline Select any record ↗

Establish origin

Whose work is this, and can this version be trusted?

01 Creator Who contributed? Identity + role 02 Contribution What did they contribute? Work item + scope 03 Version Which exact revision? Version ID + artifact 04 Evidence What supports the claim? Sources + review result

Connect use to value

What went live, and what outcome can we support?

05 Release What was approved? Release ID + approval 06 Deployment Where was it used? Location + date + release 07 Value ID How is value connected? Attribution key + method

Reconcile the money

Which terms turn attributable revenue into a payment?

08 Revenue Which revenue is linked? Amount + currency + status 09 Agreement Which terms apply? Terms + effective dates 10 Allocation How is it divided? Eligible amount + shares 11 Payment reference Can payment be verified? Transaction + settlement

Credit does not set the share.

Evidence supports attribution. The applicable agreement determines payment eligibility and terms.

A Value ID is a link, not proof.

Support the link with a measured outcome and an attribution rule. Deployment alone does not prove value.

A reference is not settlement.

Match the recipient, amount, currency, and payment status. Keep any unpaid balance visible.

Find the first unsupported link.

Assign an owner → attach the missing record → recheck the relevant checkpoint.
Trace forward to explain the outcome. Trace backward to justify the payment.

Explore the linked records

Open a record for its next action, suggested owner, minimum evidence, and what to resolve when a link is missing.

01 / Creator

Next action

Identify every person or organization whose contribution is being claimed.

Suggested owner: Contributor or team lead

Minimum linked evidence

Stable contributor ID and display name
Role and a verified link to the contribution

If this link is missing

Resolve an unverified identity before assigning credit or a payment entitlement.

Key distinction: Credit for work and eligibility for payment are separate questions.

02 / Contribution

Next action

Describe the specific work and connect each contributor to their role in it.

Suggested owner: Contributor and work owner

Minimum linked evidence

Contribution ID and linked creator IDs
Work description, scope, and supporting artifact

If this link is missing

Clarify who did what before attributing the whole outcome to any one contributor.

Key distinction: A contribution may have several creators; one creator may make many contributions.

03 / Version

Next action

Pin the exact artifact that will be reviewed, released, and later credited.

Suggested owner: Work owner or maintainer

Minimum linked evidence

Immutable revision ID or content hash
Retrievable artifact and linked contribution IDs

If this link is missing

Pin the revision before relying on evidence that may describe a different version.

Key distinction: A name such as “latest” can change. Keep the exact revision in the record.

04 / Evidence

Next action

Attach evidence for authorship and acceptance of this specific version.

Suggested owner: Reviewer or evidence owner

Minimum linked evidence

Source records and acceptance criteria
Review result, reviewer, date, and exact version link

If this link is missing

Resolve missing or conflicting proof before approving a release.

Key distinction: An assertion is not its own proof. Keep the source behind each material claim.

05 / Release

Next action

Record the approved version, intended use, and any conditions on its release.

Suggested owner: Release approver

Minimum linked evidence

Release ID linked to version and evidence
Approver, approval date, scope, and conditions

If this link is missing

Obtain the required approval before deploying outside the approved scope.

Key distinction: Approval for use does not establish that the work has actually been deployed.

06 / Deployment

Next action

Verify where the approved release was actually put into use.

Suggested owner: Deployment or operations owner

Minimum linked evidence

Deployment ID, location or environment, and date
Exact release link and verification of actual use

If this link is missing

Verify actual use before claiming that the release produced an outcome.

Key distinction: Deployment demonstrates use or availability; it does not by itself prove value.

07 / Value ID

Next action

Use a stable key to link the deployment, measured outcome, and related revenue records.

Suggested owner: Outcome or attribution owner

Minimum linked evidence

Value ID linked to the deployment and outcome evidence
Metric, observation period, attribution rule, and limitations

If this link is missing

Keep attribution unverified until a measured outcome and a defensible linking rule are attached.

Key distinction: Value ID is treated here as an attribution key. The identifier alone proves neither value nor causation.

08 / Revenue

Next action

Link the revenue record and identify the basis used to calculate distributable value.

Suggested owner: Revenue record owner

Minimum linked evidence

Revenue ID linked to Value ID; amount and currency
Status, period, and applicable adjustments or reversals

If this link is missing

Reconcile the revenue basis before calculating a distributable amount.

Key distinction: Recorded revenue and collected cash are different states. Use the basis required by the agreement.

09 / Agreement

Next action

Select the governing agreement and terms that apply to the parties, work, and period.

Suggested owner: Agreement owner

Minimum linked evidence

Agreement ID, applicable parties, and effective dates
Eligibility, rights, revenue basis, shares, and payment conditions

If this link is missing

Resolve missing or conflicting terms before monetization or allocation, as applicable.

Key distinction: Position 09 is a lookup in the trace. Establish governing terms before use; do not wait until revenue arrives.

10 / Allocation

Next action

Apply the governing terms and reconcile every calculated share to the distributable amount.

Suggested owner: Allocation preparer and reviewer

Minimum linked evidence

Linked revenue and agreement IDs
Calculation, adjustments, recipients, shares, and approval

If this link is missing

Correct a mismatched calculation or ineligible share before authorizing payment.

Key distinction: Retain the calculation and any residual or outstanding balance so the full amount is explainable.

11 / Payment reference

Next action

Match each allocation to the payment record and verify the actual settlement status.

Suggested owner: Payment or reconciliation owner

Minimum linked evidence

Payment reference, recipient, amount, currency, and date
Linked allocation IDs, settlement status, and unpaid balance

If this link is missing

Track a pending, failed, or partial payment until settlement or an explicit outstanding balance is recorded.

Key distinction: A payment reference identifies a transaction. It does not alone prove that the recipient received the money.