Skip to main content

Action matrix

The V3 action policy maps protocol operations to economic classes and authorization requirements. This matrix is intended for transaction preflight, product copy and integration planning. Final mainnet amounts are intentionally not invented here. Use the active network economics authority for numeric amounts.

How to use the matrix

A client can convert policy into a preflight object:
The UI then resolves current identity and network economics instead of encoding policy in button conditionals.

Public economic action versus governance action

The policy intentionally distinguishes public economic operations from internal governance configuration. Do not turn ownership.transfer into a paid public feature simply because it changes contract state.

Amount resolution

Economic class is not the amount. A mainnet-ready client can keep stable action semantics while loading actual amounts from a versioned environment manifest. If the current amount cannot be resolved confidently, disable authorization and report configuration error. Guessing an economic value is not a safe fallback.

Relationship checks remain critical

The role column is only one dimension. Official evidence, contributor management, bounty approval and feed registration all include contextual authority that cannot be inferred from role alone. A complete transaction preflight asks both “what role does this identity hold?” and “what relationship does it have to this specific object or organization?”