> ## 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.

# Terminology

> A practical vocabulary for PressChain V3 applications and protocol discussions.

# Terminology

PressChain uses a small set of terms very precisely. Keeping that vocabulary consistent prevents application copy, API objects and protocol records from drifting apart.

## Capsule

The canonical publication record around which PressChain organizes journalism state. A Capsule has a `bytes32` identifier and anchors content and metadata commitments. Contributor, evidence and revision records refer back to that Capsule.

A Capsule is not simply an NFT, an article body or a database row. It is a protocol record designed to be independently readable by multiple clients.

## Canonical metadata

Normalized metadata whose bytes can be hashed deterministically. Current Capsule metadata V1 includes the schema version, title, canonical source URI, optional cover media URI and hash, author and outlet identity references, publication timestamp, content type and language.

## Content hash

A cryptographic commitment to content bytes. It allows a consumer to verify that a retrieved artifact is the same artifact that a publisher committed to. The hash does not prove the content is true. It proves integrity relative to the commitment.

## Metadata hash

A commitment to the canonical metadata envelope. Because metadata contains identity and presentation references that matter to provenance, it should be verified independently of the article content itself.

## PressKey

The PressChain browser identity and signing surface. Current implementation injects `window.presschain`, exposes an EIP-style `request` method and provider events, and identifies itself with `isPressKey: true`. It is non-custodial at the application boundary: websites request authorization rather than receiving the user private key.

## Protocol role

A role represented in the V3 protocol role table. Current IDs are Reader `0`, Author `1`, Journalist `2`, Editor `3` and Validator `4`.

## Bond

PRESS committed to satisfy the minimum economic requirement for a role or action. Bonds align persistent privileges with economic accountability. A bond is not the same thing as a transaction fee.

## Fee class

A semantic economic category attached to an action. V3 defines `none`, `bond`, `micro`, `standard`, `elevated` and `funded`. Final mainnet amounts are separate policy data.

## Community evidence

Evidence that can be submitted by an authenticated PressKey identity under the community evidence policy, subject to economic, validation, duplicate and abuse controls.

## Official evidence

Evidence attached through a privileged canonical path by an actor with the required Capsule relationship or authority. The V3 evidence contract recognizes the Capsule author, attached contributors and protocol administration for canonical attachment at the contract layer.

## Dispute evidence

Evidence submitted to challenge or contradict an existing record. In the V3 evidence registry it uses reserved evidence type `255` and is recorded separately from canonical evidence attachment.

## Evidence tally

The support, reject and participation counters plus status and finalization state associated with an evidence item. Voting and finalization are distinct operations.

## Contributor

A wallet attached to a Capsule through the contributor registry with a display name, role, contribution type, basis-point share, attribution URI and active state. Contributor share allocation is capped at a combined active maximum of 10,000 basis points.

## Projection

A read-optimized representation derived from authoritative chain data. Search indexes, API documents and Explorer views are projections. They are allowed to make queries convenient, but they should retain enough chain coordinates to prove where each canonical fact came from.

## Authority manifest

A versioned source defining which network, protocol major, addresses or policies are canonical for a given environment. An authority manifest is stronger documentation than a stale client constant.

## Testnet fact

A value that is true for the current test network, such as Chain ID `77117002`. It is not automatically a mainnet value.

## Planned mainnet policy

A policy intentionally declared ahead of launch but still gated by readiness and approval. The planned mainnet PRESS supply of 10 billion is an example. Testnet balances and genesis are explicitly not reused as a shortcut to mainnet.

## Trust data

A broad data concept that may include identities, sources, claims, evidence, relationships, provenance, risk or visibility. PressChain models can interoperate with structured trust data, but PressChain and the separate TRUST Layer remain distinct systems with separate product and authority boundaries.