<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:itunes="http://www.itunes.com/dtds/podcast-1.0.dtd" xmlns:googleplay="http://www.google.com/schemas/play-podcasts/1.0"><channel><title><![CDATA[BringTrade Field Notes: Operating Doctrine]]></title><description><![CDATA[Frameworks, rules, and field-tested thinking behind BringTrade’s consent-based opportunity routing system.]]></description><link>https://fieldnotes.bringtrade.com/s/operating-doctrine</link><image><url>https://substackcdn.com/image/fetch/$s_!mhHO!,w_256,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F1b695a5f-2cfa-4715-ade1-b6c5a456b650_608x608.png</url><title>BringTrade Field Notes: Operating Doctrine</title><link>https://fieldnotes.bringtrade.com/s/operating-doctrine</link></image><generator>Substack</generator><lastBuildDate>Sat, 16 May 2026 01:13:33 GMT</lastBuildDate><atom:link href="https://fieldnotes.bringtrade.com/feed" rel="self" type="application/rss+xml"/><copyright><![CDATA[Kory Paul]]></copyright><language><![CDATA[en]]></language><webMaster><![CDATA[bringtradefieldnotes@substack.com]]></webMaster><itunes:owner><itunes:email><![CDATA[bringtradefieldnotes@substack.com]]></itunes:email><itunes:name><![CDATA[Kory Paul]]></itunes:name></itunes:owner><itunes:author><![CDATA[Kory Paul]]></itunes:author><googleplay:owner><![CDATA[bringtradefieldnotes@substack.com]]></googleplay:owner><googleplay:email><![CDATA[bringtradefieldnotes@substack.com]]></googleplay:email><googleplay:author><![CDATA[Kory Paul]]></googleplay:author><itunes:block><![CDATA[Yes]]></itunes:block><item><title><![CDATA[How a Consent-Based Opportunity Routing Network Actually Works]]></title><description><![CDATA[BringTrade is not a directory. It is a trust-and-routing network where opportunities move through consent, context, and controlled bridges.]]></description><link>https://fieldnotes.bringtrade.com/p/how-a-consent-based-opportunity-routing</link><guid isPermaLink="false">https://fieldnotes.bringtrade.com/p/how-a-consent-based-opportunity-routing</guid><dc:creator><![CDATA[Kory Paul]]></dc:creator><pubDate>Fri, 15 May 2026 11:50:24 GMT</pubDate><enclosure url="https://substackcdn.com/image/fetch/$s_!mhHO!,w_256,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F1b695a5f-2cfa-4715-ade1-b6c5a456b650_608x608.png" length="0" type="image/jpeg"/><content:encoded><![CDATA[<h2>1. The wrong model is a directory</h2><p>A directory says: here are the names. Go figure it out.</p><p>That&#8217;s not how work actually moves.</p><p>When someone needs a real person for a real job &#8212; concrete on a tight schedule, a vendor who can show up Saturday, a sub who can handle the kind of scope nobody wants to talk about &#8212; they&#8217;re not looking for a list. They&#8217;re looking for the right person at the right moment, with the right context already in place.</p><p>A directory can&#8217;t do that. A directory treats every name like it&#8217;s available, qualified, and ready. Field reality says otherwise. Some people are great but tied up. Some are free but not right for the scope. Some shouldn&#8217;t be exposed at all until there&#8217;s a real reason to make the introduction.</p><p>Most platforms that try to &#8220;organize the trades&#8221; fail in this same way: they confuse a list of names with a routing problem. They&#8217;re not the same problem.</p><div class="subscription-widget-wrap-editor" data-attrs="{&quot;url&quot;:&quot;https://fieldnotes.bringtrade.com/subscribe?&quot;,&quot;text&quot;:&quot;Subscribe&quot;,&quot;language&quot;:&quot;en&quot;}" data-component-name="SubscribeWidgetToDOM"><div class="subscription-widget show-subscribe"><div class="preamble"><p class="cta-caption">Thanks for reading BringTrade Field Notes! Subscribe for free to receive new posts and support my work.</p></div><form class="subscription-widget-subscribe"><input type="email" class="email-input" name="email" placeholder="Type your email&#8230;" tabindex="-1"><input type="submit" class="button primary" value="Subscribe"><div class="fake-input-wrapper"><div class="fake-input"></div><div class="fake-button"></div></div></form></div></div><h2>2. What routing actually means</h2><p>Routing means the opportunity doesn&#8217;t move as a broadcast. It moves through context.</p><p>A need shows up. A pattern becomes clear. Someone in the network might fit. Before any name moves, I look at the shape of the opportunity, the kind of person or company that should see it, and the risk of opening the wrong door too early.</p><p>The job isn&#8217;t to make everything visible to everyone. The job is to move the right signal to the right side at the right time.</p><p>In practice that might mean introducing one qualified sub to a GC who&#8217;s been burned by ten. It might mean holding an opportunity quiet until the partner is actually ready to receive responses. It might mean writing a public-safe description of a demand pattern so the right people can raise their hand, while the private details stay private.</p><p>Routing is quiet before it&#8217;s useful. Then it becomes very practical.</p><h2>3. Why consent matters</h2><p>Trust breaks when people get exposed before they agreed to be exposed.</p><p>A name is not a lead just because I know it. A private conversation is not public material just because it reveals real demand. A future opportunity is not a call to action until the people involved have agreed on what can be said and what stays protected.</p><p>I&#8217;ve watched relationships burn over this. One bad introduction reaches three good people who didn&#8217;t ask for it. One careless message lands in a partner&#8217;s inbox where they weren&#8217;t expecting it. One vendor&#8217;s price becomes visible when they thought it was confidential. Each time, the network loses something it can&#8217;t easily rebuild.</p><p>Consent keeps the network clean. It protects the people behind the patterns. It lets me talk publicly about what&#8217;s happening in the market without turning private people, private projects, or private timing into somebody else&#8217;s inventory.</p><p>That&#8217;s the line: describe what helps the market understand the pattern, but don&#8217;t expose the person, project, or relationship before the bridge is ready.</p><h2>4. What a controlled bridge is</h2><p>A controlled bridge is a routed connection with gates.</p><p>It is not a public list. It is not a cold-intro pile. It is not a promise that every responder gets through.</p><p>A controlled bridge means the opportunity has been framed, the responder lane has a reason to exist, and the next step is governed by review and consent. One side may need to approve the wording. The other side may need to confirm capacity. I may need to redact details, check fit, or decide that the bridge should stay closed for now.</p><p>The point isn&#8217;t control for its own sake. The point is control so trust can survive scale. A network that doesn&#8217;t gate its bridges falls apart quickly. A network that gates them well keeps growing without burning the people who made it possible.</p><h2>5. Why this matters</h2><p>Markets have plenty of noise. What they lack is clean routing.</p><p>People in the trades &#8212; owners, contractors, subs, vendors, workers, lenders, partners &#8212; don&#8217;t need more random exposure. They need useful context, protected identity, and a path forward that doesn&#8217;t burn the relationship before there&#8217;s a real fit.</p><p>When routing is done well, the public can see the demand pattern without seeing the private details. Responders can raise their hand without being thrown straight into a live deal. Partners can explore future capacity without becoming a public bid package. The market understands more, and the people in it are protected better.</p><p>That&#8217;s the work: make demand legible, keep people protected, and open bridges only when there&#8217;s enough consent and context to do it responsibly.</p><h2>6. The rule</h2><p><strong>Publish the pattern. Protect the person.</strong></p><p>That&#8217;s the operating rule.</p><p>If the market needs to understand what&#8217;s happening, I describe the pattern. If a person, company, project, or relationship needs protection, I protect it. If the bridge isn&#8217;t ready, I don&#8217;t force it open.</p><p>BringTrade is not a directory. It is a consent-based opportunity routing network. The value is not just in knowing who exists. The value is in knowing when, how, and whether a bridge should be opened.</p><p>&#8212; Kory</p><div class="subscription-widget-wrap-editor" data-attrs="{&quot;url&quot;:&quot;https://fieldnotes.bringtrade.com/subscribe?&quot;,&quot;text&quot;:&quot;Subscribe&quot;,&quot;language&quot;:&quot;en&quot;}" data-component-name="SubscribeWidgetToDOM"><div class="subscription-widget show-subscribe"><div class="preamble"><p class="cta-caption">Thanks for reading BringTrade Field Notes! Subscribe for free to receive new posts and support my work.</p></div><form class="subscription-widget-subscribe"><input type="email" class="email-input" name="email" placeholder="Type your email&#8230;" tabindex="-1"><input type="submit" class="button primary" value="Subscribe"><div class="fake-input-wrapper"><div class="fake-input"></div><div class="fake-button"></div></div></form></div></div>]]></content:encoded></item></channel></rss>