Skip to content
AFTER CERTAINTY

Glossary

Concepts

Each entry is a coordinate in the atlas — open one to move along relationships, patterns, books, and thinkers.

144 concepts

Find a concept

Search concepts…

144 concepts

Concept

Cohesion

Cohesion names whether it is clear who owns a decision, role, or outcome inside a boundary. It becomes important when diffuse assignment lets harm travel without redesign authority. It helps preserve legible ownership and coordinated response, but can fail when cohesion hardens into exclusion or when group binding is mistaken for clear responsibility. It differs from coupling because cohesion concerns ownership clarity within a boundary; coupling concerns how tightly action remains attached to consequence across a chain.

View Concept →

Concept

Compression

Compression reduces moral complexity for transmission at scale. Collapse gives way to compression, compression produces stabilization, and stabilization hardens into inheritance. When populations must coordinate across distance and strangers must share rules, compression lets expectations travel—law narrows discretion so the same words will be read tomorrow, canon fixes meaning so provinces can align. Compression is adaptation under pressure—instability demands it before truth is settled, acceptable interpretation shrinks while exposure widens. At its best, compression preserves coordination when full discernment is too costly; at its worst, tools built to compress instability begin to constrain adaptation, and compression outlives the conditions that required it.

View Concept →

Concept

Connection

Connection names what continues after sentences end—trust, dependence, history, care, or authority that makes the next read costlier or more patient. In How Meaning Moves, connection is the context signal, compression, and restraint move through. It becomes important when coordination continues but return paths thin. It helps preserve answerability across encounters, but can fail when exchange turns mechanical while people quietly stop risking more. It differs from contact because connection outlasts a single exchange; contact governs whether the read stays open while speaking.

View Concept →

Concept

Consequence

Consequence names what happens as a result of decisions and actions—the lived effects that bodies, communities, and ecologies experience regardless of what policies, plans, or intentions recorded. It becomes important when distance, scale, or mediation open gaps between choosers and those who live with the outcomes, when responsibility becomes harder to trace and feedback slower to arrive. Consequence matters because moral life depends on contact between action and effect; accountability works when people can see, feel, or trace the chain between decision and harm. But as coordination extends beyond direct encounter, consequence can travel far from decision—files move while bodies wait, planners optimize logistics far from where effects land, institutions record outcomes in ways that differ from how people experience them. Distance between action and consequence can thin responsibility into role compliance, where doing the job correctly feels sufficient even when outcomes are troubling. The question consequence raises is: who stands where the consequence lands? How long between action and recognizable effect? Consequence differs from outcome (what systems record) in that consequence is what people actually experience, which may not match what was intended or measured.

View Concept →

Concept

Consequence Architecture

Consequence architecture names professional literacy for systems where generation or scale outruns informal caution. It becomes important when guardrails exist on paper but production paths bypass them, or when postmortems produce action items detached from redesign authority. It helps preserve corrigibility under acceleration, but can fail when organizations prove they cared while the same failure class repeats. It differs from coupling because consequence-architecture is designed structure; coupling is the resulting attachment strength. It differs from cohesion because architecture designs the whole path; cohesion names ownership clarity within one boundary.

View Concept →

Concept

Constraint

Constraint marks the pressure that first shaped a moral order—not an idea discovered in isolation, but a condition survival had to answer. In Before Certainty Arrives, ages are defined by shared constraints rather than geography alone. It differs from constraints because constraint names the originating pressure a system responds to; constraints names the technical, legal, and procedural limits shaping action inside an existing system today.

View Concept →

Concept

Constraints

Constraints names the present-tense architecture of what can be done—rules, budgets, timelines, approvals, and technical ceilings. Good constraints channel behavior toward learning and accountability; poor constraints hide tradeoffs or displace consequence. It differs from constraint because constraints describes limits inside an operating system; constraint describes the originating pressure that once made a moral order necessary.

View Concept →

Concept

Contact

Contact names restraint against premature compression in dialogue. In How Meaning Moves, it slows closure so meaning can still be revisited before harm arrives from deciding you understood too soon. It becomes important when speed, being right, or schedule pressure replace live interaction. It helps preserve accurate reading under stakes, but can fail when private conclusions replace the uncertain moment still open in the room. It differs from connection because contact is moment-to-moment closeness to what was said; connection is the ongoing relationship that carries revised trust or reluctance into the next exchange.

View Concept →

Concept

Contestability

Contestability names the condition where dispute can reopen without threatening shared coherence—where challenge does not mean collapse. It becomes important when legitimacy depends on more than coercion, when correction and revision matter for trust and adaptation. It helps preserve the capacity to learn from reality and adjust to changed conditions, but it thins when authority relocates legitimacy beyond ordinary revision—when sacred framing, canon, or procedure makes questioning feel dangerous. Contestability depends on whether revision feels survivable or indistinguishable from rupture. When small groups operate under mutual visibility, authority can be argued for even after it is obeyed. But under pressure—breakdown, threat, or instability—dissent begins to read as moral failure rather than political disagreement, and the range of acceptable interpretation narrows. Contestability thins while inherited certainty still coordinates; systems can run on compliance long after persuasion fades. It marks the moment just before certainty becomes difficult to question at all.

View Concept →

Concept

Context Collapse

Context collapse names what happens when boundaries that should separate concerns, audiences, or interpretive frames dissolve into a single shared surface—when distinct contexts that require different handling are compressed together in ways that look coherent but hide important distinctions. It becomes important when coordination depends on maintaining separate concerns but structure or speed causes them to merge. In software and AI systems, context collapse appears as low cohesion at speed: modules, prompts, corpora, or tools become entangled until ownership and redesign authority become unclear, where output looks syntactically valid or rhetorically fluent even though meaning mixtures govern action undetected. In communication and social media, context collapse occurs when messages intended for one audience are received and evaluated by another, when professional and personal contexts merge on a single platform. Context collapse makes interpretation harder because the appropriate frame is unclear; it makes redesign harder because concerns have become so entangled that there is no clean cut point. The question context collapse raises is: where did separate concerns collapse into one apparently coherent surface? Which contexts that should stay separate are now entangled?

View Concept →

Concept

Contract

Contract is used in a software engineering sense. A contract is the explicit behavioral agreement attached to an interface: what inputs are valid, what outputs are expected, what errors can occur, and what invariants are guaranteed. Strong contracts reduce ambiguity between components and make failures easier to diagnose.

View Concept →

Concept

Contribution asymmetry

The uneven distribution of collaborative labor, recognition, and risk. Some participants carry coordination load, translation between functions, or emotional maintenance that others never see; asymmetry produces instability even when timelines look fine.

View Concept →

Concept

Coordination

Coordination names the problem of acting together when lives are fragmented—when people must move collectively across distance, time, strangers, and difference without complete information or full agreement. It becomes important when individual judgment alone cannot sustain the group, when behavior must hold across contexts that no one person can see completely. Coordination helps preserve collective capacity by making expectations predictable, by enabling strangers to act together under shared rules, by allowing large-scale projects that no single person could accomplish. Roles, rituals, law, canon, procedure, and bureaucracy are all coordination technologies—tools for making tomorrow recognizable from yesterday so action can continue. But coordination can become brittle when it suppresses the feedback and variation it needs to stay responsive, when inherited patterns keep moving after fit has thinned, when dissent is treated as disruption rather than signal. Coordination purchased at the cost of revision can continue functioning long after it has stopped serving the purposes that gave it authority. The question coordination raises is: what coordination problem is this tool solving? What breaks if behavior stops being predictable? Coordination differs from alignment in that coordination is about collective movement, while alignment is about shared direction or values.

View Concept →

Concept

Coordination Pressure

The structural strain that appears when many actors must stay aligned under scale while holding partial information and changing on different timelines. Coordination pressure is not the same as everyday busywork. It names the cost of maintaining a workable shared picture of responsibility, facts, and next actions when cohesion and coupling weaken. It often appears as approvals, queues, handoffs, and reporting layers that synchronize activity without returning consequence to a redesign-capable boundary.

View Concept →

Concept

Correction

Correction names the lived work of narrowing the gap between what was assumed and what is actually happening. It becomes important whenever systems, beliefs, or coordination can drift while still feeling operational. It helps preserve shared reality and learning, but can fail when every correction spawns new framing instead of updated contact with conditions. It differs from repair because correction updates belief and behavior; repair addresses damaged standing and trust. It differs from revisability because correction is the act; revisability is the designed capacity to keep correcting.

View Concept →

Concept

Corrigibility

Corrigibility names the capacity for revision and recovery when conditions change—the ability of a person, institution, model, or moral system to adapt when reality pushes back. It becomes important when stabilization succeeds but conditions continue to shift, when what once compressed instability begins to resist the adaptation it was built to enable. Corrigibility helps preserve responsiveness and learning over time, but it thins when admitting error threatens authority's foundation or when the tools built to preserve certainty begin to constrain revision. Sacred authority can resist correction without appearing illegitimate; canon can slow revision while binding force remains; writing and law can externalize judgment in ways that replace reinterpretation with precedent. Systems can record outcomes that people experience differently, and re-justification can fade while inherited form still coordinates. Corrigibility differs from revisability (openness to correction), repair (mending what broke), and reversibility (ability to undo). The question it raises is: what would have to break for this arrangement to be revised? Recognizing why revision once felt like collapse helps distinguish rigidity from adaptation's residue.

View Concept →

Concept

Counterfactual Success

Counterfactual success—disasters avoided—is hard to politicize and hard to feel. Humans remember warnings more vividly than prevented failures. A forecast that helped policymakers prepare liquidity facilities or stress tests can still feel, to the public, like an error if the movie-script crisis did not arrive. Leadership that wants trust after a forecast era must narrate invisible safeguards without sounding defensive— not "be grateful," but "here is what did not break and who still paid while it held."

View Concept →

Concept

Coupling

Coupling names the strength of the link between what was decided and what later arrives. It becomes important when scale, abstraction, or delay lengthen the chain between decision and lived harm. It helps preserve learning and legitimacy, but can fail when dashboards stay green while frontline frustration grows. It differs from cohesion because coupling tracks action-to-effect attachment; cohesion tracks whether responsibility is clearly held. It differs from consequence-architecture because coupling describes the attachment; consequence-architecture describes intentional design of boundaries, feedback, and escalation.

View Concept →

Concept

DevOps

DevOps is used in a software engineering sense. DevOps refers to practices and operating norms that reduce the distance between software implementation and operations so that delivery, reliability, and learning stay structurally connected.

View Concept →

Concept

Displacement (of interpretation)

Displacement names the condition where interpretation exists but no longer functions—it continues privately while losing public leverage. People understand what is happening without that understanding altering standing, disagreement is reframed as betrayal rather than alternative reading, moral language persists while evaluative traction disappears. Informational remedies fail despite accurate recognition because the problem is not ignorance but loss of mediating function. Displacement differs from interpretive collapse (where public interpretation vanishes) and from coercion (where threat operates). It connects to public interpretation (which still mediates), private understanding (which does not travel), and post-interpretive authority (which no longer depends on justification). Where does understanding persist without changing authority's position? What still interprets—and what no longer mediates legitimacy? The question is not content but function.

View Concept →