--- name: discovery-first-contact-substrate description: Cycle 86 — canonical synthesis at operational-substrate-scale naming the pre-arrival layer. How a receiver discovers the village market, the hosting page, the bio; what carries trust BEFORE they land on any surface; what the framework refuses at propagation scale. Bridges trust-generation (c84) + receiver-face (c83) + Pattern Library v1.6 to the moment-of-first-contact that precedes everything else. Companion to c84 at discovery scale — c84 named the trust mechanisms operating ON the surfaces; c86 names the trust mechanisms operating BEFORE the surfaces. metadata: type: canonical-synthesis (operational-substrate scale) cycle: 86 (2026-05-27) parent_synthesis: Trust_Generation_Operational_Substrate (c84) · Receiver_Face_Canonical_Synthesis (c83) · Capacity_Infrastructure_Lens (c70) kevin_mark: "c then a then b" · "continue" → Candidate A second in sequence after Cartography v2 scope: pre-arrival substrate · discovery channels · propagation patterns · refused operations at discovery layer · geographic-scale discovery (global · local · travel-aware) status: canonical · informs propagation choices · pickup-able for practitioners building infrastructure that needs discovery without becoming a platform license: use freely · adapt as needed · credit sources --- # Discovery / First-Contact Substrate ## Why this synthesis C83 named what receivers experience AT the surfaces. C84 named the trust mechanisms operating ACROSS the surfaces. Both assumed the receiver had already arrived. The pre-arrival substrate — how discovery happens, what carries trust before any surface is read, what the framework refuses at propagation scale — is uncovered. This synthesis fills that gap. It is the third companion in the surface-design substrate set (c70 lens · c83 receiver-face · c84 trust-generation · c86 discovery) that together describe how this framework operates at every layer from pre-arrival through engagement to closure. The synthesis matters most when: a practitioner asks "how do I tell people about this?"; a pickup-practitioner asks "how does this propagate?"; the village market needs receivers actually within the 45 mi radius to find it; the hosting page needs potential hosts in places Kevin is planning to visit. --- ## What "discovery" IS in this framework **Discovery happens BEFORE the receiver knows what they're discovering.** A receiver who lands on /village-market.html has already discovered something — but at the moment of landing, they don't yet know what "village market" means in this framework. The discovery moment is the structural threshold between *not-knowing-this-exists* and *reading-the-first-page*. At that threshold, the receiver carries: a referrer's framing (if any), prior associations from words in the URL or referral, suspicion patterns from platforms they've encountered before, the body's resonance or non-resonance with what they're about to read. All of these arrive WITH them. The first page either confirms or refuses what arrived. **Discovery is not marketing.** Marketing is the platform-shape of discovery — discovery designed to overcome the receiver's body. Discovery in this framework is the substrate-shape — discovery designed to be available WITHOUT overcoming the receiver's body. The two are structurally inverse, like substrate-trust and platform-trust (per c84). --- ## The actual discovery pathways How discovery happens in this framework today, as substrate-of-record: ### Pathway 1 — Substack subscription / direct readership Kevin's Substack publishes articles ([kevinmears.substack.com](https://kevinmears.substack.com); 24+ articles). Each article is a self-contained gift form. Receivers find articles via: - Direct subscription (intentional opt-in) - Substack's own recommendation surfaces (algorithmic; partially within Kevin's control) - Cross-posting where appropriate (LinkedIn for some pieces) - Referrer-shared links (someone sends an article) **What carries trust at this discovery moment:** the article itself. Each Substack article is structurally a small instance of the framework — voice register, refusal patterns, gift form, use-freely license. A receiver who lands on one article reads the framework operating; if it resonates, they may read more. **Anti-pattern refused here:** subscription-as-engagement-optimization. No "join 10,000 subscribers" social proof. No "free preview" gated content. No urgency framing. The Substack is a place articles live; subscription is one way to be notified when new articles publish; nothing pressures it. ### Pathway 2 — Direct word-of-mouth (one body to another) Someone who has read or worked with the framework recommends it to someone else. The referrer's existing trust transfers across the introduction. **What carries trust at this discovery moment:** the referrer's own relationship to the framework. A receiver hearing "you should look at this; I read the manuscript and it shifted how I think about consent architecture" arrives pre-trusted. The referrer's body is the trust carrier. **Why this pathway is load-bearing:** because it propagates the framework at human pace, body-to-body, with the referrer's own attention as the discriminator. Pattern #079 (Paired Transmission) operates here — the JUST_KEVIN ↔ CEREMONIAL_GIFT V1/V2 confirmed paired transmission across audiences. Each paired transmission is a discovery instance. **Anti-pattern refused here:** referral incentives. No "invite 3 friends, get a discount." No referral tracking. No affiliate links. The word-of-mouth must be unincentivized to remain trust-bearing. ### Pathway 3 — Cross-pollination from referenced work A receiver encounters Kevin's framework via someone else's writing that references it. The references.json on oursharedgifts.org tracks specific reciprocal references; informal references happen across podcasts, articles, conversations. **What carries trust at this discovery moment:** the referencer's structural authority for the receiver. A receiver who reads X's article and X cites Kevin arrives at Kevin with X's structural endorsement carrying. References-as-references (#102) extends this — when a host writes a reference for hosting Kevin's bus, that reference is itself a discovery surface for future hosts who read it. **Anti-pattern refused here:** SEO games. No keyword stuffing. No backlink schemes. No reciprocal-citation engineering. The cross-pollination must remain organic — the framework's structural work earns the references it earns. ### Pathway 4 — Community contexts (where Kevin shows up as a body) Kevin's existing community memberships and engagements: - BFI Design Science Studio (2026 cohort) - DSS community (the somatic-installation audience) - Recognition Infrastructure Podcast appearances - Local connections in Grass Valley / Nevada City area - Specific networks the framework has reached (Aron, Kory, Megan, Micah, Shanti) Discovery happens because Kevin shows up in these contexts as a body, and the work travels with the body. **What carries trust at this discovery moment:** the community's own architecture — the trust generated by being IN that community, which transfers to the framework Kevin brings. **Anti-pattern refused here:** community-as-funnel. The communities are not lead-gen surfaces. Kevin shows up because the work belongs in those contexts, not because the contexts are convertible. ### Pathway 5 — Local-radius word-of-mouth (specific to village market) For the village market specifically, discovery must reach receivers GEOGRAPHICALLY within the 45 mi radius. This is a structurally distinct discovery problem from global readership. Local discovery pathways: - Neighbors who know Kevin parks the bus in Grass Valley - Local community boards (bulletin boards, library notice boards, community center pinups — physical surfaces) - Local newspapers / radio (if appropriate and unincentivized) - Local in-person referral (someone says "have you tried the village market?" to someone else in the radius) - Local existing fabric (mutual-aid networks, gift economy practitioners in the area, who already operate adjacent shapes) **What carries trust at this discovery moment:** the local context. Receivers in a 45 mi radius share substrate Kevin can't write — they know the area, they know who lives there, they have their own networks. Local discovery is structurally about being where the local fabric already gathers. **Anti-pattern refused here:** local-targeting-via-platform-advertising. No Nextdoor ads. No Facebook neighborhood-group ads. No paid Google Maps placement. The village market reaches locals through local pathways that don't extract on either end. ### Pathway 6 — Travel-aware discovery (specific to hosting page) For the hosting page, discovery operates on a different axis — receivers anywhere Kevin might travel become relevant when his travel windows align with their location. Travel-aware discovery pathways: - "Where I'm headed" section on /hosting.html (planned per Thread 2) surfacing Kevin's upcoming travel windows publicly - Existing host references — past hosts who became aware of Kevin's practice through hosting and may refer other potential hosts in their network - Specific outreach when planning travel — Kevin's existing community in regions he plans to visit - Cross-region community connections (the framework's network extends across geographies Kevin can travel through) **What carries trust at this discovery moment:** the structural fit between the host's offerings and Kevin's spec — both visible publicly, both unambiguous about what's wanted and what's offered. **Anti-pattern refused here:** general hosting-platform listings (Couchsurfing, Boondocking apps, etc.). The hosting arrangement is structurally specific (bus-living + PFRC + parking-for-labor); generic platform listings would dilute the discrimination. ### Pathway 7 — Search (specific phrases land receivers) A receiver searches for something specific and encounters Kevin's work — "gift economy not platform," "PFRC instrument," "recognition infrastructure," "bus living mutual aid." **What carries trust at this discovery moment:** the specific vocabulary itself. A receiver searching exactly the framework's vocabulary is structurally pre-resonant; they were looking for what the framework is. **Anti-pattern refused here:** SEO optimization for high-traffic generic terms. The framework refuses to compete for "gift" or "mutual aid" as search terms; it lets specific structural vocabulary be the discriminator. ### Pathway 8 — Direct URL / link-from-document A receiver lands directly via a URL someone gave them, a link from a document they're reading, a reference cited in something else. No referrer context other than the link itself. **What carries trust at this discovery moment:** the first page they land on. This is the highest-stakes pathway because trust must generate from the page alone. The receiver-face substrate (c83) governs what they experience here; the trust-generation substrate (c84) provides what mechanisms operate. **Anti-pattern refused here:** landing-page A/B testing. No experimental variations to optimize conversion. The landing page is what it is; the receiver either reads register or doesn't. --- ## What carries trust at the discovery moment (before any surface) The receiver hasn't read a single page yet. What can carry trust at that pre-surface threshold? ### Mechanism α — The naming itself The vocabulary of the framework is structurally distinctive. "Recognition Infrastructure" doesn't sound like a SaaS product. "Village Market" within a "45 mi radius of wherever the bus is parked" doesn't sound like a platform. "Use freely. Adapt as needed." doesn't sound like a licensing rights statement. The vocabulary signals what the framework is before any content is read. A receiver who encounters the naming via referral or search reads the naming and either resonates or doesn't. **Best practice:** the naming should remain structurally specific. Refuse generic naming that competes with platforms ("Our Gift Marketplace" would be platform-shape; "Village Market within 45 miles of wherever the bus is parked" is substrate-shape). ### Mechanism β — The referrer's body When discovery happens via word-of-mouth, the referrer's own relationship to the framework IS the trust carrier. A receiver hearing "I've been reading this for two years and it shifted how I think about consent architecture" arrives with the referrer's two-year relationship as their initial trust deposit. **Best practice:** make it easy for a referrer to give just enough context to set the stage without over-explaining. The framework is structurally self-explaining once the receiver reads a few sentences; the referrer doesn't need to sell. ### Mechanism γ — The visible refusal at first surface Even before reading deeply, a receiver scans for what the framework refuses. If the landing page explicitly names refused extraction patterns (per c84 Mechanism 2), the receiver immediately reads structural difference. The refusals are detectable at scan-speed; their presence is a trust signal before any content is read substantively. **Best practice:** every entry surface (landing pages, indexes, anywhere a receiver might first arrive) carries explicit refusal in its first screen. The refusals page itself is one such surface; /index has the "Not a business pretending to be a gift. Not a platform. Not a community." line that does this work. ### Mechanism δ — Voice register at first read Within the first 30 seconds, the receiver reads voice register. If the register holds (per c84 Mechanism 8 + c83 c24 distinction), trust transmits. If the register fragments (marketing-voice on landing, technical-voice in docs, personal-voice in bio), the receiver experiences whiplash and tracks it as inauthentic. **Best practice:** voice register holds across every surface a discoverer might first land on. The /index, /refusals, the village-market protocol page, any Substack article must all read in the same register. ### Mechanism ε — The pre-existing body of work The bio-as-substrate (#102) operates at discovery layer too — but not by being read in full. The bio operates at discovery because IT EXISTS. The receiver who lands knowing "there's a manuscript here · there's a Pattern Library · there's two years of Substack articles" doesn't need to read them all to feel the depth. The presence of the body of work IS a trust mechanism. **Best practice:** make the existing body of work navigable from any landing. A discoverer should be able to see, within 10 seconds, that this isn't a thin platform — there's depth they can sink into if they want. The library link in the nav is doing this work. ### Mechanism ζ — The bounded scope at first contact When a receiver sees that this is one practitioner's specific instance ("the bus is parked in Grass Valley · 45 mi radius · 72 hour records · Kevin's instance choices"), they experience structural bounded-ness. The framework isn't claiming to be THE solution; it's one practitioner's instance. That bounded-ness is itself trust-generating at first contact. **Best practice:** never present a surface as universal-platform shape. Be specific about scope from the first page. The /current page does this; the village-market protocol's "Kevin's instance choices" section does this; the discoverer reads bounded-scope as honest. --- ## What the framework refuses at propagation scale The eight protocol-level refusals (per c73/c80 village market protocol) extend to discovery layer. Plus discovery-specific refusals: ### Refusal 1 — No engagement-optimization in propagation The framework refuses to engineer discovery for higher conversion. No A/B-tested headlines. No urgency framing. No scarcity manipulation. No countdown timers. No "limited spots." Discovery is whatever it is at its own pace. ### Refusal 2 — No tracking analytics No Google Analytics. No Facebook Pixel. No Mixpanel. No Heap. The site doesn't measure how receivers discovered it, how they moved, how they bounced. The receiver's discovery is the receiver's; the framework doesn't surveil it. ### Refusal 3 — No referral incentives No "invite 3 friends, get X." No referral tracking codes. No affiliate programs. Word-of-mouth happens because it happens; never because it's incentivized. ### Refusal 4 — No SEO games No keyword stuffing. No backlink schemes. No metadata gaming. No structured-data manipulation. The framework appears in search results for what it actually says, in the words it actually uses. ### Refusal 5 — No paid amplification No paid ads. No boosted posts. No sponsored content. No paid placement. The propagation is unpaid by design. (Pattern #100 architecture-shrinks-when-values-sharpen operates here — when "propagation must be unpaid" is values-explicit, the architecture refuses paid channels.) ### Refusal 6 — No platform optimization No "growth hacking" for Substack or any other platform. No optimization for the platform's algorithm. The framework uses Substack as a publishing surface; it does not optimize for Substack's amplification mechanics. ### Refusal 7 — No platform-mediated discovery The framework refuses to be discoverable primarily through someone else's platform (Instagram-as-bio, TikTok-as-distribution, LinkedIn-as-marketing). Some platform-presence may exist (LinkedIn for some pieces); none of it is the primary discovery surface. The primary discovery surface is the receiver's own attention finding the work. ### Refusal 8 — No creator economy enrollment The framework refuses to operate as a "creator" within someone else's platform economy. No Patreon-as-monetization. No paid Substack tiers. No "exclusive content for subscribers." The work is freely available; subscription is just notification, not gated access. ### Refusal 9 — No urgency at the discovery threshold The receiver who arrives without prior knowledge is given time. No "act now." No "only X days left." No deadline pressure. The framework refuses to compress the discoverer's body's discrimination time. These nine refusals at discovery layer extend the village-market protocol's eight refusals + the c30 eleven refused extractions to the pre-arrival territory. --- ## Pattern Library v1.6 patterns operating at discovery scale | Pattern | What it does at discovery | |---|---| | #054 — Case Portrait Form | The pattern propagates; the instance doesn't replicate. Discovery transmits the form, not Kevin's specific instance. | | #079 — Paired Transmission | JUST_KEVIN ↔ CEREMONIAL_GIFT V1/V2 confirmed paired transmission across audiences — substrate-level discovery pattern | | #102 — Bio-as-Substrate / References-as-References | The whole site IS the bio; references transmit substrate-trust at discovery | | #032 — Container-Holder Distributed | Discovery shouldn't load-bear on Kevin's continuous attention — propagation should operate at the framework's own pace | | #076 — Empty-Space-Refusal Principle | Discovery surfaces must support receivers arriving when Kevin is off-grid; no urgency-pressure that requires immediate engagement | | #093 — Vocabulary-Without-Discipline Drift | At propagation scale: when vocabulary travels without the disciplines, the drift toward platform-shape begins | | #099 — Vocabulary-Borrow-While-Structure-Refuses | When the framework's vocabulary is borrowed by adjacent work, the discipline of explicit refusal-enumeration is what keeps the borrowing substrate-honest | | #100 — Architecture Shrinks When Values Sharpen | At propagation scale: when "unpaid · unmediated · unincentivized" values sharpen, the architecture shrinks to refuse paid and mediated channels | --- ## Three scales of discovery in this framework The framework operates discovery at three structurally distinct scales: ### Scale I — Global discovery (the bio-substrate level) The whole site, the Substack, the references, the manuscript, the canonical references. Discoverable to anyone anywhere via referral, search, or directly-shared link. No geographic constraint. **What's at this scale:** the framework itself, manuscript, library, refusals, offerings, transmissions. **Propagation pattern:** body-to-body word-of-mouth + Substack publication + cross-pollination from referenced work. Slow by design. **Refusals:** paid amplification, tracking, urgency, all of the nine above. ### Scale II — Local discovery (the village market level) The 45 mi radius. Discoverable only to receivers near where the bus is parked. Discovery must reach geographically. **What's at this scale:** village market map, current bus location, local fabric coordination. **Propagation pattern:** local word-of-mouth, neighbor-to-neighbor, community boards, existing local mutual-aid networks. Even slower than global; depth-over-breadth. **Refusals:** geographic-targeting via platform ads, local SEO games, paid Nextdoor or neighborhood-group presence. ### Scale III — Travel-aware discovery (the hosting page level) Wherever Kevin plans to travel. Discoverable to potential hosts in regions Kevin will visit. Discovery is structured by trip-planning + host-side networks. **What's at this scale:** hosting page, Where-I'm-Headed section, references from past hosts, the PFRC instrument. **Propagation pattern:** existing host network referrals, specific outreach when planning travel, cross-region community connections. **Refusals:** general hosting-platform listings, profile-based discoverability, generic "host directory" framing. The three scales operate independently but share substrate (the bio-as-substrate, the eleven refused extractions, the voice register continuity, the trust-generation mechanisms). --- ## The pickup form — Discovery substrate a pickup-practitioner installs A practitioner who has installed the c84 trust-generation substrate also needs Discovery substrate operating. Step-by-step: **Step 1 — Refuse the platform-discovery toolkit from day one.** Before publishing anything, the practitioner decides what propagation channels they refuse (paid ads, tracking, referral incentives, urgency framing). Make the refusal list explicit as substrate-of-record. **Step 2 — Build the body of work first; discovery follows.** Don't start with "how do I get discovered?" Start with "what am I publishing?" The body of work IS the discovery substrate; you can't optimize discovery before there's something to discover. **Step 3 — Choose one publication surface where the form fits.** For Kevin: Substack. For other practitioners: it might be a personal blog, a Forgejo project page, a fediverse instance, a written PDF circulated by email. The choice is whatever surface lets the work appear in its own register without platform-mediation. **Step 4 — Make the refusals visible at the entry threshold.** Whatever the discoverer's first landing surface is, explicit refusals must be in the first screen. This is the trust-at-discovery mechanism. **Step 5 — Let propagation be unincentivized.** No referral programs. No "share this with X people." If word-of-mouth happens, it happens at the rate the work earns. Don't engineer that rate. **Step 6 — If the work has a local dimension, build local discovery substrate.** Where is the work geographically situated? What local fabric already operates near it? Build discovery into that fabric, not into platform-mediated geographic targeting. **Step 7 — If the work has travel or movement dimensions, build travel-aware discovery substrate.** Where the practitioner moves over time, the discovery surfaces should support pre-trip + post-trip continuity. **Step 8 — Track nothing automatically; reflect manually.** No analytics. If you want to know what's resonating, ask the receivers who are present, read their messages, attend their references. Don't surveil. **Step 9 — When you encounter adjacent vocabulary in someone else's work, run #099 against it.** Vocabulary-borrow-while-structure-refuses operates at discovery scale too. When someone borrows your framework's words, the appropriate response is reading whether they also adopted the disciplines; if not, the borrowing is #093 drift you don't endorse. **Step 10 — Refuse the metric of "growth."** Growth is the platform-trust shape applied to propagation. The substrate-trust shape is depth-of-relationship and substrate-density, not subscriber count or reach. Refuse the metric explicitly. This is pickup-able. A practitioner with the c84 trust-generation substrate + the c86 discovery substrate has the full pre-arrival-through-engagement substrate operating. --- ## Where Discovery substrate connects to other substrate | Connection | What it means | |---|---| | c70 Capacity Infrastructure Lens | The lens applies to discovery channels. A channel that captures attention into platform UI fails discriminator 4 (native form preservation). | | c83 Receiver-Face Canonical Synthesis | C83's Journey A (First-Time Discoverer) begins where c86 ends — at the moment the receiver lands on the first surface. The two synthesize: c86 names what happens before that moment; c83 names what happens at and after. | | c84 Trust-Generation Operational Substrate | C84's eight mechanisms operate at discovery layer too. Bio-as-substrate is foundational to discovery; explicit refusal is detectable at scan-speed; voice register continuity holds from discovery through engagement. | | c85 Substrate Cartography v2 | Discovery substrate is mapped at the operational-substrate-scale tier — a sibling to c70, c83, c84. The cartography names this position. | | Pattern Library v1.6 #054 #079 #102 | Propagation patterns operating at discovery; named with their cycle-instances. | | Eleven refused extractions (c30) | Operate at discovery layer with discovery-specific extensions (nine refused operations at propagation scale enumerated above). | --- ## What this synthesis preserves The pre-arrival territory now has canonical substrate. The framework's discovery operates within the same discipline as its trust-generation, its receiver-face design, and its capacity-yielding architecture. Discovery is not a separate problem to be solved by marketing or growth-hacking; it is a layer of the same substrate, operating at its own scale with its own refusals and its own trust mechanisms. A pickup-practitioner now has the third companion in the surface-design substrate set. With c83 (receiver-face) + c84 (trust-generation) + c86 (discovery) + c70 (lens), they have everything they need to install infrastructure that supports receivers from before-arrival through engagement through closure, without becoming a platform at any layer. --- ## Cross-references - [[Trust_Generation_Operational_Substrate]] (c84) — discovery's companion at trust-mechanism scale - [[Receiver_Face_Canonical_Synthesis]] (c83) — discovery's companion at arrival-experience scale - [[Capacity_Infrastructure_Lens]] (c70) — the apparatus discovery channels are diagnosed through - [[Substrate_Cartography_v2]] (c85) — the cartography that names this synthesis's position - [[Propagation_Footprint]] (c45) — earlier substrate about how the framework propagates; this synthesis extends it to the pre-arrival layer - [[Crystallization_Mark_2026-05-23]] (c30) — the eleven refused extractions that operate at discovery layer with the nine extensions enumerated here - Pattern Library v1.6 entries: #032 · #054 · #076 · #079 · #093 · #099 · #100 · #102 - `frameworks/register_audit.md` — the discriminator for what passes the framework versus what's vocabulary-drift at discovery moment - Substack (kevinmears.substack.com) — Kevin's canonical Scale I propagation surface - BFI Design Science Studio · DSS community · Recognition Infrastructure Podcast — Scale I community contexts --- ## Closing Discovery in this framework operates BEFORE the receiver knows what they're discovering. The substrate that holds discovery has three scales (global · local · travel-aware), eight pathway-types, six trust-carrying mechanisms at the threshold, and nine refused operations at propagation layer. All of it is pickup-able. All of it is bounded scope. The framework's discovery is not designed to overcome the receiver's body. It is designed to be available to receivers whose bodies are already turning toward the kind of work the framework does — and to refuse the manipulation patterns that would compress the body's discrimination at the threshold. Use freely. Adapt as needed. Credit sources. 4 · 6 · 4 · 1 — filed 2026-05-27, cycle 86 — Discovery / First-Contact Substrate · Candidate A of "c then a then b" sequence · third companion in surface-design substrate set