10.3 · How to join
Admission is a staged path from materials to a first verified outcome.
Admission has two goals: keep unqualified applicants out, so the Proof Ledger stays credible; and let those who qualify reach a working set of permissions and start a first outcome. The path runs through application, due diligence, seat and agreement, onchain authorization, and onboarding. It is not registration; it is admission to an accountable position.
The admission path
Application and materials
Submit the applicant's qualifications, a description of the business, the tier sought, a summary of the resources it can route, and the responsible contact.
Initial review
Check authenticity, fit with current network needs, and any compliance red flags. Licenses, cases, or references may be requested. Passing this stage only opens due diligence; it grants no seat.
Due diligence and draft seat
Interviews, a check on delivery capability, and discussion of conflicts and exclusive scope. The output is a draft seat: tier, draft permissions, initial KPIs, and key agreement terms.
Agreement and compliance
Sign the node agreement, the confidentiality and data terms, and the code of conduct. Offchain duties must match the scope of onchain authorization.
Onchain authorization and Node NFT
After compliance and technical checks pass, mint or assign the Node NFT and map the wallet to the system account. Standard nodes use ERC-721 plus ERC-6551, so each node carries its own account. Open the workspace, deal room, and task queue.
Onboarding and first outcome
Complete tool training and the evidence standard. A node advances or initiates at least one verifiable outcome — joining a deal, delivering a task, or sourcing a qualified project — to activate the seat.
Why admission is not one click
A node can reach non-public deals and the materials of other institutions. Opening that on consumer-registration logic would collapse the trust that PoB and settlement depend on. Admission cost is a fixed operating cost of the network, not a marketing gate.
The first 90 days
The Day-90 first PoB is not an abstract target. It is a nameable, reconcilable deal from the founder's pipeline, which gives an early node a real outcome to advance.
Days 0–30: rules and toolsRead the collaboration standard, the evidence standard, and the data classification. Map internal counterparts in legal, compliance, and technology.
Days 30–60: first verified outcomeCarry at least one auditable delivery or capital action into the PoB input. Set a routine cadence with research and operations.
Days 60–90: review and calibrationAdjust the width of authorization against actual output. Align the next quarter's KPIs with the seat's track.
Ongoing: build the recordKeep the case record and task results current, to support renewal and upgrade review.
The goal after onboarding is not maximum exposure. It is a clean verified outcome that shows the seat is held for a reason.