# Consultations — Substrate

**Status:** substrate doc, v0.2, 2026-05-25. Revised to correct a structural drift. The original v0.1 treated consultations as a priced exchange tier with sliding-scale bands. The practice has since named one rail for material support (Venmo, donor-controlled, gift-form aligned). Consultations are not a payment tier; they are a deep engagement form. Booking is free; support runs separately. The v0.1 band specification is preserved at the end of this document as the upgrade-path proposal if the practice ever migrates to a fiscal-sponsor-mediated rail.

## What this is

A structured engagement form for receivers building their own infrastructure who want framework-applied attention on a specific situation. Three shapes. Capacity capped. Bookings on Wednesdays and Thursdays only.

Consultations are not a payment tier. The practice has one rail for material support — the [donation rail](../automation/donate.html), Venmo-based, donor-controlled. Booking a consultation costs nothing on the calendar. Receivers who want to support the practice do so on the donation rail, separately, at whatever amount and cadence feels right to them.

The structural distinction between consultations and [gift offerings](../offerings.html) is about **depth and substrate-application**, not about pricing. Gift offerings are time-bounded acts of capacity Kevin gives in response to a specific request. Consultations are deeper engagements where the framework is applied to the receiver's own infrastructure across one session, three sessions, or a written reading.

## Role in the architecture

Consultations are where the framework leaves the substrate library and lands inside a specific practitioner's situation. The Library carries the framework as text; the Toolkits make it operable in receivers' hands; consultations are the form where Kevin's attention applies the framework to a specific case the receiver brings.

They exist as their own engagement form because:

- Some receivers are building their own personal-scale infrastructure and need framework-applied attention at a depth that gift-form offerings cannot sustainably hold across multiple sessions.
- Naming this form explicitly is what protects the [gift menu](../offerings.html) from quiet drift. An unnamed deep-engagement form means every gift interaction is shadowed by "could this go further?" Naming consultations closes that ambiguity.
- The form gives Kevin a containable surface for the longer work, with explicit capacity limits, so the practice doesn't quietly convert into a consulting-dominant shape.

Consultations are not one of the four facets of OSG (Library / Toolkits / Public Face / Automation). They are a derivative surface that applies the substrate; they do not produce it.

## What is offered

Each engagement is **specific and emergent.** Not pre-structured into N-session arcs. Every receiver starts with an initial; follow-ups happen if the work wants follow-ups; the engagement extends as long as it should and closes when it's done.

Two event types:

### Initial consultation — 30 minutes
The first contact. The receiver brings a specific situation (organizational, personal, project-scale, a body of their own work). Kevin reads it through the Recognition Infrastructure framework; together they name what would be useful next. Most engagements complete here — the structural read is what was needed. Some engagements open into follow-up sessions; some identify a body of work for a written reading; some surface that the consultation tier isn't the fit and route the receiver to substrate.

### Follow-up session — 1 hour
For engagements that continue past the initial. Each follow-up is its own complete unit and emerges from what the prior session opened. The number of follow-ups is determined by the work, not by a pre-committed package. Some engagements have one follow-up; some have several; some have none.

### Written substrate-level reading
A receiver bringing a body of their own work (manuscript, framework, governance model, site plan) starts with the 30-minute initial to scope the reading and confirm fit. Kevin then reads the work through the lens and returns a written structural read, 4–8 pages, naming what holds, what drifts, what's extraction-patterned, what's load-bearing. One optional follow-up session after delivery for clarifying exchange.

### The 2-hour calendar block per engagement
Every engagement holds a 2-hour block on the calendar — the session itself plus built-in processing time. The hour after a 1-hour follow-up, the 90 minutes after a 30-min initial, is where Kevin metabolizes the session: transcription review, pattern extraction, the substrate work that lets the engagement deposit back to the commons per the commons-work consent. The processing time is part of the engagement, not unpaid overhead added afterward.

## What is NOT offered

Equal weight to this section. The negative space is a structural fact, not a disclaimer.

- **No deliverables for hire.** Kevin does not write decks, reports, strategy docs, or site copy for clients.
- **No implementation.** Kevin does not build the receiver's infrastructure for them. The framework only works when the practitioner does the building.
- **No "fix my team / fix my org" engagements.** The framework is for one practitioner with a body that can discriminate. Organizational engagements with no named individual carrying the somatic work are refused.
- **No retainers, no monthly contracts, no advisory seats.** Every engagement closes.
- **No productized methodology.** The framework is not a sellable system. Receivers who want a turnkey method are routed to other practitioners.
- **No crisis intervention.** Acute organizational or personal crisis is a Boundaries vertex problem, not a consultation engagement. Refused with a referral.
- **No validation of pre-made decisions.** Receivers who want Kevin to ratify a choice they have already made are refused. The framework reads structure; it does not co-sign.
- **No personal branding work, no scaling consulting, no growth strategy.** Categorically outside the frame.
- **No therapy. No coaching in the conventional sense.** Kevin is not a therapist and does not perform therapeutic work.
- **No NDAs that block Kevin from learning from the engagement.** Confidentiality of specifics is honored; the right to integrate generalized pattern recognition into the public substrate is non-negotiable.

## Sustaining the practice

Booking a consultation costs nothing on the calendar. The practice is sustained through donations on a separate rail — the [donation rail](../automation/donate.html), Venmo-based, sliding scale, donor-controlled.

The two channels are kept structurally separate:

- **Booking does not require donation.** Receivers who never donate are not second-class. Receivers booking back-to-back arcs are not under any implicit obligation to give.
- **Donation does not buy access.** Donors do not get priority booking, name recognition, or any transactional benefit. The donor discipline Kevin commits to on the donate page applies inside the consultation tier as well: donor identity does not shape engagement.
- **No mention of donations inside the engagement.** Sessions don't end with "if this was useful, consider supporting the practice." That would re-couple the channels. The donation rail is named publicly on the site; receivers find it if they want it.

This structural separation reads as anomalous in the conventional model, where engagement and payment are tightly coupled. The uncoupling is the point — it's what keeps the gift form intact across the deep-engagement surface.

## Commons-work consent

This is the load-bearing structural arrangement of the consultation tier. Receivers know this before they engage; it is not a clause in fine print.

**The arrangement:**

- The specifics of your situation stay with you. Names, places, the particular shape of your bind — none of that leaves the room.
- General patterns the framework reads in your situation may appear, generalized and anonymized, in Kevin's published work (essays, kit cells, framework revisions, transmissions).
- The redaction discipline is built into the work, not added at the end. If a pattern is so specific that anonymization can't make it unrecognizable, it doesn't get used.
- You can ask Kevin not to use a specific pattern. He'll honor it. He won't ask why.
- You can also offer the inverse — explicit permission to use your name, to credit you, to link to your work. The default is anonymity; named credit is an opt-in move you make.

**Why it's shaped this way:** the framework only stays alive if it keeps metabolizing real situations. A consultant who hoards what they learn from clients accumulates private expertise to charge more for. Kevin is not in that frame. The patterns belong to the field, not to him. You are not paying for proprietary access; you are participating in commons-work whose outputs flow back to public substrate that other practitioners — including you — can use freely.

If this arrangement doesn't feel right in your body, this is not the work for you. That is not a failure on either side; it is the fit filter doing its job.

## Quadrant (Wheel of Consent)

Engagements 1 and 2 sit primarily in **Serving** — Kevin doing, receiver benefiting. Engagement 3 (written substrate-level reading) is the same.

A small number of engagements may run in **Accepting** — Kevin learning from a peer-level practitioner whose work informs the framework. These are named explicitly as such.

The shadow form to watch for is **Allowing**: Kevin permitting the receiver to consume his attention in a shape that doesn't serve them but they wanted. Caught by the fit gate.

The **Taking** shadow — Kevin extracting from receivers — is structurally harder to fall into now that booking is free. In v0.1 of this doc, Taking was a live concern because price could pressure a receiver to over-extend. With no calendar-attached price, that pressure surface is gone. Taking can still operate if Kevin lets a poorly-fitting engagement run past where the body says stop; the fit filter and post-booking decline patterns protect against this.

## Capacity

Capacity is body-discriminated. There is no published fixed concurrent-engagement ceiling — different weeks hold different loads depending on what the body has room for and what substrate work is in process.

The structural floor is set by the calendar math. Wed/Thu only, 2-hour block per engagement, ~4–6 hours of available calendar per day → maximum ~6 engagements per week. Cal.com's per-event-type frequency limits hold this floor (e.g., max new initials per week, max total bookings per week).

Above the floor, Kevin's body discriminates. Some weeks two engagements; some weeks four; some weeks zero. The number reflects current capacity, not a published commitment.

When intake is closed, the consultation event types are paused in Cal.com. When intake reopens, they unpause. The visible state lives on [Current State](../current.html); the operating decision lives in the body.

## Calendar boundary

Bookings open **Wednesday and Thursday only**. Five days a week stay for substrate work, the body, family, the rest of the practice. The two-day calendar boundary is itself a Boundaries-vertex move — limits made operational at the calendar layer.

Specific hours within Wed/Thu, the buffer between sessions, and timezone are Kevin's to set in Cal.com per current capacity.

## Fit criteria — what makes the work fit

A receiver is a fit when:

1. **They are building their own infrastructure.** Not asking Kevin to build theirs.
2. **They have somatic ground.** A body, a practice, a context the framework can rest on. The framework is portable; it does not propagate by being carried — it propagates by the new practitioner having their own ground.
3. **They have engaged with the substrate.** Read the manuscript, run the kit's audit, sat with at least one of the essays. The conversation starts at depth, not at "tell me about your work."
4. **The commons-work arrangement lands cleanly in their body.** They understand and consent that patterns from the engagement may appear, generalized and anonymized, in public substrate. They are not seeking proprietary, exclusive, or NDA-protected work.
5. **The question is specific.** A named situation, a named decision, a named body of work to read. Not "I'd love to pick your brain."
6. **They can name what they want at the end.** "A structural read I can act on." "A map of my own build." "A written diagnosis of where my framework drifts." If they can't name an outcome, they're not ready for a consultation — they're ready for the kit or the manuscript.

## Fit criteria — what makes the work NOT fit

Refused, with referral where possible:

1. **Validation-seeking.** Receiver wants Kevin to ratify a decision. Refused; the framework reads structure, it does not co-sign.
2. **Performative expertise.** Receiver wants Kevin to perform the role of consultant as deliverable theater. Refused.
3. **Org-without-practitioner.** Engagement framed as "our organization needs this" with no named individual carrying the somatic work. Refused.
4. **Productization request.** Receiver wants the framework licensed, packaged, or turned into a curriculum they will sell. Refused; self-license is "use freely, adapt as needed" — they don't need a consultation for that.
5. **Crisis-driven urgency.** Acute distress that needs immediate intervention. Refused with a referral; consultation tier is not a crisis service.
6. **Mismatched substrate.** Receiver's frame is fundamentally extractive (growth, scaling, ROI on the engagement). Refused; they would not metabolize the work.
7. **Repeat-receiver looking to convert to retainer.** Refused; every engagement closes. Repeat engagements are possible but each one is its own closed scope.
8. **NDA-bound work.** Refused; the commons-work arrangement is non-negotiable.

## Refusal table

Consultation-tier-specific extraction patterns this engagement form refuses. Extends the `_PERSONAL_OS.md` refusal table.

| Pattern | What it looks like | Refusal |
|---|---|---|
| Retainer drift | "Could we just do an ongoing arrangement?" | Every engagement closes. New engagement = new scope. |
| Scope creep mid-engagement | "While we're at it, could you also…" | Named scope holds. New asks become a new engagement. |
| Recorded-and-resold | Receiver wants to record the session for resale, course content, or training material | Refused. The engagement is for the receiver, not for their downstream content product. |
| Endorsement-as-payment | "I'll tweet about you / refer five people" — framed as something Kevin should account for | The engagement is free regardless. Endorsement is neither payment nor required. Referrals are welcome and structurally uncoupled from anything. |
| Gatekeeping the framework | "I want exclusive access to the methodology" | Refused. The substrate is self-licensed and public. Nothing about the consultation tier is exclusive. |
| Therapy substitution | Receiver uses the engagement as covert therapy | Named gently; referred to actual therapy. |
| Donation-as-priority-pass | "I'll give a large donation if you can fit me in this week" | Refused. The donation rail and the calendar are sealed from each other. Donations don't move the queue. |
| Quid-pro-quo framing post-session | "Thanks for the session; what should I donate?" | Named structurally. The donation rail is autonomous; donor-controlled; not coupled to engagement. Kevin doesn't suggest amounts. |

## How this protects the gift tier and the donation rail

- **Gift menu stays clean.** A gift offering does not lead to a consultation offer. A consultation does not start as a gift offering "upgraded."
- **Donation rail stays clean.** Donations don't buy consultation access. Consultation receivers don't get name recognition or preferential access through donations.
- **Three surfaces, three doors.** Receivers enter each through its own surface — Offerings, Consultations, Donate — and the surfaces don't bleed into each other.
- **No bundling.** A consultation does not include "and you'll also get…" access to gift offerings, kit content, or anything else. The consultation is the consultation. Everything else is free and separately accessible.

## Operational specifics

What the booking infrastructure must satisfy. Updated for the Cal.com (free booking, no payment integration) rail.

1. **The fit filter is recommended, not required.** Receivers walking the [fit filter](../toolkits/fit-filter.html) before booking is the preferred path. Direct booking is allowed; Kevin declines clean post-booking when signal says not-fit.
2. **Booking takes no money.** Cal.com handles the slot only. No Stripe integration. No price visible anywhere on the calendar.
3. **No platform that requires Kevin to perform marketing inside it.** Cal.com hosted is acceptable (open-source, escape hatch, minimal platform branding). Platforms with aggressive branding, productized intake flows, or marketplace conversion patterns (Calendly's "powered by," Patreon-style tiers, Intro/Clarity.fm) are refused.
4. **The receiver knows what they will get and what they will not get before booking.** All "not offered" content visible at the consultation page; booking page links back to it.
5. **Cancellation policy is generous and named.** 48-hour cancellation is no-friction; under 48 hours is honored with a clean re-schedule unless somatic ground says otherwise. Since no money changes hands, refund logic doesn't apply.
6. **Capacity floored by Cal.com, body-discriminated above the floor.** Per-event-type frequency limits hold the operational maximum (e.g., max new initials per week, max total bookings per week). When body says full earlier than the floor, the event types pause manually.
7. **Wed/Thu only on the calendar.** Set as recurring availability; substrate days stay protected.
8. **2-hour calendar block per engagement.** Includes the session itself and the processing time after — transcription review and pattern extraction. The processing is part of the engagement, not unpaid overhead.

## Failure modes

- **Gift menu and consultation page link to each other directly.** Structural error. They must be reachable from the site but not from each other (both reachable from the Index and Refusals; not from each other's surfaces).
- **The fit filter becomes ornamental.** If everyone who walks the filter gets FIT, the filter is doing no work. Periodic check: the not-tier and not-offered outcomes should be visibly non-zero.
- **Calendar fills past body capacity.** The Cal.com floor sets the upper bound; the body's signal lives below it. If the body says full and the calendar still has open slots, the discipline is to pause the event types regardless of what the calendar says is possible.
- **Receiver retention without engagement closure.** Receivers who keep coming back without each engagement closing cleanly — this is retainer drift even if formally each was a "new engagement." Caught by the same-receiver-three-times check.
- **Implicit donation pressure leaks into sessions.** If Kevin finds himself mentioning the donation rail during or after sessions, the channels are coupling. Stop.
- **Donor-receivers get implicit preference.** If a frequent donor books and Kevin notices himself softening fit criteria, the donor discipline is breaking. Restructure.
- **Substrate-production time shrinks below threshold.** If consultations consistently leave less than three days/week for substrate work (writing, library curation, transmission engine runs), the tier is wrong-sized.

## Voice notes for the page

- Third person about Kevin, consistent with the rest of OSG.
- The "not offered" section gets equal weight to the "offered" section visually. Not folded into accordions, not below the fold.
- No testimonials. No social proof. No "trusted by X organizations."
- The "sustaining the practice" section makes the rail separation explicit. No "if this was useful, please consider…" framing.
- Lineage line at the close: this work rests on the Recognition Infrastructure framework, self-licensed and public.

## Open questions

- Whether engagement type 3 (written substrate-level reading) should be the lead offering — it is the most asynchronous and least taxing on Kevin's calendar, but it requires the receiver to have a body of work to send. Currently lead with #1; revisit if intake reveals #3 is more sustainable.
- Whether Wed/Thu specific hours should be morning-only, full-day, or split. Set in Cal.com per current capacity.
- Whether to name the practitioners Kevin refers out to (when refusing for fit reasons). Adds value to the refused receiver, but creates a referral network Kevin then has to maintain. Currently a one-line "Kevin maintains a short list of practitioners for X, Y, Z and can share by email" approach.
- Whether the consultation tier should ever migrate to a fiscal-sponsor-mediated rail that includes pricing (per archived v0.1 spec below). Trigger conditions for that migration: if the Venmo donation rail does not sustainably cover the practice, and if Kevin reaches a body-yes on the structural shift. Default: don't migrate; the gift-form alignment is the load-bearing claim of the practice.

## What this document is not

- Not a marketing document. This is internal substrate. It tells the page what to be.
- Not the rail. Scheduling and intake mechanics live in the Cal.com configuration; only the structural constraints on that configuration live here.
- Not the final word on engagement form. New engagement shapes may surface from operating experience; this doc updates when they do.

---

## Archived — the v0.1 sliding-scale band specification

The original v0.1 of this doc specified consultations as a priced exchange tier with named sliding-scale bands. That specification was archived 2026-05-25 when the practice consolidated all material support on the Venmo donation rail.

This section is preserved as the upgrade-path proposal **if and only if** the practice ever migrates to a fiscal-sponsor-mediated rail (e.g., Open Collective or local 501(c)(3)) that structurally supports price-coupled booking. Until that migration is named explicitly, these bands are not in use.

| Engagement | Band | Floor | Notes |
|---|---|---|---|
| Framework application (90 min) | $150 – $600 | $150 | Floor was real; not symbolic. |
| Practitioner-to-practitioner (3 sessions) | $600 – $2,400 | $600 | Six-to-eight week arc. Paid in full at the first session. |
| Substrate-level reading (written) | $400 – $1,600 | $400 | Scope set at intake. |

**Original structural rationale for the band shape (archived):**

- Floors non-zero to keep the tier distinct from gift-tier work.
- Ceilings to prevent guilt-payment drift.
- Receiver self-selects within the band; Kevin doesn't negotiate.
- No discounts, no sliding below the floor, no scholarships.

**Why these were archived:** the priced-tier model couples engagement to payment. The Venmo decision named one rail for the whole practice's material support, donor-controlled, structurally separate from any engagement surface. Re-introducing per-engagement pricing would reproduce the extraction-shape that the Refusals page names.

The archived band is preserved here as substrate — work that informed the current model — not as future intent unless explicitly re-decided.

---

*Substrate references: [`_PERSONAL_OS.md`](../../_PERSONAL_OS.md) (refusal table, four-facet map) · [`donate.html`](../automation/donate.html) (donation rail substrate) · [`offerings.html`](../offerings.html) (gift tier substrate) · [`_archived/donation_rail_full_spec.md`](_archived/donation_rail_full_spec.md) (donation rail fiscal-sponsor upgrade-path spec).*