Intimacy as a System: Inputs, Constraints, and Experiments

You can't negotiate desire like a contract.

You've built an operating model (Post 14). Roles are clear, load is balanced, state is managed. But one area operates by different rules: intimacy. You can't demand it into existence. The demand itself blocks the state required.

Think of it like trying to demand sleep. The harder you try, the more elusive it becomes. Sleep is a system output that emerges when conditions are right. Intimacy works the same way.

This post treats intimacy as a system: inputs, conditions, outputs. If you want the output, you engineer the inputs.

Frame: Intimacy is a system output. It's not owed, and it can't be negotiated like a contract. But it can be designed for. The inputs are: state, trust, load, novelty, time/space. Engineer those, and the output becomes more likely.

The Intimacy System Model

Inputs
Conditions

The inputs create conditions. Conditions create possibility—not guarantee.

Output

Erotic connection. Variable, not owed. Emerges when conditions are sufficient.

Constraint Mapping

Before designing experiments, map the constraints honestly. What's actually blocking the system?

Intimacy Constraint Audit

Constraint Type Current Status Design Around?
Fatigue/energy
Privacy (kids, housemates, etc.)
Stress cycles (work, family)
Medications affecting libido
Body image concerns
Resentment debt
Mismatched desire types

Key insight: Design around constraints rather than pretending they don't exist. If privacy is the constraint, solve for privacy. If fatigue is the constraint, solve for fatigue.

Experiment Design

Use the agreement experiment framework from Post 8. Choose one experiment, run it for 14 days, measure, adjust.

Intimacy Experiments Menu

Option A: Date Night with No-Pressure Rule

Option B: Sensual Touch Ladder

Option C: Novelty Injection

My Chosen Experiment

Experiment: _______________

Duration: _______________

Metrics (2 max): _______________

Review date: _______________

Metrics

Pick 2 maximum. The goal is learning, not surveillance.

Track in your weekly sync. A dropping pressure rating with stable or rising closeness rating = system improvement.

System Failure Modes

Common intimacy system failures:
Example Experiment Output

Constraint identified: Both exhausted by evening; privacy limited (kids)

Experiment: Monthly overnight with no kids + weekly morning time (kids watching TV)

Rule: No-pressure protocol on weekly mornings—closeness only, no expectation

Metrics: Closeness rating, pressure rating

14-day result: Closeness 6→7, Pressure 7→4. Continue experiment.

Guardrail:

If there's coercion, intimidation, or fear around intimacy, the priority is safety and professional support—not experiments. This framework is for couples working through disconnection, not for managing abuse dynamics.

What Comes Next

Intimacy often gets hijacked by old patterns that run silently in the background. The next post addresses how past data distorts present-day signals—and how to update your priors.

Post 16: Updating Relationship Priors—How Old Models Hijack Present Decisions

Intimacy system failing despite input optimisation?

If experiments aren't producing results, or if there's significant pain in this domain, working with a professional can help identify deeper constraints.

Book an Assessment

Educational content. This material is for informational purposes and does not constitute professional advice.