GlossaryConceptsEach entry is a coordinate in the atlas — open one to move along relationships, patterns, books, and thinkers.ConceptAbstractionAbstraction is mediation away from direct encounter: compression of complexity as systems scale, valued when it preserves accountability signal at the boundaries where behavior can still be redesigned—and costly when it hides consequence until feedback arrives too late.ConceptAccelerationpressure favoring speed/alignment over reflectionConceptAccountabilityAccountability is exposure to consequence: who can see effects, who can be challenged or redirected, and whether authority stays close enough to lived outcomes for correction to remain plausible.ConceptAdaptabilityThe capacity of coordinated action to change direction when reality pushes back. Together with scalability, it sorts groups into the four states adaptive, entrenched, regenerative, and stalled, and underpins how renewal and erosion are read.ConceptAdaptationlocal response to pressureConceptAgencyAgency is the practical capacity to initiate action that can affect outcomes. Formal role without real leverage is low agency, even when nominal responsibility remains.ConceptAgileAgile is used in a software engineering sense. Agile refers to iterative development approaches that shorten feedback cycles, emphasize incremental delivery, and increase team-level ownership of ongoing change.ConceptAlignmentcoordinated behavioral convergenceConceptAsymmetryuneven distribution of power/consequenceConceptAuthorityAuthority is operational coordination power—the recognized right to steer, allocate, or constrain action—always in tension with legitimacy and with whether consequence stays visible enough under scale for coordination to remain contestable rather than brittle.ConceptAuthorizationNormalized permission for action that outlasts the local pressures that first produced it; contrasts with one-off adaptation.ConceptBureaucracyrule-bound institutional coordination and role-bound authorityConceptCertaintystabilized coordination stateConceptCirculationCirculation is transmission and reproduction through systems: how norms, habits, and design choices move, repeat, and amplify—what spreads without being re-owned locally, and what keeps learning alive as coordination widens.ConceptCohesionThe degree to which responsibility is clearly held within a boundary (team, role, function, or institution). High cohesion means ownership is legible and decisions are not diffusely assigned.ConceptCompressionreduction of complexity for transmissionConceptConsequenceactual effects in realityConceptConstraintlimits preserving stability/corrigibilityConceptConstraintsConstraints are the limits and boundary conditions that shape what actions are possible in a system. They include technical limits, legal rules, time pressure, budget limits, and institutional procedures. Good constraints channel behavior toward learning and accountability; poor constraints hide tradeoffs or displace consequence.ConceptContestabilityability to challenge without collapseConceptContractContract 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.ConceptCoordinationcollective behavioral organizationConceptCorrectionCorrection is reality-contact and revisability: the lived work of noticing mismatch, updating beliefs or behavior, and narrowing the gap between what was assumed and what is actually happening before drift hardens into normal.ConceptCorrigibilitycapacity for revision and recoveryConceptCouplingCoupling is attachment between action and consequence—how tightly decisions remain traceable to effects, how feedback travels, and whether redesign authority can still bite when scale and abstraction lengthen the chain.ConceptDecayThe state of a group when capacities shrink: influence no longer changes course readily under pressure, coordinated action no longer sustains reach, or both. Contrasts with vitality; sustained erosion tends toward decay.ConceptDevOpsDevOps 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.ConceptDistanceseparation from visible consequenceConceptDORADORA is used in a software engineering sense. DORA refers to research-backed software delivery metrics and practices (for example, lead time for changes and change failure rate) used to evaluate learning-loop quality between development and operations.ConceptDriftgradual decoupling from original conditionsConceptEffectivenessWhat gets amplified, deferred, or mistaken for control when people look to leadership—not the same as morality or intent.ConceptErosionThe direction in which a group moves when scalability or adaptability shrinks—toward insulation, narrowed correction, and broken reach. Contrasts with renewal; it names structure, not moral worth.ConceptExposuredegree of consequence contactConceptFeedbackThe path by which outcomes return as signal and influence future decisions. Weak or delayed feedback reduces learning quality.ConceptFrictionresistance that interrupts automatic escalationConceptGovernance CouplingThe degree to which formal oversight structures preserve real consequence return to decision-capable authority. Governance coupling weakens when signal is filtered, delayed, or politically insulated, even if nominal accountability mechanisms still exist.ConceptGuest LeadershipA form of circulation where people closest to an issue can temporarily step in to lead a response, then return to their usual role.ConceptHarmWhere cost lands when influence is exercised: who absorbs it, who is kept in view, and what displacement is treated as acceptable.ConceptHexagonal ArchitectureHexagonal architecture is used in a software engineering sense. Hexagonal architecture (also called ports and adapters) is a boundary pattern that keeps domain logic insulated from external technologies by routing integration concerns through explicit interface ports and adapter implementations.ConceptIncentivesIncentives are the reward and penalty patterns that influence behavior over time. Incentives include formal metrics, promotion logic, political pressures, funding structures, and social recognition patterns. Incentives do not determine behavior by themselves, but they strongly bias what actors optimize for.ConceptInheritancepersistence across generations/structuresConceptInterfaceInterface is used in a software engineering sense. An interface is the defined boundary through which one component interacts with another (for example, function signatures, API endpoints, message schemas, or protocol expectations). A good interface makes dependencies explicit while minimizing exposure to internal implementation details.ConceptInterpretationlocalized reconstruction of meaningConceptInvariantA condition that should remain stable across contexts and scale if a system is to stay healthy. The invariant is that responsibility should remain cohesive and consequence should remain intentionally coupled.ConceptJudgmentJudgment is deliberate evaluation under uncertainty: slowing automatic escalation long enough to weigh tradeoffs honestly, keep coordination aligned with consequence rather than with speed alone, and preserve room for contestability.ConceptLegitimacyLegitimacy is justified recognition of authority—whether power reads as earned and contestable enough that coordination holds under stress instead of collapsing into cynicism, performative compliance, or hidden veto by drift.ConceptMeaningtransmitted coordination signalConceptMediationinterpretation through layered systemsConceptMomentumcontinuation detached from renewed judgmentConceptMoral Densityconcentration of visible consequence and relational accountabilityConceptNormalizationdrift becoming baselineConceptOperational CouplingThe degree to which the people who design or decide also remain close to execution and runtime consequence. Operational coupling is stronger when builders, operators, and reviewers share consequence exposure. It is weaker when handoffs separate decision authority from incident impact.ConceptProximityrelational nearness to consequenceConceptReciprocityshared exposure and mutual constraintConceptRenewalRenewal is restoration of legitimacy and correction: deliberate moves that reopen feedback, shorten consequence distance, and pull a stretched system back toward workable exposure to reality before erosion becomes the new baseline.ConceptResponsibilityResponsibility is the durable relation between action and answerability. It includes not only causal involvement but also the obligation to account for consequences and respond to what is revealed by them.ConceptReversibilityability to undo movementConceptScalabilityThe capacity of coordinated action to grow in reach. Together with adaptability, it sorts groups into adaptive, entrenched, regenerative, and stalled, and underpins how renewal and erosion are read.ConceptScaleScale is coordination beyond direct relational encounter—growth in size, complexity, or abstraction layers that increases distance between decisions and consequences and therefore changes how cohesion, coupling, and feedback must be engineered to stay learnable.ConceptShift LeftShift left is used in a software engineering sense. Shift left means moving quality, security, and risk checks earlier in the development lifecycle rather than concentrating detection late in integration or release.ConceptStabilityContinuity of coordination and expectation that resists disruption; can trade off against contestability when revision paths thin.ConceptSystemA system is an organized set of people, processes, rules, and structures that produces repeatable outcomes over time. The term applies across domains: software architectures, teams, firms, agencies, governance structures, and media institutions. The shared criterion is not technology; it is patterned behavior under constraints, incentives, and feedback.ConceptTemporal CouplingThe degree to which consequences return quickly enough to shape near-term decisions. Strong temporal coupling shortens the time between action and correction. Weak temporal coupling introduces lag, memory loss, and interpretive noise that can protect failing designs from timely revision.ConceptThinkingactive interruption of automaticityConceptThroughputoptimization for flow/speedConceptUncertaintyunresolved/revisable coordination stateConceptVitalityThe state of a group when influence can sustain coordinated action as reach grows—how open the group is to revision and how workable coordination remains in the moment. Contrasts with decay; sustained renewal tends toward vitality.ConceptWaterfallWaterfall is used in a software engineering sense. Waterfall refers to a phase-sequenced development model where requirements, design, implementation, testing, and release are treated as largely distinct stages with formal handoffs and review gates.
