Propose the Rule, Not the Framework

Here is a deployment mistake that undoes months of good design in a single message, and nearly everyone makes it:

"I've been reading about a framework for handling our conflict, and I think we should try it."

Every word is sincere. Every word is a tactical disaster. The moment you announce a system, the proposal on the table is no longer a Friday pickup time. It is your worldview. It is the book you read. It is the unmistakable implication that the last three years were a design failure — one they contributed to. You have handed the other parent something much easier to reject than a pickup time: a doctrine. Even a fair rule gets rejected when it arrives as the first clause of an ideology.

So deploy the way the successful cases deploy: without a name and without a preamble. One rule at a time. Smallest surface first. Framed as what it actually is — less friction for both of you:

"Weekday exchanges at the house have been difficult. I propose that on school days, the parent ending time drops off at school and the parent starting time picks up there — same for both of us, both directions. Can we try it for six weeks and see how it goes?"

Look at the engineering inside that unassuming paragraph.

It is one rule. Not a package, not a manifesto, not "and while we're at it." A single decision is a small ask; a system is an identity change.

It costs both parents the same. Nobody's driveway, nobody's territory, identical obligations in both directions. There is no trap to find, and a co-parent who has been fighting you for months will read it twice looking for one. Symmetry is what lets them stop looking.

It has a test window and a review date. This is the disarming clause. Nobody is signing a constitution — they are agreeing to an experiment they can exit. "Try it for six weeks" converts a demand into a trial, and a trial is the cheapest thing in the world to say yes to. (Quiet truth: rules that survive their trial period almost never get cancelled at review. Working systems defend themselves.)

It never mentions the past. No "because you always," no relitigating the incident that motivated it. The rule is about Fridays, not about fault. A proposal that requires someone to concede history will be fought as history; a proposal about the future can be evaluated as logistics.

Then — and this is the discipline — you wait. One rule, one test window, one review. When it holds, the next proposal gets easier, because you are no longer a person with a theory. You are the co-parent whose last idea made both your weeks quieter. Your track record becomes the argument, and it argues while you sleep.

The framework — the surface map, the keystone analysis, the escalation ladder, the whole apparatus — is yours. It runs in the background, in your notes, in how you choose which rule to propose next. What the other parent ever needs to see is only its output: one reasonable, neutral, revocable proposal at a time.

Nobody has to adopt a system for the system to work on them.

---

This deployment discipline sits inside Chapter 11 of Conflict Surfaces — "Build Systems Even Your Ex Would Like" — with the fairness test every proposal should pass before you send it. Appendix F has the templates.