№ 05·0605 · Network architecture3 min read · Section 6 of 6
5.6 Verification and settlement layer
The closing layer: Proof of Business reconciles evidence into a Verification Node, attributes contribution, and settles value.
Updated
5.6 · Verification and Settlement Layer
L5 · Verification and settlement — turning what was done into what was proven.
The first four layers handle resources, capital, execution, and distribution. The fifth handles the questions that decide whether any of it holds: how a result is confirmed, how contribution is attributed, and how value is settled. Without this layer, WCN would not differ in substance from a higher-grade CRM. This layer is the reason the architecture exists.
PositionL5 — the value outlet of the five-layer architecture
The problem it answersHow a result becomes trustworthy
The question this layer answers: how does a result become trustworthy?
However capable the first four layers are, without L5 the system cannot separate done from claimed to be done. This layer upgrades a subjective narrative into an auditable chain of evidence.
The work of L5: turning "the result happened" into "the result was verified, attributed, and settled."
The three ledgers and the Verification Node
WCN keeps three parallel ledgers — the Project ledger, the Capital ledger, and the Proof ledger. Reconciliation runs along the midline that joins them. When a business outcome reconciles across the three, it produces a Verification Node: an anchor that can be checked independently.
Project ledgerWhat was raised, scoped, and executed — the record of the work itself.
Capital ledgerWhat was committed, deployed, and settled — the record of the money.
Proof ledgerThe verifiable, tamper-evident record of outcomes, joined to the other two by reconciliation.
How verification and settlement run
A result does not enter the record on a claim. It enters once evidence reconciles and a reviewer confirms it.
Evidence submission
The deal owner submits the result evidence — signed agreement, payment record, deliverable, onchain hash, minutes, confirmation. What is required depends on the deal: a financing deal needs the agreement and payment confirmation; a service deal needs the scope and acceptance.
Independent review
A reviewer checks the evidence for completeness, authenticity, a plausible timeline, and risk. A reviewer cannot be a participant in the deal, and the result is confirmed by multiple signatures.
Verification Node
On passing review, reconciliation produces a Verification Node on the Proof ledger. The record is immutable and carries the participants, an evidence summary, the attribution, and timestamps.
Settlement
Verified records are aggregated and settled on a defined schedule. Value is allocated to contributors — nodes, service providers, and agents — by their attribution.
What makes a business loop valid
Proof of Business records a verifiable business outcome, not participation. A loop counts only when four conditions hold.
Externally observableThe result is visible outside the system — a signing, a transfer, a launch, a delivery, a met target.
Verifiable evidenceContracts, receipts, onchain records, partner confirmation, and reviewable logs support the result.
Traceable responsibilityEach step that advanced the outcome maps to a specific node or agent.
Reviewable processA reviewer, re-examining the process, reaches the same conclusion.
The states of a record
On the Proof ledger, a record moves through defined states. Each is a precise term, not a casual one.
VerifiedThe record has passed reconciliation across the three ledgers.
SettledA transaction on the Capital ledger has completed its settlement.
SealedThe record is locked — a final state that can no longer change.
A dispute or audit resolves in a Verdict: a conclusion that cannot be appealed. Proof of Business is an internal mechanism, but its evidence chain can be retrieved and re-examined by external auditors and regulators — evidence-backed, not self-asserted.
Real-time, not year-end
Traditional verification is an audit after the fact — reviewed once the period closes. WCN embeds verification in the moment.
Traditional: post-action auditEstablished and trustworthy, but centralized, gated, and reviewed after the period — which leaves a gap between the action and its confirmation.
WCN: real-time embeddingEach deal enters evidence submission and review as it completes. The evidence chain stays open to external audit, so there is no year-end catch-up.
What fails without this layer
Results stay subjectiveA participant claims to have driven a deal, with no evidence behind the claim. The system falls back to words and relationships.
Attribution is contestedSeveral parties join one deal, and no one can establish who contributed what. Most projects avoid the question, which discourages real contribution over time.
Reputation does not buildWithout verified results, a node's reputation cannot form. The system cannot tell a high-value node from a low-value one.
Value does not accumulateA collaboration closes and dissolves, leaving no record. The network cannot learn from past work or compound on it.
The verification and settlement layer is not a patch on the final step. It is the reason the architecture exists. It gives every collaboration a trustworthy endpoint, every contribution a measurable value, and turns the network from one-off cooperation into a system that accumulates.
