№ 04·0104 · How WCN works3 min read · Section 1 of 4
4.1 Minimum business closed loop
What counts as a closed loop and what does not — WCN's single test for separating noise from value.
Updated
4.1 · Minimum business loop
The smallest unit of WCN is not content, a relationship, or activity. It is a verifiable business loop.
Web3 has no shared standard for business completion. Teams record activity, post counts, TVL, and member numbers, but few systems track whether a deal actually closed. WCN's minimum business loop answers that gap.
Core definitionResource enters + work advances + result is verified = one loop
Why it mattersThe loop is WCN's only test for separating noise from value
TradFi referenceDeal completion rate in PE and VC
A minimum business loop equals a resource introduced, plus a task executed, plus a result verified. Remove any one of the three and it is not a loop.
Three necessary conditions
A resource enters
A node brings a real project, capital, service, or regional resource into the network. The resource must be specific — a round being raised, an allocation to deploy, a service to deliver — not "I know some people."
Work advances
People and agents move the resource from an opportunity to a result inside a Deal and its Tasks. Advancing means someone owns it, actions occur, and status changes — not a group chat.
A result is verified
Evidence is submitted, reviewed, and approved, and attribution is clear. The result enters the Proof ledger. Verification means third-party-verifiable evidence — not "he said it was done."
What counts, and what does not
This is the line between WCN and every activity-reward system.
Counts as a loopA seed round closes, with agreement and payment record. A forensic audit is accepted, with SOW and deliverables. A market-making service goes live, with contract and onchain liquidity data. A project is introduced and lists, with communication record and launch evidence.
Does not countTwo parties are introduced but nothing follows. A deck is shared but no work advances. A meeting happens but produces no action items. An agent runs research that no one adopts. A post goes out but converts no business.
Industry reference. In PE and VC, deal completion rate is a core metric. It does not count how many projects you see; it counts how many you actually close. A fund may screen 3,000 projects a year and complete 10 to 15. WCN's loop is the same test: only a closed deal enters the value layer.
The test is simple. Remove an action, and if the business result still occurs, that action is not part of the loop. Only participation that causally contributes to the outcome counts.
The standard loop path
A node introduces a resource → the opportunity enters a Deal and its Tasks → people and agents execute and advance → a result forms → evidence enters the Proof Desk → review passes → a Verification Node is generated → the entry proceeds to Settlement.
Each step on the path carries a clear owner, a status, and an output. There are no ownerless tasks and no stateless progress.
Why a result is verified: four conditions
A loop only verifies when all four conditions hold. They come straight from how Proof of Business reconciles a result.
The result is externally observableA signing, a wire, a launch, a delivery, or a KPI met — visible outside the parties' own account.
The evidence is verifiableContracts, receipts, onchain records, counterparty confirmation, and reviewable logs. Words alone do not verify.
Responsibility is traceableEach advancing action maps to a specific node or agent. No anonymous contribution enters the record.
The process is re-reviewableA reviewer re-examining the process reaches the same judgment. Verification must reproduce, not depend on one person's read.
Why Web3 has lacked this concept
No shared definition of resultDefinitions of success are fragmented — TVL for some, member counts for others, token price for the rest. No system uses real business completion as the common measure.
No evidence infrastructureTradFi has a full audit chain: large auditors, law firms, custodians. In Web3, evidence scatters across chat, email, documents, and the chain, with no shared collection and review.
Incentives reward process, not resultAirdrops, points, check-ins, and social tasks reward actions taken, not results produced. The system then fills with noise.
Attribution is hard, so teams avoid itIn multi-party work, fixing who contributed how much is difficult. Most projects split evenly or negotiate by relationship rather than build a systematic attribution mechanism.
Why the loop is the origin of the system
It defines the value boundaryThe loop is WCN's only test for what is worth recording. No loop means no PoB, no entry to Settlement, and no value distribution.
It drives incentive designEvery incentive and settlement turns on the loop. Resource allocation then points to operators who advance loops, not operators who make noise.
It anchors execution qualityA loop requires an owner, a status, and an output at each step. That requirement forces real work instead of the appearance of work.
It accumulates network valueEach verified loop settles into a system asset: node reputation, matching accuracy, attribution data, and agent training material. The record grows harder to replace over time.
Every later structure in WCN — PoB, settlement, reputation, governance — rests on the minimum business loop. Understand the loop, and you understand how WCN extracts real value from noise.
