Boundaries · Automation
Automation
Limits made operational.
A limit that requires continuous attention is not a limit; it is a chore. Automation is what lets a limit hold without consuming the person holding it.
The Boundaries vertex of the practice. Three surfaces. Each one carries a specific kind of structural limit, wired in deeply enough that the limit operates without Kevin having to enforce it conversation by conversation. Where Refusals names what the practice will not do, Automation is where the not-doing is built into the flow.
Read each surface as limit / makes possible, not feature / benefit. The limit is the load-bearing fact.
- Limit
- Wed/Thu calendar boundary. Body-discriminated capacity above the Cal.com floor. Explicit refusal patterns (no retainers, no validation work, no NDA-blocked engagements). Engagement and donation rails sealed from each other.
- Makes possible
- The engagement form holds without converting to consulting-dominant or product-shaped. Without the calendar boundary, substrate days dissolve. Without the explicit refusals, the tier converts to retainers. Without the rail separation, engagement and exchange couple back into transactional logic.
Open the consultation surface →
- Limit
- No donor list. No leaderboards. No acknowledgment ledger. No tying donations to specific services. No follow-up sequence after a donation.
- Makes possible
- Donation as gift, not transaction. The structural asymmetry — even where Venmo can't enforce it — protects both donor and practice from converting the relationship into ledger.
Open the donation surface →
- Limit
- Receiver-shaped intake. No required fields. No funnel. No qualifying questions. Three paths (gift offering, consultation, general) routed by the ask itself, not by a form's logic.
- Makes possible
- The ask stays in the receiver's shape. Kevin reads what was actually written, not what an intake form filtered. The receiver decides what's worth including.
Open the request surface →
Edges from here
- Library · Self-Knowledge edge
- The limits each surface carries derive from named substrate. The refusal patterns, the capacity ceiling, the consent defaults — all referenced from Library content.
- Public Face · Consent edge
- Every automation surface sits behind a consent gate on the Public Face. No automation fires without the receiver passing through a visible interface that names what they are agreeing to.
- Toolkits · Deployment edge
- Tools operate with built-in limits. The fit filter is itself a tool wired into this vertex — Toolkits and Automation share infrastructure where the limit lives in the tool.