Common Knowledge Generation

Descriptive

Full Practice - Bond - Repairing After Rupture

Mechanism

Common Knowledge Generation is the practice of making a fact, commitment, breach, or new term mutually visible enough that people can coordinate around it.

It is not the same as communication. A leader can tell each person privately that the rule has changed, and every person may know the new rule. That is not yet common knowledge. Common knowledge arrives when people know the rule, know that others know it, know that others know that they know it, and can act on that shared visibility without guessing whether they are the only one who heard.

Private understanding does not repair a public rupture.

Repair often fails at exactly this point. The responsible person says they apologized. The harmed person says they understood. The team says everyone knows what will change. But the knowledge sits in separate heads. No one can rely on the others relying on it. The next difficult moment arrives, and people discover that the repair never became a shared operating condition.

The Control failure is official declaration without mutual uptake: the institution announces, closes the issue, and treats the announcement as repair. The Decay failure is private understanding without shared terms: everyone has a feeling that something was discussed, but nothing becomes visible enough to guide future behavior. The Range form is common knowledge: the relevant people can say what happened, what changed, who knows, and what future conduct will be judged against.

Practice

The diagnostic question is: "Who needs to know this, and how will they know that the others know?"

Use the tool when repair depends on shared terms, group accountability, public correction, team alignment, or any case where private understanding would leave people unable to coordinate.

The tool is simple and often uncomfortable. People dislike making shared terms explicit because explicitness removes deniability.

In the Wild

A team has a serious conflict over a missed deadline. The manager talks privately with each person and believes repair has happened. It has not. Each person now knows something, but no one knows what the others know, and the old story remains available in the room. Common Knowledge Generation requires a shared moment: what happened, what will change, who owns which next action, and what everyone can now expect everyone else to remember.

An organization corrects a public claim quietly on an internal page. The people harmed by the false claim still see the old version circulating. The correction is information, but it has not become common knowledge for the relevant public. Repair requires a correction visible enough that the affected parties can rely on others seeing the corrected record.

Two partners repair a breach privately, but their wider friend group still acts on the older story. The repaired pair may not owe the group every detail. But if the group's behavior keeps reopening the rupture, some shared statement may be needed: enough to reset the common map without violating privacy.

After rupture, do not settle for "we talked about it." Ask what is now commonly known.

If people cannot say what happened, what changed, and what future behavior will be judged against, repair has not yet entered the cooperative field. It may have begun inside private understanding. It has not become something people can act on together.

Lineage

David Lewis' work on convention is the philosophical source for common knowledge as a coordination condition. Conventions work because people do not merely know the convention; they know others know it, and that shared visibility lets them choose behavior in expectation of one another.

Robert Aumann gave common knowledge one of its central formal treatments in game theory. His agreement theorem shows how strong the condition is: once certain beliefs are common knowledge under shared priors, disagreement has a different structure than ordinary private disagreement. The Codex does not import the theorem as a repair method. It inherits the lesson that higher-order knowledge changes what coordination can rationally do.

Michael Chwe's Rational Ritual is the clearest source for common knowledge generation as a social mechanism. Public ceremonies, announcements, rituals, broadcasts, and shared events do not only transmit information from a center to individuals. They let the participants know that others have seen the same thing.

The Codex places the tool in the Bond because repair is often a coordination problem. People may privately know enough to continue, but the cooperation cannot safely resume until the relevant knowledge is shared, witnessed, and available for accountability.

Cross-references

Within the category. Trust Repair names what must be repaired. Common Knowledge Generation makes the repair visible enough to guide future behavior. Indaba and Peacemaking Circles are process forms that can generate common knowledge through direct collective speech.

Across the Workshop. Schelling Points reads tacit coordination where common expectations already exist. Common Knowledge Generation deliberately builds shared expectations when tacit salience is not enough. Report Fidelity matters because the shared record can coordinate people around a false or distorted account if the report is bad.

Limitations. Common knowledge can coordinate around falsehood, coercion, scapegoating, or premature closure as easily as around truth. The tool does not decide whether the shared object is accurate. It only asks whether the knowledge has become visible enough to coordinate behavior. That is why it needs Trust Repair and Report Fidelity beside it.