Connection Before Correction
The practice of naming what is valid, shared, or worth preserving before correcting what is wrong.
Expansion · Bond · Receiving Disagreement Well
Mechanism
Correction usually fails before the correction begins. The other person hears threat, status loss, dismissal, contempt, or the opening move in a fight. Sometimes they are wrong. Sometimes they are reading the situation accurately because correction is being delivered as attack.
Connection Before Correction is the discipline of naming the valid, shared, or preservable part before engaging what is wrong. It is not flattery. It is not softening the conclusion. It is the sequence that keeps correction inside cooperation.
If you want correction to be received, show the person what you are not trying to destroy.The tool belongs in the Bond because truth often arrives through relationship. A person can be factually right and relationally ineffective. They correct in a way that makes the other person defend identity, status, or belonging rather than inspect the claim. Then both people blame the other's psychology. The simpler explanation is that the correction removed safety before asking for revision.
The Control failure is correction without connection: efficient, sharp, often accurate, and often useless because it turns the interaction into defense. The Decay failure is connection without correction: warmth, validation, empathy, and no honest challenge. The Range form is connection that clears the path for correction, followed by correction that actually names the issue.
Practice
The diagnostic question is: "What can I truthfully preserve before I challenge what needs changing?"
Use it when you are about to disagree, reject a draft, challenge a decision, correct a factual error, respond to criticism, or name a pattern that the other person may experience as attack.
Name the preserved signal. Find the part that is true, useful, understandable, or worth keeping. "The urgency is right." "The concern about user trust is valid." "You are protecting a real risk." "The first half works." If you cannot name anything specific, slow down. You may not have understood the position yet, or the correction may need a different frame.
Distinguish validation from agreement. Connection does not mean accepting the claim. You can validate the concern and reject the conclusion. You can recognize the motive and still say the method is harmful. You can name the strong part and still cut the weak part. This distinction keeps connection from becoming Decay.
Correct the object, not the person. Once connection is established, name the object precisely: the claim, inference, behavior, risk, evidence gap, missing constraint, or cost. Do not make the person defend their whole self when the actual correction concerns one part of the work.
Connection has to be specific or it becomes a technique. People can feel the difference between "I hear you" as a ritual and "the risk you are protecting is real, but the solution creates a worse one" as actual engagement. The first is a cushion. The second is a bridge.
In the Wild
Someone sends you a draft with a weak argument and one strong instinct. The bad correction starts with the weakness: "This does not work." The better correction starts with what should survive: "The concern about incentives is the right center. The problem is that the current argument jumps from one example to a general claim too quickly." Now the person knows what to preserve while revising. The correction becomes usable.
A team member challenges your plan in a meeting. Your first impulse is to explain why they are missing context. Connection Before Correction asks you to name what they saw first. "You are right that the rollout risk is higher than the roadmap makes visible. I still think the launch is possible, but only if we change the support plan." The disagreement remains sharp, but the signal is not punished.
A friend says something you think is wrong about a conflict. You could correct the conclusion directly. You could also start where they are protecting something real: "I understand why the loyalty question bothers you. I think you are right that loyalty matters here. I do not think loyalty requires defending what happened." That sequence keeps the correction attached to a shared value rather than turning it into a contest over who is a better friend.
Before you correct, name what survives the correction.
Not to make the other person comfortable. To make the correction honest. If nothing survives, say that. But if something does, and you skip it, you are making the other person defend what you should have preserved.
Lineage
"Connection before correction" appears most directly in education, child development, and positive discipline contexts. The common lesson is that people are less able to receive correction when they feel unsafe, shamed, or disconnected. The Codex adapts the phrase for adult cooperation and disagreement: the same sequence matters when the correction concerns a claim, decision, draft, public position, or institutional practice.
Conflict mediation and restorative practice supply another lineage. Effective mediation often separates impact from intent, validates the experience that can be validated, and then creates conditions for accountability. Connection does not erase responsibility. It creates the conditions under which responsibility can be faced without immediate self-defense.
Motivational interviewing belongs nearby as a communication discipline: resistance is often increased by direct confrontation and reduced when the other person's own values, reasons, and autonomy are engaged. The Codex does not turn correction into therapy. It inherits the practical lesson that people revise more honestly when they do not experience the revision as domination.
Rapoport's rules for criticism, popularized in Daniel Dennett's version, are also relevant. Restate the other person's position clearly, name points of agreement, say what you learned, then criticize. Connection Before Correction is narrower and more relational, but the sequence is similar: prove contact before challenge.
Cross-references
Within the category. Productive Conflict is the wider disagreement discipline. Connection Before Correction is one sequence inside it. Loyal Opposition protects the role of dissent; Connection Before Correction protects the moment where dissent or correction is being answered.
Across the Workshop. Good Faith as Default is the opening posture that keeps ambiguity from becoming accusation too early. Charitable Interpretation is the Foundation-side ambiguity discipline. Steelmanning builds the strongest version of the claim before answering it.
Limitations. The tool can be weaponized. A manipulative person can demand endless connection before any correction is allowed, turning the sequence into a tax on truth. The Cooperative Vulnerability names that failure. Connection Before Correction is a cooperative practice under reciprocal norms. It is not an obligation to keep cushioning correction for someone who uses the cushion to avoid being corrected.