WCNCitizen Ledger
№ 08·0508 · Proof of Business2 min read · Section 5 of 6

8.5 Attribution logic

The distinction between leadership, collaboration, adoption and review; analogy with Brinson’s attribution and performance splitting; preventing duplication and stealing credit.

Updated
8.5 · Attribution logic

PoB must not only answer "what happened", but also "who promoted it and how" with the participation of multiple parties.

PoB can prove the existence of results, but if attribution is unclear, settlement will still degenerate into political distribution. The task of the attribution layer is to establish a defensible contribution mapping within the same closed loop - who removes key blockers, who provides input with low substitutability, and who only participates in the periphery - similar to splitting the total return into explainable parts in portfolio management.

What this page doesAttribution principles, role semantics, and comparison with TradFi splitting ideas
core themesFair settlement, prevention of duplicate claims, auditable narrative
Reading highlightsLeadership ≠ all members; last link ≠ full success; Agent must adopt

basic principles

Multi-party participation ≠ Multi-party leadershipA close can have lawyers, underwriters, introducers, and execution nodes; the leader should be bound to the irreplaceable critical path rather than the attendance list.
Dominance cannot be copied infinitelyThe same event archive layer should have mutually exclusive or explicit split ratios for Dominants; otherwise the PoB would be isomorphic to Double Spend Narrative.
The last link does not automatically cover the entire chainBrinson attribution distinguishes between configuration and selection; in the business closed loop, it also distinguishes between who sets the transaction structure, who introduces decisive resources, and who completes the last mile - evidence support is required, not chronological default.
Without attribution, PoB only proves the results; with attribution, PoB can support the harder question of who creates distributable value.

Mental alignment with Brinson/GIPS (not verbatim equivalent)

  • Brinson: Total excess returns are split into asset allocation, security selection, and interaction effects. WCN: Total closed loop is divided into resource introduction, execution promotion, risk removal, final state sign-off and other narrative blocks, and then bound to nodes or agents.
  • GIPS: Performance presentation must be fair, complete, and consistent. WCN: Attribution conclusions should be consistent with the evidence package and timeline, and "all-dominant" narratives supporting the conflict using the same material are prohibited.

The "rewards in proportion to stake" of PoS on the chain are capital weight; PoB attribution is contribution structure - the two can be combined, but cannot replace each other.

Role differentiation (semantic layer)

dominant nodeTake primary responsibility for the removal of critical blockages or the introduction of decisive terms/resources; the material should show the causal chain of its actions and final state.
Collaboration nodeNecessary but not decisive assistance; or sharing according to a clear contract ratio, rather than being equivalent to dominance by default.
BeneficiaryValue accrues to the host; usually does not automatically equate to "contributing the most".
ReviewerVerify and leave traces, does not participate in revenue attribution on the business side, unless governance dictates otherwise.
Agent contributionOnly when the output has been officially adopted and can be pointed to in the evidence package (ticket, sign-off, merge record) does the attribution discussion enter.

Practical Tip: Reduce the hassle

  • Write it out as early as possible: Deal/Task layer agrees on the expected attribution framework (can still be modified by PoB, but reduces subsequent disputes).
  • Timeline Priority: Email, calendar, contract effective date, and on-chain transaction timestamps are cross-aligned.
  • Objection Procedure: You can apply for review of the archived conclusion, but you need to attach new materials or point out specific logical errors to prevent endless delays.

The quality of attribution determines whether nodes are willing to do heavy work, a long cycle, and a closed loop that is difficult to prove. If it is always "whoever shows up last gets the prize", the network will become short-sighted, which is contrary to the long-termism of PoB.

← Previous8.4 Verification processNext →8.6 Why PoB is important