Enterprise
What is trust routing, and how does it protect a declined introduction?
Deal flow is a routing problem: who knows whom, and who will vouch. The refusals are what make a "no" safe to give.
The answer
Trust routing is the practice of routing an introduction along consented relationships, where every hop’s owner must agree and there is no partial yes. It protects a declined introduction by rendering it to the requester identically to a path that never existed, so a refusal reveals neither who declined nor that a relationship was there to decline.
Only the owner of a relationship consents to crossing it
Every request lands proposed; nothing constructs a consented hop directly; and an introduction requires every hop to consent, with no partial yes that routes most of the way and hopes. Agents may suggest a path; the humans who own each edge consent to it — this is not bent at any level of automation, because the whole value of a warm introduction is that the person in the middle actually agreed.
Standing from what others assert, never from activity
The measured figure counts only sealed, non-trivial outcomes; a party acting alone moves nothing about its own standing, and a test exists whose entire job is to prove unilateral activity moves the number by zero. Every figure carries a register — measured, asserted or estimated — and a hearsay-only or unrenewed edge contributes only at the estimated level.
The underlying concept is defined canonically at Trust routing — FlashyOS. This page answers the build question; that page answers the “what is it” question.
Talk to the practice
Tell us what you are trying to build and what has to be true for it to work.
Contact