6.4 · Function nodes
Function node answer: In the closed loop, do you provide the asset side, capital side, delivery side, market side or execution amplifier?
Functional classification is the first layer of the routing table: it determines where demand comes in, where capital is received, how services are unpacked, who handles liquidity and narrative, and which links can be automated but must be auditable.
Overview of function nodes
Project nodeFor example, L2, RWA platform, payment application: carry roadmap, compliance strategy, financing rhythm and currency listing requirements; they are the source of demand and asset narrative.
capital nodeFor example, a single company's allocation range of US$5 million to US$50 million, or a seed-focused crypto fund: determine the valuation logic, term sheet, and co-investment rhythm.
service nodeFor example, Top-tier law firm token group, smart contract auditor, brand public relations retainer: turn verbal recommendations into signature pages and deliverables.
distribution nodeFor example, Tier1 CEX currency listing office, leading KOL matrix, large-scale summit IP: undertaking TGE, market making packages and communication schedules.
Regional nodeNational master node and city node: organize activities, government relations and local capital in the geographical dimension; see 6.5 and 6.6 for details.
Agent nodeFor example, 7×24 monitoring of financing rounds and automatic drafting of first-round contact emails: model boundaries, manual review points, and log retention strategies must be disclosed.
Divide functions first, and then divide responsibilities and contribution measurement; otherwise the roles of the same organization in different links will be mixed, and the PoB will not be able to separate the introduction fee, execution fee and success fee.
Comparison of functional division of labor and TradFi tabletop
Project nodeCorresponding to the corporate account department: Define transaction motivation and timetable.
capital nodeCorresponding buyer sales to capital markets: matching products and constraints.
service nodeCorresponding to the middle office and third-party consultants: put the terms into documents and code.
distribution nodeCorresponding to ECM / sales transaction interface: turning stories into order flow and liquidity.
Regional nodeCorresponding branch coverage: localized relationships and regulatory communications.
Agent nodeCorresponding quantification and middle-office scripts: Amplify standard processes, but do not replace the disclosure point of regulated judgment.
Regional nodes appear side by side with functions in the 6.3 overview, but are often implemented as superimposed labels of "function + geography"; in 6.4, it is emphasized that their functional semantics are "local organization and implementation" to avoid confusion with pure online capital or service nodes.