> ## Documentation Index
> Fetch the complete documentation index at: https://docs.presschain.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Attribution

> Preserve authorship, co-authorship, source relationships and outlet context in application data.

# Attribution

Attribution is a structured part of provenance. PressChain gives applications several different places to represent it because “who is responsible for this?” rarely has only one answer.

## Primary author

The Capsule core interface includes an `author` address. This identifies the primary actor associated with the Capsule.

## Outlet identity

The Capsule also includes `outletId`, and canonical metadata contains `outlet_identity_ref`. That lets the record retain organizational context separately from the author wallet.

## Contributors

`CapsuleContributorsRegistryV3` adds wallet-specific relationships with role, contribution type, share basis points and `attributionURI`.

This is useful for co-authors, additional authors and source relationships that should be explicit.

## Human-readable presentation

A good article header might render:

```text theme={null}
By Lena Ortiz and Marcus Hale
Published by Metro Ledger
Verified publication record: 0x7f...91c
```

An expanded provenance panel can then show the underlying addresses, contributor roles, attribution records and transaction links.

This gives ordinary readers simple copy without throwing away technical traceability.

## Attribution URI

Use the contributor `attributionURI` for durable structured detail, not for ephemeral UI text only. It can point to a contributor statement, role description or signed metadata document.

Do not put confidential source identities into public attribution merely because the protocol supports a SOURCE contributor role. Editorial source protection remains a critical constraint.

## Shared economic attribution

Contributor share basis points can express an allocation, but the downstream economic meaning must follow the applicable settlement policy. A 2,500 bps contributor record is structurally 25 percent of the active share allocation. It should not be described as a guaranteed token payout unless the payout system explicitly defines that connection.

## Changes over time

A contributor can become inactive. Preserve the historical record and show active status separately.

For an audit interface:

```text theme={null}
Contributor added at block 12033
Role: CO_AUTHOR
Share: 4000 bps
Deactivated at block 12880
Current state: inactive
```

This is far more useful than deleting the contributor from the page and making it appear they were never associated with the work.