WCNCitizen Ledger
№ 08·0308 · Proof of Business2 min read · Section 3 of 6

8.3 What doesn’t count

Exclude superficial actions, repeated claims, and proxy indicator cheating; compare with the failure modes of airdrops/points/pledge incentives.

Updated
8.3 · Exclusion rules

Half of the credibility of PoB comes from what it admits, and half comes from what it firmly does not record in the ledger.

The scarcity of PoB comes from a double gate: admitting high-standard results and systematically rejecting inputs that are easy to forge, repeat, and outsource. Without exclusion rules, the network would repeat the distortion that Web3 has already seen - optimizing snapshot rules instead of optimizing delivery.

What this page doesDelineate the outer edge of PoB, service anti-cheating and audit standards
core themesEliminate noise, identify spurious contributions, and align incentives
Reading highlightsTypical exclusions; gamification attack surface; comparison with on-chain proxy metrics

Explicitly exclude: Behavior that has not yet entered the results layer

Pure posting, pure forwarding, pure group building, pure recommendation without follow-up, pure intention negotiation, and "help" without deliverables do not constitute PoB objects. The reason has nothing to do with PoW/PoS: the marginal copying cost of these behaviors approaches zero, and there is no stable causal chain with the business end state - if it is accounted for, incentives will flow to volume and relationship performance rather than output.

pure touchExposure, likes, and the number of community members themselves; analogous to airdrop interaction volume, it can be earned and is difficult to link to income/delivery.
Pure introduction without closed loop"Knowing someone" does not mean "promoting signature or payment"; the final state and evidence of 8.2 are required.
plans and intentionsLOI, verbal consensus, exclusive negotiations - are not considered closed in TradFi.
no evidence claimClaiming to be in charge but having no chronological materials and no traces of reconciliation by a third party means that performance cannot be reviewed.

Pseudo-contribution and anti-gamification points

Duplicate claimThe same final state is declared as the unique dominant by multiple entities; event numbers, timestamps and material mutual exclusion rules are required, and dispute adjudication is introduced when necessary.
The last mileIt only appears at the end before the result, but there is no key node record; attribution must be based on who unlocked the blocking condition (see 8.5).
Loud volume replaces high valueIsomorphic to the failure of the integral system: what is observable is noise, what is unobservable is true advancement.
Tool output not acceptedIf the Agent/script output has not entered the adoption and acceptance of humans or customers, it is the same as undeployed code and does not count as a business result.
Cycle and brush volumeAnalogy to brushing up transaction volume and reversing liquidity: If the evidence only comes from controllable parties and no external beneficiaries, the review should be strict.
Evidence piecing / backdatingThe time series is cross-checked with third-party records; consistent with GIPS requirements of "completeness, accuracy, and non-misleading", and fraud is rejected with one vote.

Why it's different from common Web3 rewards

  • Airdrops and Tasks: Optimize Rule Programmability, but not optimize Delivery Quality; Witch cost can be lower than the real customer acquisition cost.
  • Pledge: Optimize Capital Lock, do not optimize Service Completion; large accounts may not complete any customer closed loop.
  • Points Ranking: Optimize short-term action frequency to easily decouple from real alpha in the Brinson sense.

PoB deliberately increases the cost of "scoring", so that it is better to make a real closed-loop transaction than to earn points. This is the economic core of anti-gamification, not just a moral appeal.

If "what doesn't count" is laxly implemented, PoB will quickly be diluted into another marketing score; strong implementation relies on Proof Desk standards, transparent records of supplements and rejections (see 8.4).

The exclusion rules protect the scarcity of results and the marginal returns of honest nodes; what they harm is the settlement semantics of the entire network.
← Previous8.2 What counts as an effective closed loop?Next →8.4 Verification process