The lines I hold, and why holding them keeps the rest honest.
Held, not hostile — a line I keep on myself first.
Saying no is cheap. Anybody can say no. The honest part is naming the whole cost of a yes before you give it — so here's where I draw my lines, and the real reason behind each one. None of this is me being difficult. It's the stuff that, if I let it slide, turns good work into a trap.
If any of this reads like it's pointed at you, it isn't. These are lines I hold on myself first.
Every "no" on this page comes with an "instead." A no without an instead is just a wall.
About the work
I don't quietly run my hours past empty. I hold a half-day floor — about a half-day of real work a day. That's not me being lazy. A one-man operation doesn't get ended by doing too little; it gets ended by holding one more worry than I can keep track of, and the one I drop is the one that bites. So I keep the load to what I can carry on a bad day, not a good one.
I won't make the hardest thing pay the rent. The slow, ambitious build is a big swing — I don't bet the month on it. The fast, easy work pays the bills and buys me the time to build up to the bigger thing. If you need something simple and quick, that's the bread-and-butter, and I'm glad to do it.
I won't pretend the selling is free. If I'm setting up at a gathering, talking to everyone, handling money, cleaning up — that's a day of work on top of the building. I either price it in or keep it small. I won't quote you like the labor vanishes once the table's done.
I won't leave a hole. When I help someone, I try to give the kind of help that doesn't need me again — a written how-to, a finished jig, a setup that runs on its own. I build the thing that does the job first, then step back. I don't walk off and leave you stranded, and I don't make myself into another unpaid phone call you have to keep dialing.
About money and favors
I keep paid and free in separate lanes — no barter. One lane: you pay me cash for trade work, clean and clear. Other lane: I give something away free, no strings, take what's useful and leave the rest. I won't let them blur into "you owe me one." That fuzzy middle is exactly where neighbors fall out. Free is free. Paid is paid. Keeping them apart is what keeps both of them clean.
I name the whole cost up front. The job that pays $200 but eats two days of callbacks. The quick favor that becomes my problem forever. Scope creep. A clean deal says what it'll actually cost before anybody shakes on it — and I won't pull that trick on you either.
I don't take a cut of money that isn't mine. If I connect two people and money moves between them, it moves between them. I'm not a middleman skimming the deal.
About how I treat people
I don't score people. No star ratings, no reviews, no "trusted" badges, no tiers. If you want to know whether I'm worth hiring, look at the work and talk to the people I've done it for. They stand on their own. I'm not running a leaderboard.
I won't work a long day without a shared meal. If a job runs past about four hours, eating together is part of the deal, not a nicety. You don't separate the body doing the work from the body that needs feeding. That's just how I work.
I won't be the guy who can never say no. Holding my line isn't stinginess — it's the only thing that keeps me from burning out doing free work for everybody until there's nothing left to give. Low burn is what makes my "no" affordable and my "yes" real.
About this site
No tracking, no metrics, no funnel. This site doesn't watch how you found it or how you move around. No analytics, no pixel. No mailing list to harvest. No "act now," no countdown, no urgency games. If you showed up, good — take your time.
No platform owns this. It's my own domain, plain files, nothing optimized to keep you scrolling. Word-of-mouth is unpaid and uncounted. The site sits quiet until you come look at it.
This list isn't finished. When I catch a line I should've been holding, I add it.
That's the whole thing in plain terms. What follows is the same thing in structural language, for the reader who wants the geometry.
The same lines, as structure
The refusals above aren't a temperament. They cluster. Every line on this page is one of four shadow operations — each one the failure form of one of the four capacities the practice runs on: Differentiation (each element knows what it is), Connection (value flows between distinct elements), Boundaries (limits stated as information), Architecture (what works gets built to outlast its builders). Each capacity, dropped or inverted, casts a predictable shadow. The vocabulary from here down is exact on purpose; the glossary is load-bearing.
The patterns operate at four scales. The content-level refusals — the plain-terms list above — cluster as the four anti-extraction axes. Three further layers (system, protocol, propagation) extend the same refusals to the scales of architecture, fabric, and discovery. Retrofitting refusals after the fact does not work; extraction logic baked into defaults stays operative no matter what surface language is applied. So they're refused at the design stage, and each one is paired with what happens instead — a refusal held without its alternative is a wall, not a boundary.
The geometry of the page: four capacities, four shadows. Every refusal below lives in one of the shadows.
Content· 11what the practice itself refuses — the four tables below, colored by shadow
System· 8what an architecture claiming this vocabulary cannot also do
Protocol· 9the Gift Circle spec — holds for any adaptation of it
Propagation· 9what the work refuses to do to be found
Thirty-seven named refusals, four scales — the map of everything below.
Capture — shadow of Connection
Taking from receivers without consent or awareness; converting circulating flow into one-way capture.
Pattern
What it looks like
What happens instead
Attention extraction
Tools optimized to hold the eye; engagement metrics; notifications
Local-first tools; plain files; no analytics anywhere on the site
Data extraction
Cloud tools that learn from inputs to improve their own value
Local-first; open formats; no telemetry
Identity extraction
Platforms that own handle, audience, social graph
Own domain; references on own site; no platform-owned identity
Aggregation — shadow of Differentiation
Collapsing individual distinctness into abstract numerical metrics; replacing recognition with score.
Pattern
What it looks like
What happens instead
Audience-as-number
Followers, engagement, reach as success signal
No audience metrics surface; references are named witness statements
Reputation systems
Star ratings, averages, vouching scores
References stand individually; no aggregation, no scoring
Relational extraction
Relationships turned into marketing channels
No conversion funnel; no list-building; no relationship-as-pipeline
Scaling — shadow of Architecture
Treating personal scale as preliminary or insufficient; collapsing depth into reach.
Pattern
What it looks like
What happens instead
Scaling as virtue
Personal scale treated as preliminary to "real" scale
Personal scale named as the correct unit; the gift propagates through utility, not growth
Productization of gift
Converting circulating gift into priced commodity
Gift and exchange kept structurally distinct; no price on gift work
Coherence extraction
Outsourcing sense-making to external systems
The library is local; the framework is self-applied; AI is partner, not author
Performance — shadow of Boundaries
Substituting visible form for actual structural function; performing the boundary rather than holding it.
Pattern
What it looks like
What happens instead
Container-holder extraction
The person holding the field becomes the absorber of system dysregulation
Named directly in the practice's governance; the half-day floor and the mesh's second set of eyes are the working answer
Safety-as-highest-value
Expanding justification for control framed as protection
Resilience over safety; limits stated as information, not enforced as management
Why the four-axis form
The patterns are not a random list of extractions — they cluster as the four shadow operations of the four capacities. Each capacity predicts its own shadow:
Connection (value flows between distinct elements) shadows as Capture — flow becomes one-way taking.
Differentiation (each element knows what it is) shadows as Aggregation — distinctness collapses into score.
Architecture (what works gets built into infrastructure that outlasts the builders) shadows as Scaling — persistence becomes growth, depth becomes reach.
Boundaries (limits stated as information) shadows as Performance — structural form replaced by visible performance of form.
System-level refusals
When a platform or system claims this framework's vocabulary, these are the architectural patterns the framework refuses. The presence of any one is the discrimination — what reads as "alignment" at the language layer can be inversion at the structural layer.
Vertex substitution by generic categories. Replacing the four-capacity structure with generic project-management categories (Vision/Process/People/Tools). If the four can be renamed without losing the structure, the framework was being used as decoration.
Reading a person's substrate as empty workspace. A system that reports "no goals tracked" because the receiver's actual practice doesn't fit its schema. The emptiness-report is the platform looking at its own database, not at the person.
Declaring completion targets at start. Naming a "100% target" at the moment a practice begins. Closes the form before structure can crystallize around it.
Marks landing into platform state, not into substrate. Status emojis, progress bars, in-progress labels. Each marking action updates platform state without depositing anything the next action rests on. Movement without compounding.
Recursive subtasking without scale-crossing. Spawning sub-tasks that are verbal restatements of their parent — redundancy at the same scale rather than new substrate at a new scale.
All four shadow operations operating simultaneously. A system embodying Capture + Aggregation + Scaling + Performance at once is the unmixed extraction-permission shape. Maximal negative instance.
Container-holder dependence as designed shape. Architecture that requires continuous engagement to maintain visible state. The dependence is the design intent, not an accident.
Cycles getting more expensive over time. Each interaction adds entities that need maintenance; turn N+1 is harder than turn N because per-turn capacity is inversely related to accumulated surface area.
Protocol-level refusals
Refusals operating on specific fabric pieces — the Gift Circle and any practitioner's adaptation of it. These are protocol-layer; they hold across any instance that uses this framework's village-coordination architecture. The Gift Circle as built enacts every one of them, and any polish pass on that page must keep it that way.
No profiles. The unit of trust is the record, not the user. People post asks, offers, references — not selves.
No reputation systems. No ratings, no reviews, no "trusted" badges, no aggregated scores.
No verification tiers. No "verified host," no premium status, no completed-onboarding stratification.
No matching-as-recommendation. Readers do their own matching. No algorithmic suggestion. No "you might like."
No reputation-as-data. Claim history, engagement history, response history — not aggregated or displayed publicly.
No platform-take. If money moves between two people meeting through the fabric, it moves off-platform. The infrastructure does not process payments.
No engagement optimization. No notifications designed to bring you back. No streaks. No "you have 3 unread asks." The infrastructure is silent unless you check it.
No global aggregation. Each radius is local. The protocol does not aggregate across radii into a national or global view. Practitioners can talk; their infrastructures don't merge.
No labor without nourishment. Treating the body doing work as separable from the body that needs feeding. In-person engagements past the threshold (this instance: four hours) include a shared meal as structural requirement, not optional benefit. Co-regulation is part of the architecture, not its decoration.
Propagation-level refusals
How the work reaches anyone in the first place — what it refuses to do to be found.
No engagement-optimization in propagation. No A/B-tested headlines. No urgency framing. No scarcity manipulation. No countdown timers. Discovery is whatever it is at its own pace.
No tracking analytics. No Google Analytics. No pixel. No Mixpanel. The site does not measure how receivers discover it, how they move, how they bounce.
No referral incentives. No "invite 3 friends, get X." No referral tracking. No affiliate programs. Word-of-mouth is unincentivized.
No SEO games. No keyword stuffing. No backlink schemes. The work appears in search for what it actually says, in the words it actually uses.
No paid amplification. No paid ads. No boosted posts. No sponsored content. Propagation is unpaid.
No platform optimization. The Substack publishes articles; it is not optimized for the platform's amplification mechanics.
No platform-mediated discovery as primary. Some platform presence may exist; none of it is the primary discovery surface. The primary surface is the receiver's own attention finding the work.
No creator-economy enrollment. No paid tiers. No Patreon. No gated content. The work is freely available; subscription is just notification, not access.
No urgency at the discovery threshold. The receiver who arrives without prior knowledge is given time. No "act now." The work does not compress the body's discrimination time.
Why the four-layer architecture
Each layer extends the refusals to a different scale of operation. The content-level refusals describe what the practice itself refuses to do. The system-level refusals describe what an architecture using this framework's vocabulary cannot also do. The protocol-level refusals operate on specific fabric pieces. The propagation-level refusals operate on how the work reaches anyone in the first place.
Together: thirty-seven named refusals operating at four scales. Each is what makes the design what it is by what it refuses to be. What I won't do is part of what I am — same as what I will.
This list is not exhaustive. New patterns get added when the body catches one not yet here.
