​

Role matrix

The active V3 protocol role table contains five protocol roles. Enterprise and Administrator are platform roles and must not be inserted into this numeric sequence.

​

Canonical role table

These bond values are current testnet authority, not automatically final mainnet economics.

​

Common action eligibility

* Community evidence requires an authenticated PressKey identity and is still subject to fee, validation, duplicate and quota policy. † Official evidence and contributor operations also require the appropriate Capsule relationship or authority. Holding the role alone is not sufficient. ‡ Bounty approval also depends on creator, designated reviewer or protocol authority relationship. § Feed registration additionally requires outlet administration or Enterprise project authority.

​

Bond requirements are action-specific too

A role can exist while its bond is inactive or insufficient for a particular action. Publishing, official evidence, challenges, reviews and bounty actions can require active bond state according to policy. A client should resolve both role and bond before showing a transaction as ready.

​

Role weight is not a universal reputation score

Weight can be used by protocol processes that explicitly reference it. It does not mean a Validator is ten times more truthful than a Reader or that every application should calculate a trust score from the number. Use weight only where the active rulebook says it belongs.

​

Contributor roles are separate

Do not confuse protocol roles with the contributor registry’s AUTHOR, CO_AUTHOR and SOURCE enum. One describes protocol eligibility. The other describes a person’s relationship to one Capsule. Keeping those namespaces separate prevents subtle authorization bugs.