№ 10·0710 · Node joining2 min read · Section 7 of 7

10.7 What a node owes

A node's four duties: bring resources, advance collaboration, submit evidence, comply. Non-contributing nodes face review and exit. A seat is a liability until performance offsets it.

Updated
10.7 · What a node owes

Rights and duties are symmetric: a seat is held against continued verifiable contribution.

A node is a working position, not a paying membership. It carries four duties: bring callable resources into the network, advance the deal and task toward an outcome, submit evidence to standard, and comply with the permissions and review that govern a seat. A node that contributes nothing faces review and exit. Failure can mean downgrade, frozen settlement, or a revoked onchain mapping.

Core questionWhat must a node do, continuously, to hold a seat?
Four dutiesResources · collaboration · evidence · compliance
Governance logicA dynamic filter, not a static roster

The four duties

Bring resourcesKeep callable resources current by seat: a capital node's check size and decision cycle; a service node's available hours and delivery templates; a distribution node's schedule and reach; a regional node's events and institutional contacts. Empty placeholder listings are not accepted.
Advance collaborationRespond to matches, claim tasks, and move milestones — term sheets, audit delivery, listing materials — within the agreed window. An active node advances at least one auditable path each quarter.
Submit evidenceDeliverables, meeting minutes, onchain hashes, and signed scopes enter the evidence package. A material conflict of interest is declared in advance. The standard is working-paper evidence, not verbal confirmation.
ComplyAccept KPI review, spot checks, the compliance questionnaire, and address rotation. Accept a temporary freeze of operation rights during a dispute. A refusal to be reviewed is a material breach.

Why the duties are written into the protocol

If nodes take exposure and data but carry no delivery, the network's signal-to-noise ratio and the credibility of PoB both fall, which harms every node that keeps its duties. A high-quality network grows through verified outcomes, not through a head-count fee.

KPI focus by node type

Node typeTypical KPI focusCommon red lines
CapitalResponse time, due-diligence rate, rate of closing or clear rejectionSustained non-response; bad-faith repricing or breach
ServiceOn-time delivery rate, re-inspection pass rate, satisfaction samplingRepeated delays; delivery that diverges from the brief
Distribution / market makingAgreed reach or depth compliance, compliance disclosureFalse traffic; market manipulation; undisclosed interest
RegionEvents held, institutions introduced, localization supportAn exclusive seat with no activity organized

The thresholds follow the signed agreement and the current operating manual. The table aligns expectations; it is not a unilateral commitment.

Renewal, upgrade, downgrade, and exit

RenewA rolling review: no open compliance matters, KPIs met, and seat fees settled where they apply.
UpgradeSustained performance and no major dispute can support a wider region, track, or operation right. Security and legal sign-off is required.
DowngradeInsufficient output or a lower risk-control score narrows visible deals and removes operation rights, leaving read access.
ExitA material breach, fraud, a sanctions hit, or repeated refusal of evidence ends the agreement and revokes the NFT mapping, disclosed to partners within the limits the law allows.
The node system stays alive through an enforceable exit. Removing the seat that only enters and never leaves is what protects long-term network capital.