Availability.
Context
This is the first pattern of the Body and Presence layer, and it opens a territory that is both deeply practical and deeply philosophical. Availability is not simply about being reachable. It is about the quality and scope of presence that one person offers another within a conscious dynamic — and that question reaches all the way back to Why Would You and The Nature of Your Relationship. How available you are is determined by who you are to each other.
This pattern builds directly on Structured Agreements and Standing Orders — availability must be precisely defined to function — and on the consent frameworks of Daily Consent Basics and Consent Theory and Philosophy.
Core Dynamic
Availability exists on a spectrum as wide as the spectrum of conscious dynamics itself. At one end: the sub who is fully present in a scene once a month, whose availability is bounded and explicit. At the other: the sub who has chosen to be owned completely — without individuality, without separate rhythm, available to the dominant at any moment in any context. Both are legitimate expressions of conscious power exchange. Both require the same thing: absolute clarity about what has been agreed to, and genuine consent underneath that agreement.
The practical infrastructure of availability is more specific than most dynamics acknowledge. A check-in message in the morning. A check-out message at the end of the day. Notification when the sub is temporarily unreachable — for an appointment that was known and approved in advance, for a meeting with vanilla friends, for a context where the dynamic is not visible. How available is the sub by phone when they are with others? What protocol applies when they cannot respond immediately? These are not bureaucratic questions. They are the specific agreements that give the dominant genuine presence in the sub's day, and the sub a clear structure within which to move.
Rubel's protocol work is precise on this: the dominant who has not specified what availability means in practice has not yet built a household. The sub who does not know exactly what is expected — when to check in, how to communicate absence, what the protocol is in each context — cannot be consistently available, because there is no clear form to be available within. Clarity here is not constraint. It is the structure that makes genuine availability possible.
Betty Martin's Wheel of Consent is directly relevant here. The question underlying all availability is: who is this for, and is it genuinely given? The sub who is available because they want to be — whose availability comes from genuine orientation toward the dynamic — is in a very different place from the sub who is available because they are afraid of what happens when they are not. Availability that is driven by fear or obligation is not surrender. It is compliance, and compliance at this level of totality eventually produces either resentment or disappearance. The Wheel asks: is this given, or is it merely allowed? Is this wanted, or only tolerated?
Dan and Dawn Williams describe availability in a 24/7 M/s dynamic as one of the most consequential agreements the relationship makes — because it shapes every hour of every day. They point toward the same conclusion as the consent frameworks: availability must be designed with enough care that both people know exactly what it means in practice, and reviewed regularly enough that it remains genuinely alive rather than becoming a form that has outlasted the feeling behind it.
Possible Pathways
Define availability precisely. Not in general terms but in specific ones. When does the sub check in, and how? What protocol applies when they are with others? What does temporarily unreachable mean, and what is expected around it? The more specifically this is designed, the more clearly it can be lived.
Ask honestly, with Betty Martin's question as a guide: is this availability genuinely given, or is it merely allowed? Is it an expression of actual orientation toward the dynamic, or a performance of availability driven by something other than genuine desire to be present? The answer matters — not as judgment but as information about the health of the consent underneath the agreement.
Build the review into the structure. The Periodic Review is the place to examine whether the availability that was agreed is still right — whether it fits the people inside it or whether it has become a form that neither person is actually living fully. A dynamic that can review and adjust its availability agreements is a dynamic that can sustain them over time.
Discussion
The most demanding forms of availability — full ownership, 24/7 total power exchange, the sub who has chosen to surrender individuality entirely — are also the forms that require the most careful consent architecture underneath them. The sub who is always available has not simply agreed to a set of rules. They have agreed to a way of being in the world. That agreement must be built on genuine self-knowledge, honest negotiation, and a dominant who has genuinely earned and can genuinely carry that level of trust and responsibility.
Availability and the surrounding world
Most dynamics exist in a world that does not know what they are. The sub who is available by phone while out with vanilla friends is navigating two contexts simultaneously — the protocol of the dynamic and the norms of the surrounding world. This requires clarity about what the protocol actually asks in that specific context, and the Protocol Gradient is the instrument for navigating it. The check-in that goes unnoticed by others, the response that is given discreetly, the notification sent before entering a context where the dynamic is not visible — these are availability lived at low protocol, and they require as much design as the high-protocol moments.
When availability breaks down
The dynamic cannot come to rest — cannot grow, cannot deepen — when availability is consistently unreliable. The missed check-in, the notification not sent, the protocol around presence not followed: these create a background noise of uncertainty that prevents both people from settling into what the dynamic can be. Consistency, Punctuality, and Honesty are the conditions of reliable availability. When they are present, the dynamic has a ground to stand on. When they are absent, availability becomes something that is claimed but not actually given.
Dr. Bob Rubel, ed., Protocols: A Variety of Views (Nazca Plains, 2008). Dan & Dawn Williams, Living M/s. Betty Martin, The Art of Receiving and Giving: The Wheel of Consent (2021).
Connected Patterns
This pattern reaches back to Why Would You and The Nature of Your Relationship — how available you are is determined by who you are to each other. It builds on Structured Agreements and Standing Orders, which give availability its specific form, and on Daily Consent Basics and Consent Theory and Philosophy, which are the ethical ground it stands on. It connects to Protocol Gradient — availability looks different in different registers — and to Surrender, of which genuine availability is one of the most sustained expressions. It requires Consistency, Punctuality, and Honesty as its conditions. It connects to Accessibility, which addresses a related but distinct dimension of presence, and leads into Attending — availability is the precondition, attending is what happens within it. And it loops to The Periodic Review, where the availability agreements are examined and renewed.