Feedback¶
Core Idea¶
Feedback is the structural arrangement in which a portion of a system's output is routed back to influence its subsequent input, closing a loop between cause and effect. The essential commitment is that the system's own behavior becomes a driver of its own behavior on the next cycle: the present depends not only on the external input but on the system's prior output. Every feedback arrangement specifies (1) the variable being measured or tapped at the output, (2) the path by which that signal returns to the input, (3) the sign and strength of the coupling — whether the returned signal opposes, reinforces, or conditionally modifies the input — and (4) the timescale on which the loop closes. Feedback is not merely a causal chain A→B→C but a closure: A→B→A, where the output of the system at time \(t\) becomes (part of) the input at time \(t + \delta\). This closure is the defining feature: without a return path, there is no feedback, only open-loop feedforward. Feedback enables self-regulation (negative feedback) and self-amplification (positive feedback); it is the mechanism by which systems steer themselves, maintain equilibrium, or spiral into instability. The concept is ubiquitous: an organism maintaining body temperature, a price system clearing a market, a social group enforcing norms, a software system monitoring and restarting failed services—all operate through feedback loops. Understanding feedback requires clarity on the loop's sign (stabilizing or amplifying), its gain (responsiveness), and its delay (latency around the loop); these three parameters jointly determine whether a feedback system converges to equilibrium, oscillates around it, or diverges into runaway behavior.
How would you explain it like I'm…
Loop Back
Output Becomes Next Input
Closed Cause-Effect Loop
Structural Signature¶
the input-output sensing mechanism — the comparison-to-reference (set-point) operation — the corrective-action signal generation — the negative-feedback (stabilizing) versus positive-feedback (amplifying) distinction — the loop closure connecting output to input — the time-delay-induced oscillation tendency
A system exhibits feedback when each of the following holds:
- An identifiable output. Some measurable or operationally-tappable quantity is produced by the system: a temperature, a price, a rate, a count, a signal.
- A sensed or measured return path. Something in the environment or system samples that output and carries a representation of it back toward the input stage.
- Coupling to the input. The returned signal combines with, modifies, or replaces the original driving input — additively, multiplicatively, or through a switching rule.
- Sign of the loop. The loop is negative (returned signal opposes the output, stabilizing the system), positive (returned signal reinforces the output, amplifying or runaway), or mixed/conditional (sign depends on state or threshold).
- Loop gain and delay. The strength of the coupling and the time it takes for a disturbance to propagate around the loop jointly determine whether the system is stable, oscillatory, or unstable.
- A closed topology. The cause-effect arrows form a cycle, not just a chain. Open-loop systems have no feedback even if they respond to external inputs.
What It Is Not¶
- Not any cause-effect relation. A one-way influence from A to B is not feedback. Feedback requires the return arrow from B back to A that closes the loop.
- Not equilibrium. Equilibrium is a state property
(balance of forces, no net change); feedback is a
structural mechanism that can produce equilibrium,
oscillation, or instability depending on loop
parameters. See
equilibriumfor the distinction. - Not homeostasis alone. Homeostasis is one product of negative feedback — a regulated variable held near a setpoint. Feedback is the underlying mechanism; positive feedback and mixed-sign feedback also exist and produce quite different outcomes.
- Not learning. Many learning processes use feedback signals, but learning additionally involves updating an internal model or parameter, not just closing a loop on the current output.
- Not iteration or recursion. Recursion is self-reference in a definition; iteration is repeating a step. Feedback specifically routes a measured output back as a modifier of input, at runtime, continuously.
- Common misclassification. Calling any dynamic adjustment "feedback." If there is no explicit return path and the adjustment is driven by a planner or schedule rather than the system's own output, what is present is feedforward control or open-loop planning, not feedback.
Broad Use¶
- Control engineering
- Thermostats, PID controllers, automatic gain control, servo mechanisms, stability compensators.
- Biology and physiology
- Homeostatic regulation (temperature, blood glucose, osmolarity), endocrine loops, predator-prey dynamics, neural inhibition.
- Economics
- Supply-demand adjustments, price signals, speculative bubbles (positive feedback), central-bank stabilization (negative feedback).
- Ecology
- Population regulation, nutrient cycles, climate feedbacks (albedo, water vapor, carbon cycle).
- Organizations and learning
- Performance reviews, product-iteration cycles, after-action reviews, OKR check-ins, customer complaint loops.
- Social dynamics
- Reputation effects, norm reinforcement, viral spreading, polarization loops in media ecosystems.
Clarity¶
Feedback clarifies by insisting that any claim about a system's self-regulating or self-amplifying behavior point to an explicit return path from output to input. "The market self-corrects" becomes "the loop is: rising prices reduce demand, which reduces prices, with gain and delay characteristic X." The clarifying force is to convert handwaved dynamics into an explicit loop diagram with named variables, signed couplings, and identifiable timescales.
Manages Complexity¶
- Replaces continuous planning with local sensing: a feedback-controlled system does not need a predictive model of all future disturbances; it reacts to the consequences of disturbances as they arrive.
- Licenses robust behavior from imperfect components: negative feedback tolerates component drift, nonlinearity, and unmodeled effects by driving the error to zero regardless.
- Makes otherwise intractable dynamics predictable: linear feedback systems have a mature mathematical theory (stability, bandwidth, poles, zeros) that yields quantitative predictions before running the system.
- Enables composition into cascades and hierarchies: inner loops handle fast dynamics, outer loops handle slow ones, with each loop responsible for a different timescale.
- Surfaces system identity: the loops present in a system often reveal what that system is trying to hold invariant, amplify, or exclude — loops are a fingerprint of purpose.
Abstract Reasoning¶
Feedback trains a reasoner to ask:
- Is the arrow from output back to input explicit, or am I invoking self-regulation without a return path?
- What is the sign of the loop — does the returned signal oppose, reinforce, or conditionally modify the input?
- What is the loop gain, and what is the loop delay? Are they compatible with stable operation, or will they produce oscillation or runaway?
- Where is the setpoint or reference, if any, and what determines it?
- What happens at the boundaries of the operating range — saturation, nonlinear switching, hysteresis?
- Are there multiple loops, and do they compete, cooperate, or operate on separable timescales?
Knowledge Transfer¶
Role mappings across domains:
- Output variable ↔ measured quantity / observable / behavior / price / rate / level
- Sensor / tap ↔ measurement / perception / monitoring / audit / metric
- Return path ↔ wire / signal / information flow / communication / hormone
- Comparator / error ↔ deviation from setpoint / discrepancy / gap / dissatisfaction
- Actuator / input coupling ↔ control valve / policy lever / behavior change / intervention
- Loop gain ↔ responsiveness / sensitivity / elasticity / reaction strength
- Loop delay ↔ lag / latency / reporting interval / reaction time
- Negative feedback ↔ stabilization / homeostasis / error correction / damping
- Positive feedback ↔ amplification / bandwagon / runaway / bubble / chain reaction
An engineer tuning a PID controller, a physiologist tracing the insulin-glucose loop, and a product manager reading a weekly customer-sentiment dashboard are all doing the same structural work: name the output, identify the sensed return path, determine the sign and strength of the coupling, and set the loop delay by how often the signal is read. The same three diagnostic questions — "what is returning, how strong, how delayed?" — apply across the domains, and the same failure modes (oscillation, saturation, runaway) arise from the same loop-level properties regardless of substrate.
Examples¶
Formal/abstract¶
Wiener's 1948 Cybernetics introduced feedback as the foundational concept of control + communication systems[1]. Consider the continuous-time linear feedback system where an output \(y(t)\) is measured, compared to a setpoint \(r(t)\), producing an error \(e(t) = r(t) - y(t)\), which drives a control input \(u(t) = K_p e(t) + K_i \int e(\tau) d\tau + K_d \frac{de}{dt}\) (proportional-integral-derivative controller). The closed-loop dynamics are \(\dot{y} = f(y, u)\); stability depends on the poles of the transfer function \(\frac{Y(s)}{R(s)}\), which depend on \(K_p, K_i, K_d\) (loop gain parameters) and the system poles. Nyquist stability criterion and Bode analysis provide quantitative methods to determine stability without solving the differential equation[2]; a loop with insufficient phase margin oscillates; a loop with excess gain drives instability. The classical control-theory toolkit (root-locus, frequency response, pole placement) is entirely about tuning the feedback parameters to achieve stability and bandwidth specs. Feedback amplifiers (Black 1934) in signal processing use negative feedback to reduce amplifier nonlinearity and distortion; the trade-off is that gain is reduced unless open-loop gain is very high[3]. This formal structure is the foundation of modern control engineering.
Mapped back: Formal feedback is the canonical example where continuous-time dynamical systems are stabilized through error-based control; all engineering feedback-control design traces back to this structure.
Applied/industry¶
A product team's weekly customer-complaint review illustrates feedback at organizational scale[4]. Output variable: rate of a particular complaint type. Sensor: customer-support dashboard, tracking complaint frequencies by category. Return path: the weekly review meeting and subsequent product-backlog additions. Comparator: the team's tolerance threshold for each complaint class — if the complaint rate exceeds the threshold, priority rises; if below, it deprioritizes. Actuator: engineering changes deployed in the next sprint. Loop sign: negative (fixes reduce complaint rate, which reduces urgency, which stabilizes the feedback). The same failure modes appear as in thermostat control[1]: high gain (overreacting to one bad week of complaints, thrashing priorities) produces oscillating priorities and instability; long delay (complaints take two quarters to address after diagnosis, because the backlog is deep) produces persistent error despite effort; unstable tuning (too-responsive product managers making daily priority changes based on hourly complaint counts) produces chaotic behavior. Ashby's feedback framework applies unchanged[5]. Another example: a manufacturing process uses a feedback loop to maintain product quality. Output: defect rate measured in real-time from quality-assurance samples. Return path: automated monitoring system feeding data to the control system. Comparator: desired defect-rate target. Actuator: adjustment of machine parameters (temperature, speed, pressure). The same dynamics hold: if the response is too slow (long delay in adjusting temperature after a defect signal), the system overshoots and quality oscillates around the target; if the response is too aggressive (high gain, making large parameter changes for small quality deviations), the system hunts around the setpoint. Forrester's Industrial Dynamics pioneered this application, showing that supply-chain feedback loops with delays produce the "bullwhip effect" — small fluctuations in downstream demand are amplified into massive swings in upstream orders, a direct consequence of loop gain and delay mis-tuning[6].
Mapped back: Applied feedback is found in production control, organizational quality loops, and supply-chain dynamics; the structural diagnosis—check gain, check delay, ensure stable tuning—transfers directly from engineering to operations.
Structural Tensions¶
T1 — Sign of the Loop. Negative feedback stabilizes; positive feedback amplifies; many real systems contain both, and the operating regime determines which dominates. Misidentifying the sign — or missing a positive-feedback pathway hiding inside what is nominally a negative-feedback system — changes predicted behavior from bounded to runaway[7]. A canonical failure: designing or reasoning about a system assuming negative feedback dominates and missing the positive-feedback pathway that triggers a bubble, phase transition, or cascade once a threshold is crossed. Maruyama's distinction between negative-feedback (deviation-dampening) and positive-feedback (deviation-amplifying) loops[7] clarifies this tension but does not resolve it — the analyst must examine loop structure in detail to identify which dominates and under what conditions the dominance shifts.
T2 — Gain versus Delay (Stability). Stability depends on the joint values of loop gain and loop delay. A modest gain with substantial delay can oscillate or go unstable; high gain with short delay can be well-behaved. Reasoning about gain in isolation, or delay in isolation, misses the interaction that governs whether the system rings, oscillates, or converges[2]. The canonical failure mode: increasing responsiveness (gain) to fix a sluggish system without accounting for the delay already present, producing oscillation or instability that is harder to diagnose than the original sluggishness. Tuning feedback loops requires simultaneous attention to both parameters; this is why classical control emphasizes gain margins and phase margins, not gain alone.
T3 — Setpoint versus Drift. A feedback loop holds the system near a setpoint or reference; but the setpoint itself can drift (deliberately or through error), and the loop cannot distinguish "faithfully tracking a shifting reference" from "failing to hold a constant reference." The loop's behavior is only as trustworthy as its reference[8]. The failure mode: a successful controller quietly tracking a drifting reference — meeting its loop-level objective while the overall purpose is being missed. Organizational performance metrics drifting upward or downward in an organization that is "hitting targets" quarter after quarter is the canonical pattern. Powers' control-of-perception framework addresses this by modeling organisms as controlling for internally-specified reference values[9]; the implication is that feedback control cannot guarantee correct purpose if the reference itself is not correct.
T4 — Loop Isolation versus Loop Interaction. Systems often contain many feedback loops, and those loops interact[10]. Two independently-designed negative-feedback loops can combine into an oscillator; a fast inner loop can destabilize a slow outer loop if they share a variable. Single-loop thinking misses the multi-loop dynamics that actually govern the system. The failure mode: tuning one loop in isolation — a control system, a policy lever, an incentive scheme — and getting pathological global behavior because other loops were not in the analysis. Bateson's "Steps to an Ecology of Mind" explores this extensively, showing that ecological and social feedback loops often interact to produce surprising behaviors[11].
T5 — Sensor Error versus True Output. Feedback relies on accurate sensing of the output; but sensors have noise, bias, and latency. A perfect feedback algorithm with a noisy sensor produces erratic control; conversely, exquisite accuracy in control computation cannot overcome a bad sensor. The tension is between investing in sensor quality versus control-algorithm sophistication. In organizational feedback loops (customer surveys, quality metrics), the tension is acute: the "signal" is often indirect, delayed, and subject to gaming.
T6 — Feedback Coupling versus External Disturbance. Feedback mechanisms couple the output back to input, but real systems also experience external disturbances not routed through the feedback loop. A system with strong feedback may be robust to disturbances it can sense but fragile to unseen disturbances. Sterman's focus on dynamics in organizations[10] emphasizes this: a feedback loop that is well-tuned for one class of disturbances may be poorly tuned for others, especially if the disturbances are novel or occur outside the feedback mechanism's sensing range.
Structural–Framed Character¶
Feedback sits at the structural end of the structural–framed spectrum: it is a pure relational pattern, the same in any domain where it appears, and nothing about its meaning depends on a particular field's vocabulary or assumptions. The pattern is a closed loop: part of a system's output is routed back to shape its next input, so the system's own behavior becomes a driver of its later behavior.
Every diagnostic points one way. The pattern carries no home vocabulary that must travel with it: the same loop describes a thermostat correcting room temperature, a microphone howling near its speaker, or a population whose growth feeds back on its own rate, each told in its own field's words. It carries no inherent approval or disapproval — a feedback loop is neither good nor bad until you specify what it does. Its origin is formal, describable purely in terms of signals routed from output to input, with no appeal to human norms. To identify feedback is to recognize a loop already wired into the system, not to add an interpretation. On every diagnostic, it reads structural.
Substrate Independence¶
Feedback is about as substrate-independent as a prime can be — composite 5 / 5 on the substrate-independence scale. Its signature, route an output back to the input, compare it against a setpoint, and apply a correction, is stated in pure relational terms with no commitment to any medium, so it is recognized rather than translated when it turns up in a new field. And it turns up almost everywhere: cybernetics, endocrine regulation, predator–prey ecology, central-bank policy, software control loops, and organizational management all instantiate the identical structure, a universality established as far back as Wiener's founding work. Maximal abstraction, maximal spread, and heavily documented transfer all line up, which makes it one of the catalog's canonical 5s.
- Composite substrate independence — 5 / 5
- Domain breadth — 5 / 5
- Structural abstraction — 5 / 5
- Transfer evidence — 5 / 5
Relationships to Other Abstractions¶
Current abstraction Feedback Prime
Foundational — no parent edges in the catalog.
Children (156) — more specific cases that build on this
-
Adaptive feedback cancellation Domain-specific is a kind of Feedback
The proposed strict upward parent is
prime:feedback.The method senses and cancels a signal returned through a feedback path; adaptive path estimation supplies the residual. This is a proposal-only workspace relationship: the accepted Prime supplies a genuinely instantiated structural prerequisite or superclass, while Adaptive feedback cancellation adds domain-specific constraints. The entry does not collapse into that parent because online system identification inside an electro-acoustic feedback loop and its entrainment tradeoff It also declines a nearby thematic catalog node: the neighbor does not literally subsume the constitutive identity of Adaptive feedback cancellation. This explicit assert-and-decline pattern keeps the proposed DAG narrow and prevents a merely thematic edge. The prospective workspace queue contains one strict upward edge toprime:feedback. No live DAG mutation is authorized. -
Algorithmic radicalization Domain-specific is a kind of Feedback
The proposed strict upward parent is
prime:feedback.User behavior and recommendations form a coupled feedback loop; platform objectives and radicalization evidence supply the residual. This is a proposal-only workspace relationship: the accepted Prime supplies a genuinely instantiated structural prerequisite or superclass, while Algorithmic radicalization adds domain-specific constraints. The entry does not collapse into that parent because the contested algorithm-exposure-feedback pathway from personalization to extremist orientation, together with its causal-identification burden It also declines a nearby thematic catalog node: the neighbor does not literally subsume the constitutive identity of Algorithmic radicalization. This explicit assert-and-decline pattern keeps the proposed DAG narrow and prevents a merely thematic edge. The prospective workspace queue contains one strict upward edge toprime:feedback. No live DAG mutation is authorized. -
Carbon cycle Domain-specific is a kind of Feedback
The proposed strict upward parent is
prime:feedback.prime:feedback is the nearest broader Prime; the source domain and invariant supply the autonomous residual. This is a proposal-only workspace relationship: the accepted Prime supplies a genuinely instantiated structural prerequisite or superclass, while Carbon cycle adds domain-specific constraints. The entry does not collapse into that parent because the domain-specific identity determined by the spatial and temporal boundary, carbon reservoirs and chemical forms, directed fluxes and units, transformations, residence times, conservation balance, natural baseline and anthropogenic perturbations and uncertainty are explicit It also declines a nearby thematic catalog node: the neighbor does not literally subsume the constitutive identity of Carbon cycle. This explicit assert-and-decline pattern keeps the proposed DAG narrow and prevents a merely thematic edge. The prospective workspace queue contains one strict upward edge toprime:feedback. No live DAG mutation is authorized.
- Carbon leakage Domain-specific is a kind of Feedback
The proposed strict upward parent is `prime:feedback`.prime:feedback is the nearest broader Prime while the source-domain carrier and invariant supply the autonomous residual. This is a proposal-only workspace relationship: the accepted Prime supplies a genuinely instantiated structural prerequisite or superclass, while Carbon leakage adds domain-specific constraints. The entry does not collapse into that parent because the domain-specific identity fixed by the regulated and external regions, policy and counterfactual, sectors and gases, direct emissions reduction inside the boundary, policy-caused increase outside, production relocation trade fuel-price and technology channels, leakage-rate numerator denominator and sign, time horizon, consumption-versus-production accounting, uncertainty and distinction from competitiveness effects are explicit It also declines a nearby thematic catalog node: the neighbor does not literally subsume the constitutive identity of Carbon leakage. This explicit assert-and-decline pattern keeps the proposed DAG narrow and prevents a merely thematic edge. The prospective workspace queue contains one strict upward edge to `prime:feedback`. No live DAG mutation is authorized.
- Causal loop diagram Domain-specific is a kind of Feedback
The proposed strict upward parent is `prime:feedback`.CLDs explicitly represent reinforcing and balancing feedback loops; system-dynamics notation and evidence boundaries supply the residual. This is a proposal-only workspace relationship: the accepted Prime supplies a genuinely instantiated structural prerequisite or superclass, while Causal loop diagram adds domain-specific constraints. The entry does not collapse into that parent because signed qualitative causal feedback mapping with explicit loop polarity and narrative interpretation before quantitative stock-flow modeling It also declines a nearby thematic catalog node: the neighbor does not literally subsume the constitutive identity of Causal loop diagram. This explicit assert-and-decline pattern keeps the proposed DAG narrow and prevents a merely thematic edge. The prospective workspace queue contains one strict upward edge to `prime:feedback`. No live DAG mutation is authorized.
- Closed-loop transfer function Domain-specific is a kind of Feedback
The proposed strict upward parent is `prime:feedback`.The function is the algebraic signature of a closed feedback interconnection; control-system port semantics supply the residual. This is a proposal-only workspace relationship: the accepted Prime supplies a genuinely instantiated structural prerequisite or superclass, while Closed-loop transfer function adds domain-specific constraints. The entry does not collapse into that parent because net transfer behavior created by closing a feedback loop, including pole relocation and reference, disturbance, noise, and sensitivity path distinctions It also declines a nearby thematic catalog node: the neighbor does not literally subsume the constitutive identity of Closed-loop transfer function. This explicit assert-and-decline pattern keeps the proposed DAG narrow and prevents a merely thematic edge. The prospective workspace queue contains one strict upward edge to `prime:feedback`. No live DAG mutation is authorized.
- Cloud feedback Domain-specific is a kind of Feedback
The proposed strict upward parent is `prime:feedback`.The output radiative anomaly literally returns to influence the temperature state that drove the cloud change; cloud microphysics, altitude, shortwave and longwave radiation, and climate-response normalization supply the autonomous residual. The edge is proposal-only and points to a frozen prior-baseline Prime. The entry does not collapse into the parent because the closed climate-response loop from temperature through cloud-property change to radiative imbalance, normalized or otherwise tied to the initiating perturbation; present-day cloud cooling, aerosol–cloud forcing, and albedo alone do not reproduce it A thematic neighbor is declined whenever it does not literally subsume that rule. The prospective workspace queue contains one strict upward edge to `prime:feedback`. No live DAG mutation is authorized.
- Collateral Squeeze Domain-specific is a kind of Feedback
A Collateral Squeeze is a positive feedback loop specialized to price-linked borrowing capacity, forced sales, and further price declines in a shared collateral market.Feedback supplies the genus: Outputs influence inputs. Collateral Squeeze preserves that general structure while adding its differentia: The procyclical spiral in which a fall in a pledged asset's price cuts every leveraged holder's borrowing capacity and forces sales into the same market that sets the price — coupling firms through a shared observable rather than a counterparty network. The parent can occur without those added commitments, whereas removing the parent structure leaves no basis for classifying the child as this subtype. That asymmetry establishes subsumption rather than mere association.
- Communal reinforcement Domain-specific is a kind of Feedback
The proposed strict upward parent is `prime:feedback`.Repeated belief and retransmission form a reinforcing social feedback loop; evidential dependence supplies the residual. This is a proposal-only workspace relationship: the accepted Prime supplies a genuinely instantiated structural prerequisite or superclass, while Communal reinforcement adds domain-specific constraints. The entry does not collapse into that parent because community-mediated repetition loop that substitutes consensus familiarity for independent warrant It also declines a nearby thematic catalog node: the neighbor does not literally subsume the constitutive identity of Communal reinforcement. This explicit assert-and-decline pattern keeps the proposed DAG narrow and prevents a merely thematic edge. The prospective workspace queue contains one strict upward edge to `prime:feedback`. No live DAG mutation is authorized.
- Constructionism (learning theory) Domain-specific is a kind of Feedback
The proposed strict upward parent is `prime:feedback`.prime:feedback is the nearest broader Prime; the source-domain carrier and recognition invariant supply the autonomous residual. This is a proposal-only workspace relationship: the accepted Prime supplies a genuinely instantiated structural prerequisite or superclass, while Constructionism (learning theory) adds domain-specific constraints. The entry does not collapse into that parent because the domain-specific identity fixed by the learners and prior knowledge, concept or capability, artifact and construction medium, project and choice structure, facilitator role, iteration and debugging, audience or sharing, reflection and evidence of learning and transfer are explicit It also declines a nearby thematic catalog node: the neighbor does not literally subsume the constitutive identity of Constructionism (learning theory). This explicit assert-and-decline pattern keeps the proposed DAG narrow and prevents a merely thematic edge. The prospective workspace queue contains one strict upward edge to `prime:feedback`. No live DAG mutation is authorized.
- Data scrubbing Domain-specific is a kind of Feedback
The proposed strict upward parent is `prime:feedback`.Inspection detects degradation and repair restores integrity in a maintenance feedback loop; storage redundancy supplies the residual. This is a proposal-only workspace relationship: the accepted Prime supplies a genuinely instantiated structural prerequisite or superclass, while Data scrubbing adds domain-specific constraints. The entry does not collapse into that parent because periodic latent-error removal that restores redundancy margin before demand access It also declines a nearby thematic catalog node: the neighbor does not literally subsume the constitutive identity of Data scrubbing. This explicit assert-and-decline pattern keeps the proposed DAG narrow and prevents a merely thematic edge. The prospective workspace queue contains one strict upward edge to `prime:feedback`. No live DAG mutation is authorized.
- Delay-gradient congestion control Domain-specific is a kind of Feedback
The proposed strict upward parent is `prime:feedback`.The family literally observes a system output, compares its trend with desired queue behavior, and changes the sender input in response; network delay estimation supplies the domain-specific residual. The edge is proposal-only and points to a frozen prior-baseline Prime. The entry does not collapse into the parent because the feedback loop centered on delay change as a congestion signal, not delay-based congestion control generally, derivative control in the abstract, or a named implementation alone A thematic neighbor is declined whenever it does not literally subsume that rule. The prospective workspace queue contains one strict upward edge to `prime:feedback`. No live DAG mutation is authorized.
- Dunning (process) Domain-specific is a kind of Feedback
The proposed strict upward parent is `prime:feedback`.prime:feedback is the nearest broader Prime; the source-domain carrier and recognition invariant supply the autonomous residual. This is a proposal-only workspace relationship: the accepted Prime supplies a genuinely instantiated structural prerequisite or superclass, while Dunning (process) adds domain-specific constraints. The entry does not collapse into that parent because the domain-specific identity fixed by the creditor and debtor relationship, verified debt and due date, aging state, communication stages and channels, payment and dispute responses, escalation thresholds, jurisdictional restrictions, records and resolution outcome are explicit It also declines a nearby thematic catalog node: the neighbor does not literally subsume the constitutive identity of Dunning (process). This explicit assert-and-decline pattern keeps the proposed DAG narrow and prevents a merely thematic edge. The prospective workspace queue contains one strict upward edge to `prime:feedback`. No live DAG mutation is authorized.
- Dynamic insulation Domain-specific is a kind of Feedback
The proposed strict upward parent is `prime:feedback`.Controlled airflow recovers otherwise lost heat and changes envelope performance; building-physics coupling supplies the residual. This is a proposal-only workspace relationship: the accepted Prime supplies a genuinely instantiated structural prerequisite or superclass, while Dynamic insulation adds domain-specific constraints. The entry does not collapse into that parent because airflow-dependent envelope conductance and integrated ventilation heat recovery It also declines a nearby thematic catalog node: the neighbor does not literally subsume the constitutive identity of Dynamic insulation. This explicit assert-and-decline pattern keeps the proposed DAG narrow and prevents a merely thematic edge. The prospective workspace queue contains one strict upward edge to `prime:feedback`. No live DAG mutation is authorized.
- Emotion-sensitive software Domain-specific is a kind of Feedback
The proposed strict upward parent is `prime:feedback`.prime:feedback is the nearest broader Prime while the source-domain carrier and invariant supply the autonomous residual. This is a proposal-only workspace relationship: the accepted Prime supplies a genuinely instantiated structural prerequisite or superclass, while Emotion-sensitive software adds domain-specific constraints. The entry does not collapse into that parent because the domain-specific identity fixed by the user and use context, intended affect construct and label scheme, signal modalities and sensors, preprocessing and features, model and training population, inference confidence and calibration, adaptive software response, feedback loop, ground truth and validation, demographic and contextual bias, consent privacy security and contestability and non-diagnostic boundary are explicit It also declines a nearby thematic catalog node: the neighbor does not literally subsume the constitutive identity of Emotion-sensitive software. This explicit assert-and-decline pattern keeps the proposed DAG narrow and prevents a merely thematic edge. The prospective workspace queue contains one strict upward edge to `prime:feedback`. No live DAG mutation is authorized.
- Energy monitoring and targeting Domain-specific is a kind of Feedback
The proposed strict upward parent is `prime:feedback`.M&T closes a measurement-comparison-action loop around energy performance; baseline normalization supplies the residual. This is a proposal-only workspace relationship: the accepted Prime supplies a genuinely instantiated structural prerequisite or superclass, while Energy monitoring and targeting adds domain-specific constraints. The entry does not collapse into that parent because a closed operational feedback loop joining energy metering, baseline modeling, exception detection, targeting and verified response It also declines a nearby thematic catalog node: the neighbor does not literally subsume the constitutive identity of Energy monitoring and targeting. This explicit assert-and-decline pattern keeps the proposed DAG narrow and prevents a merely thematic edge. The prospective workspace queue contains one strict upward edge to `prime:feedback`. No live DAG mutation is authorized.
- Epistemic feedback Domain-specific is a kind of Feedback
The proposed strict upward parent is `prime:feedback`.prime:feedback is the nearest broader Prime while the source-domain carrier and invariant supply the autonomous residual. This is a proposal-only workspace relationship: the accepted Prime supplies a genuinely instantiated structural prerequisite or superclass, while Epistemic feedback adds domain-specific constraints. The entry does not collapse into that parent because the domain-specific identity fixed by the target phenomenon and observer, measurement or disclosure, information channel, affected actor or instrument, response mechanism, temporal order, changed data or method, counterfactual no-feedback baseline and evidential consequence are explicit It also declines a nearby thematic catalog node: the neighbor does not literally subsume the constitutive identity of Epistemic feedback. This explicit assert-and-decline pattern keeps the proposed DAG narrow and prevents a merely thematic edge. The prospective workspace queue contains one strict upward edge to `prime:feedback`. No live DAG mutation is authorized.
- Erosion and tectonics Domain-specific is a kind of Feedback
The proposed strict upward parent is `prime:feedback`.prime:feedback is the nearest broader Prime while the source-domain carrier and invariant supply the autonomous residual. This is a proposal-only workspace relationship: the accepted Prime supplies a genuinely instantiated structural prerequisite or superclass, while Erosion and tectonics adds domain-specific constraints. The entry does not collapse into that parent because the domain-specific identity fixed by the tectonic setting and deformation rate, topography and relief, erosion transport and deposition rates, climate and lithology, mass redistribution and isostatic response, stress and fault or exhumation feedback, spatial and temporal scale, observations and models and alternative causal explanations are explicit It also declines a nearby thematic catalog node: the neighbor does not literally subsume the constitutive identity of Erosion and tectonics. This explicit assert-and-decline pattern keeps the proposed DAG narrow and prevents a merely thematic edge. The prospective workspace queue contains one strict upward edge to `prime:feedback`. No live DAG mutation is authorized.
- Error-Correcting Codes with Feedback Domain-specific is a kind of Feedback
receiver-side output returns to change later encoder inputs or stopping.receiver-side output returns to change later encoder inputs or stopping.
- Escape reflex Domain-specific is a kind of Feedback
The proposed strict upward parent is `prime:feedback`.The candidate literally instantiates prime:feedback; its animal_behavior constraints provide the residual. This is a proposal-only workspace relationship: the accepted Prime supplies a genuinely instantiated structural prerequisite or superclass, while Escape reflex adds domain-specific constraints. The entry does not collapse into that parent because A rapid sensorimotor response that detects a threat-like stimulus and initiates stereotyped movement away from it It also declines a nearby thematic catalog node: the neighbor does not literally subsume the constitutive identity of Escape reflex. This explicit assert-and-decline pattern keeps the proposed DAG narrow and prevents a merely thematic edge. The prospective workspace queue contains one strict upward edge to `prime:feedback`. No live DAG mutation is authorized.
- Expenditure cascades Domain-specific is a kind of Feedback
The proposed strict upward parent is `prime:feedback`.The candidate literally instantiates prime:feedback; its behavioral_economics constraints provide the residual. This is a proposal-only workspace relationship: the accepted Prime supplies a genuinely instantiated structural prerequisite or superclass, while Expenditure cascades adds domain-specific constraints. The entry does not collapse into that parent because A consumption spillover in which higher spending by top-income households raises local comparison standards and induces successive spending increases down the income distribution It also declines a nearby thematic catalog node: the neighbor does not literally subsume the constitutive identity of Expenditure cascades. This explicit assert-and-decline pattern keeps the proposed DAG narrow and prevents a merely thematic edge. The prospective workspace queue contains one strict upward edge to `prime:feedback`. No live DAG mutation is authorized.
- Explicit Congestion Notification Domain-specific is a kind of Feedback
The proposed strict upward parent is `prime:feedback`.prime:feedback is the nearest broader Prime; the source domain and invariant supply the autonomous residual. This is a proposal-only workspace relationship: the accepted Prime supplies a genuinely instantiated structural prerequisite or superclass, while Explicit Congestion Notification adds domain-specific constraints. The entry does not collapse into that parent because the domain-specific identity determined by the IP version and transport, negotiation, ECT and CE codepoints, marking queue and policy, receiver feedback, sender response, loss interaction, tunnels and middleboxes, deployment fallback, security and fairness are explicit It also declines a nearby thematic catalog node: the neighbor does not literally subsume the constitutive identity of Explicit Congestion Notification. This explicit assert-and-decline pattern keeps the proposed DAG narrow and prevents a merely thematic edge. The prospective workspace queue contains one strict upward edge to `prime:feedback`. No live DAG mutation is authorized.
- Facial feedback hypothesis Domain-specific is a kind of Feedback
The proposed strict upward parent is `prime:feedback`.prime:feedback is the nearest broader Prime; the source domain and invariant supply the autonomous residual. This is a proposal-only workspace relationship: the accepted Prime supplies a genuinely instantiated structural prerequisite or superclass, while Facial feedback hypothesis adds domain-specific constraints. The entry does not collapse into that parent because the domain-specific identity determined by the participants and context, facial manipulation or naturally occurring expression, emotion outcome, strong or weak hypothesis, awareness and demand controls, timing, measurement validity and replication evidence are explicit It also declines a nearby thematic catalog node: the neighbor does not literally subsume the constitutive identity of Facial feedback hypothesis. This explicit assert-and-decline pattern keeps the proposed DAG narrow and prevents a merely thematic edge. The prospective workspace queue contains one strict upward edge to `prime:feedback`. No live DAG mutation is authorized.
- Full state feedback Domain-specific is a kind of Feedback
The proposed strict upward parent is `prime:feedback`.prime:feedback is the nearest broader Prime; the source domain and invariant supply the residual. This is a proposal-only workspace relationship: the accepted Prime supplies a genuinely instantiated structural prerequisite or superclass, while Full state feedback adds domain-specific constraints. The entry does not collapse into that parent because the domain-specific identity determined by the full state is available or estimated, the plant pair is controllable over the assigned modes, and the chosen gain gives the declared closed-loop eigenvalues It also declines a nearby thematic catalog node: the neighbor does not literally subsume the constitutive identity of Full state feedback. This explicit assert-and-decline pattern keeps the proposed DAG narrow and prevents a merely thematic edge. The prospective workspace queue contains one strict upward edge to `prime:feedback`. No live DAG mutation is authorized.
- Generative adversarial network Domain-specific is a kind of Feedback
The proposed strict upward parent is `prime:feedback`.prime:feedback is the nearest broader Prime while the source-domain carrier and invariant supply the autonomous residual. This is a proposal-only workspace relationship: the accepted Prime supplies a genuinely instantiated structural prerequisite or superclass, while Generative adversarial network adds domain-specific constraints. The entry does not collapse into that parent because the domain-specific identity fixed by the observed data distribution and training sample, latent prior, generator and discriminator or critic architectures, generated distribution, adversarial objective and minimax or alternative loss, alternating optimization, equilibrium interpretation, conditioning when used, convergence diagnostics and sample quality diversity and fidelity, mode collapse instability and evaluation and provenance limits are explicit It also declines a nearby thematic catalog node: the neighbor does not literally subsume the constitutive identity of Generative adversarial network. This explicit assert-and-decline pattern keeps the proposed DAG narrow and prevents a merely thematic edge. The prospective workspace queue contains one strict upward edge to `prime:feedback`. No live DAG mutation is authorized.
- Gold points Domain-specific is a kind of Feedback
The proposed strict upward parent is `prime:feedback`.Gold arbitrage feeds exchange-rate deviations back toward parity; historical convertibility supplies the residual. This is a proposal-only workspace relationship: the accepted Prime supplies a genuinely instantiated structural prerequisite or superclass, while Gold points adds domain-specific constraints. The entry does not collapse into that parent because commodity-arbitrage exchange band characteristic of the international gold standard It also declines a nearby thematic catalog node: the neighbor does not literally subsume the constitutive identity of Gold points. This explicit assert-and-decline pattern keeps the proposed DAG narrow and prevents a merely thematic edge. The prospective workspace queue contains one strict upward edge to `prime:feedback`. No live DAG mutation is authorized.
- Goodwin model (biology) Domain-specific is a kind of Feedback
The proposed strict upward parent is `prime:feedback`.prime:feedback is the nearest broader Prime; the source domain and invariant supply the autonomous residual. This is a proposal-only workspace relationship: the accepted Prime supplies a genuinely instantiated structural prerequisite or superclass, while Goodwin model (biology) adds domain-specific constraints. The entry does not collapse into that parent because the domain-specific identity determined by the biological interpretation and variables, differential equations and units, production and degradation terms, repression function and Hill coefficient, parameter regime, equilibrium and stability, initial conditions and limit-cycle versus closed-orbit claim are explicit It also declines a nearby thematic catalog node: the neighbor does not literally subsume the constitutive identity of Goodwin model (biology). This explicit assert-and-decline pattern keeps the proposed DAG narrow and prevents a merely thematic edge. The prospective workspace queue contains one strict upward edge to `prime:feedback`. No live DAG mutation is authorized.
- Ground proximity warning system Domain-specific is a kind of Feedback
The proposed strict upward parent is `prime:feedback`.The system feeds detected terrain hazard back to flight crew action; aviation alert envelopes supply the residual. This is a proposal-only workspace relationship: the accepted Prime supplies a genuinely instantiated structural prerequisite or superclass, while Ground proximity warning system adds domain-specific constraints. The entry does not collapse into that parent because last-line terrain-collision warning based on flight-envelope pattern recognition It also declines a nearby thematic catalog node: the neighbor does not literally subsume the constitutive identity of Ground proximity warning system. This explicit assert-and-decline pattern keeps the proposed DAG narrow and prevents a merely thematic edge. The prospective workspace queue contains one strict upward edge to `prime:feedback`. No live DAG mutation is authorized.
- Hyperhydricity Domain-specific is a kind of Feedback
The proposed strict upward parent is `prime:feedback`.Water balance, vessel atmosphere, hormones, and tissue development can reinforce the abnormal state; the defined plant-culture syndrome supplies the residual. This is a proposal-only workspace relationship: the accepted Prime supplies a genuinely instantiated structural prerequisite or superclass, while Hyperhydricity adds domain-specific constraints. The entry does not collapse into that parent because the linked in-vitro excessive-hydration syndrome and impaired structural maturation It also declines a nearby thematic catalog node: the neighbor does not literally subsume the constitutive identity of Hyperhydricity. This explicit assert-and-decline pattern keeps the proposed DAG narrow and prevents a merely thematic edge. The prospective workspace queue contains one strict upward edge to `prime:feedback`. No live DAG mutation is authorized.
- Ice–albedo feedback Domain-specific is a kind of Feedback
The proposed strict upward parent is `prime:feedback`.prime:feedback is the nearest broader Prime; the source domain and invariant supply the autonomous residual. This is a proposal-only workspace relationship: the accepted Prime supplies a genuinely instantiated structural prerequisite or superclass, while Ice–albedo feedback adds domain-specific constraints. The entry does not collapse into that parent because the domain-specific identity determined by the geographic and temporal domain, snow or ice carrier, reference temperature perturbation, albedo contrast and spectral convention, incoming shortwave flux, cover response, radiative forcing, feedback sign and strength, cloud and ocean interactions, seasonality, model or observational evidence, and saturation limits are explicit It also declines a nearby thematic catalog node: the neighbor does not literally subsume the constitutive identity of Ice–albedo feedback. This explicit assert-and-decline pattern keeps the proposed DAG narrow and prevents a merely thematic edge. The prospective workspace queue contains one strict upward edge to `prime:feedback`. No live DAG mutation is authorized.
- Inertia wheel pendulum Domain-specific is a kind of Feedback
The proposed strict upward parent is `prime:feedback`.prime:feedback is the nearest broader Prime; the source domain and invariant supply the autonomous residual. This is a proposal-only workspace relationship: the accepted Prime supplies a genuinely instantiated structural prerequisite or superclass, while Inertia wheel pendulum adds domain-specific constraints. The entry does not collapse into that parent because the domain-specific identity determined by the pendulum and wheel inertias, coordinates, actuator torque, gravity, coupled equations, sensing, control objective, saturation and distinction from gyroscopic action are explicit It also declines a nearby thematic catalog node: the neighbor does not literally subsume the constitutive identity of Inertia wheel pendulum. This explicit assert-and-decline pattern keeps the proposed DAG narrow and prevents a merely thematic edge. The prospective workspace queue contains one strict upward edge to `prime:feedback`. No live DAG mutation is authorized.
- Instructional rounds Domain-specific is a kind of Feedback
The proposed strict upward parent is `prime:feedback`.The candidate literally instantiates prime:feedback; its educational_improvement restrictions supply the domain-specific residual. This is a proposal-only workspace relationship: the accepted Prime supplies a genuinely instantiated structural prerequisite or superclass, while Instructional rounds adds domain-specific constraints. The entry does not collapse into that parent because A collaborative school-improvement practice in which educators observe multiple classrooms around a shared problem of practice, synthesize low-inference evidence and identify a next level of work It also declines a nearby thematic catalog node: the neighbor does not literally subsume the constitutive identity of Instructional rounds. This explicit assert-and-decline pattern keeps the proposed DAG narrow and prevents a merely thematic edge. The prospective workspace queue contains one strict upward edge to `prime:feedback`. No live DAG mutation is authorized.
- Interpersonal gap Domain-specific is a kind of Feedback
The proposed strict upward parent is `prime:feedback`.Feedback between communicators reveals and can correct gaps across the communication chain; interpersonal stage distinctions supply the residual. This is a proposal-only workspace relationship: the accepted Prime supplies a genuinely instantiated structural prerequisite or superclass, while Interpersonal gap adds domain-specific constraints. The entry does not collapse into that parent because stagewise map of interpersonal misunderstanding and repair through descriptive feedback It also declines a nearby thematic catalog node: the neighbor does not literally subsume the constitutive identity of Interpersonal gap. This explicit assert-and-decline pattern keeps the proposed DAG narrow and prevents a merely thematic edge. The prospective workspace queue contains one strict upward edge to `prime:feedback`. No live DAG mutation is authorized.
- L4S Domain-specific is a kind of Feedback
**Feedback** is the strict parent because L4S closes a measurable loop in which bottleneck queue growth changes ECN signals, signals change sending rate, and rate changes later queue growth.Queueing and Interface are important neighbors but do not alone capture the control-loop identity. The prospective workspace queue contains one strict upward edge to `prime:feedback`. No live DAG mutation is authorized.
- Law of effect Domain-specific is a kind of Feedback
The proposed strict upward parent is `prime:feedback`.prime:feedback is the nearest broader Prime while the source-domain carrier and invariant supply the autonomous residual. This is a proposal-only workspace relationship: the accepted Prime supplies a genuinely instantiated structural prerequisite or superclass, while Law of effect adds domain-specific constraints. The entry does not collapse into that parent because the domain-specific identity fixed by the organism and situation or stimulus context, candidate response, immediate or delayed consequence, satisfying reinforcing or discomforting punishing classification, change in response probability or bond strength, repetition and learning curve, temporal contiguity and contingency, revised historical formulations and distinction from Pavlovian association and purely cognitive expectation are explicit It also declines a nearby thematic catalog node: the neighbor does not literally subsume the constitutive identity of Law of effect. This explicit assert-and-decline pattern keeps the proposed DAG narrow and prevents a merely thematic edge. The prospective workspace queue contains one strict upward edge to `prime:feedback`. No live DAG mutation is authorized.
- Lyapunov redesign Domain-specific is a kind of Feedback
The proposed strict upward parent is `prime:feedback`.prime:feedback is the nearest broader Prime; the source-domain carrier and recognition invariant supply the autonomous residual. This is a proposal-only workspace relationship: the accepted Prime supplies a genuinely instantiated structural prerequisite or superclass, while Lyapunov redesign adds domain-specific constraints. The entry does not collapse into that parent because the domain-specific identity fixed by the nonlinear plant and input channel, nominal model and stabilizing law, Lyapunov function and domain, uncertainty class and bound, redesign term, derivative inequality, continuity or chattering treatment and resulting stability claim are explicit It also declines a nearby thematic catalog node: the neighbor does not literally subsume the constitutive identity of Lyapunov redesign. This explicit assert-and-decline pattern keeps the proposed DAG narrow and prevents a merely thematic edge. The prospective workspace queue contains one strict upward edge to `prime:feedback`. No live DAG mutation is authorized.
- Medullary ischemic reflex Domain-specific is a kind of Feedback
The proposed strict upward parent is `prime:feedback`.Falling cerebral perfusion activates a pressure-restoring feedback response; brainstem emergency physiology supplies the residual. This is a proposal-only workspace relationship: the accepted Prime supplies a genuinely instantiated structural prerequisite or superclass, while Medullary ischemic reflex adds domain-specific constraints. The entry does not collapse into that parent because last-resort cerebral-perfusion feedback with extreme systemic vasoconstriction It also declines a nearby thematic catalog node: the neighbor does not literally subsume the constitutive identity of Medullary ischemic reflex. This explicit assert-and-decline pattern keeps the proposed DAG narrow and prevents a merely thematic edge. The prospective workspace queue contains one strict upward edge to `prime:feedback`. No live DAG mutation is authorized.
- Mix automation Domain-specific is a kind of Feedback
The proposed strict upward parent is `prime:feedback`.prime:feedback is the nearest broader Prime; the source domain and invariant supply the autonomous residual. This is a proposal-only workspace relationship: the accepted Prime supplies a genuinely instantiated structural prerequisite or superclass, while Mix automation adds domain-specific constraints. The entry does not collapse into that parent because the domain-specific identity determined by the session timeline and synchronization, automated parameters, write and playback modes, interpolation, precedence, editing, recall state and rendered result are explicit It also declines a nearby thematic catalog node: the neighbor does not literally subsume the constitutive identity of Mix automation. This explicit assert-and-decline pattern keeps the proposed DAG narrow and prevents a merely thematic edge. The prospective workspace queue contains one strict upward edge to `prime:feedback`. No live DAG mutation is authorized.
- Natural nuclear fission reactor Domain-specific is a kind of Feedback
The proposed strict upward parent is `prime:feedback`.prime:feedback is the nearest broader Prime; the source domain and invariant supply the autonomous residual. This is a proposal-only workspace relationship: the accepted Prime supplies a genuinely instantiated structural prerequisite or superclass, while Natural nuclear fission reactor adds domain-specific constraints. The entry does not collapse into that parent because the domain-specific identity determined by the deposit and geologic age, uranium grade and historical isotope abundance, geometry, moderator and neutron economy, criticality evidence, fission-product isotope balances, heat and water feedback, duration, migration, uncertainty, and distinction from engineered reactors are explicit It also declines a nearby thematic catalog node: the neighbor does not literally subsume the constitutive identity of Natural nuclear fission reactor. This explicit assert-and-decline pattern keeps the proposed DAG narrow and prevents a merely thematic edge. The prospective workspace queue contains one strict upward edge to `prime:feedback`. No live DAG mutation is authorized.
- Numerical response Domain-specific is a kind of Feedback
The proposed strict upward parent is `prime:feedback`.prime:feedback is the nearest broader Prime while the source-domain carrier and invariant supply the autonomous residual. This is a proposal-only workspace relationship: the accepted Prime supplies a genuinely instantiated structural prerequisite or superclass, while Numerical response adds domain-specific constraints. The entry does not collapse into that parent because the domain-specific identity fixed by the predator and prey populations, prey density trajectory, predator density response, demographic birth death and survival components, aggregational immigration and emigration, lag and timescale, functional-response relation and density-dependence and environmental confounders are explicit It also declines a nearby thematic catalog node: the neighbor does not literally subsume the constitutive identity of Numerical response. This explicit assert-and-decline pattern keeps the proposed DAG narrow and prevents a merely thematic edge. The prospective workspace queue contains one strict upward edge to `prime:feedback`. No live DAG mutation is authorized.
- Oligopolistic reaction Domain-specific is a kind of Feedback
The proposed strict upward parent is `prime:feedback`.The candidate literally instantiates prime:feedback; its international_business constraints provide the residual. This is a proposal-only workspace relationship: the accepted Prime supplies a genuinely instantiated structural prerequisite or superclass, while Oligopolistic reaction adds domain-specific constraints. The entry does not collapse into that parent because A foreign-direct-investment theory in which firms follow rivals into overseas markets to preserve competitive balance under oligopoly It also declines a nearby thematic catalog node: the neighbor does not literally subsume the constitutive identity of Oligopolistic reaction. This explicit assert-and-decline pattern keeps the proposed DAG narrow and prevents a merely thematic edge. The prospective workspace queue contains one strict upward edge to `prime:feedback`. No live DAG mutation is authorized.
- P-chart Domain-specific is a kind of Feedback
The proposed strict upward parent is `prime:feedback`.The chart feeds statistical process evidence into investigation and correction; binomial proportions supply the residual. This is a proposal-only workspace relationship: the accepted Prime supplies a genuinely instantiated structural prerequisite or superclass, while P-chart adds domain-specific constraints. The entry does not collapse into that parent because proportion-nonconforming surveillance with binomially scaled limits It also declines a nearby thematic catalog node: the neighbor does not literally subsume the constitutive identity of P-chart. This explicit assert-and-decline pattern keeps the proposed DAG narrow and prevents a merely thematic edge. The prospective workspace queue contains one strict upward edge to `prime:feedback`. No live DAG mutation is authorized.
- Parabolic SAR Domain-specific is a kind of Feedback
The proposed strict upward parent is `prime:feedback`.prime:feedback is the nearest broader Prime; the source domain and invariant supply the autonomous residual. This is a proposal-only workspace relationship: the accepted Prime supplies a genuinely instantiated structural prerequisite or superclass, while Parabolic SAR adds domain-specific constraints. The entry does not collapse into that parent because the domain-specific identity determined by market and bar data, trend initialization, extreme point, acceleration schedule and cap, reversal and gap rules, missing data, price adjustment, and evaluation protocol are explicit It also declines a nearby thematic catalog node: the neighbor does not literally subsume the constitutive identity of Parabolic SAR. This explicit assert-and-decline pattern keeps the proposed DAG narrow and prevents a merely thematic edge. The prospective workspace queue contains one strict upward edge to `prime:feedback`. No live DAG mutation is authorized.
- Paradox of toil Domain-specific is a kind of Feedback
The proposed strict upward parent is `prime:feedback`.A wage-price-real-rate feedback reverses the partial-equilibrium effect of labor supply; lower-bound macroeconomics supplies the residual. This is a proposal-only workspace relationship: the accepted Prime supplies a genuinely instantiated structural prerequisite or superclass, while Paradox of toil adds domain-specific constraints. The entry does not collapse into that parent because general-equilibrium reversal from individual labor willingness to lower collective employment in a liquidity trap It also declines a nearby thematic catalog node: the neighbor does not literally subsume the constitutive identity of Paradox of toil. This explicit assert-and-decline pattern keeps the proposed DAG narrow and prevents a merely thematic edge. The prospective workspace queue contains one strict upward edge to `prime:feedback`. No live DAG mutation is authorized.
- PID controller Domain-specific is a kind of Feedback
The proposed strict upward parent is `prime:feedback`.The candidate literally instantiates prime:feedback; its control_engineering constraints provide the residual. This is a proposal-only workspace relationship: the accepted Prime supplies a genuinely instantiated structural prerequisite or superclass, while PID controller adds domain-specific constraints. The entry does not collapse into that parent because A feedback controller that combines proportional response to current error, integral response to accumulated error and derivative response to error trend It also declines a nearby thematic catalog node: the neighbor does not literally subsume the constitutive identity of PID controller. This explicit assert-and-decline pattern keeps the proposed DAG narrow and prevents a merely thematic edge. The prospective workspace queue contains one strict upward edge to `prime:feedback`. No live DAG mutation is authorized.
- Plant–soil feedback Domain-specific is a kind of Feedback
The proposed strict upward parent is `prime:feedback`.The candidate literally instantiates prime:feedback; its plant_ecology constraints provide the residual. This is a proposal-only workspace relationship: the accepted Prime supplies a genuinely instantiated structural prerequisite or superclass, while Plant–soil feedback adds domain-specific constraints. The entry does not collapse into that parent because A reciprocal ecological process in which plants modify soil biotic or abiotic conditions and those changes alter subsequent plant performance It also declines a nearby thematic catalog node: the neighbor does not literally subsume the constitutive identity of Plant–soil feedback. This explicit assert-and-decline pattern keeps the proposed DAG narrow and prevents a merely thematic edge. The prospective workspace queue contains one strict upward edge to `prime:feedback`. No live DAG mutation is authorized.
- Power-knowledge Domain-specific is a kind of Feedback
The proposed strict upward parent is `prime:feedback`.prime:feedback is the nearest broader Prime while the source-domain carrier and invariant supply the autonomous residual. This is a proposal-only workspace relationship: the accepted Prime supplies a genuinely instantiated structural prerequisite or superclass, while Power-knowledge adds domain-specific constraints. The entry does not collapse into that parent because the domain-specific identity fixed by the historical discourse and institutional field, subjects and objects of knowledge, practices of observation classification examination and documentation, experts and authorities, truth regime and criteria, disciplinary or governmental power relations, production of categories and subjectivities, feedback between knowledge and intervention, resistance and counterknowledge and genealogy as method are explicit It also declines a nearby thematic catalog node: the neighbor does not literally subsume the constitutive identity of Power-knowledge. This explicit assert-and-decline pattern keeps the proposed DAG narrow and prevents a merely thematic edge. The prospective workspace queue contains one strict upward edge to `prime:feedback`. No live DAG mutation is authorized.
- Promoting adversaries Domain-specific is a kind of Feedback
The proposed strict upward parent is `prime:feedback`.The candidate literally instantiates prime:feedback; its strategic_interaction constraints provide the residual. This is a proposal-only workspace relationship: the accepted Prime supplies a genuinely instantiated structural prerequisite or superclass, while Promoting adversaries adds domain-specific constraints. The entry does not collapse into that parent because A mutually reinforcing rivalry in which opposing organizations gain attention, legitimacy or resources by attacking one another while avoiding decisive defeat It also declines a nearby thematic catalog node: the neighbor does not literally subsume the constitutive identity of Promoting adversaries. This explicit assert-and-decline pattern keeps the proposed DAG narrow and prevents a merely thematic edge. The prospective workspace queue contains one strict upward edge to `prime:feedback`. No live DAG mutation is authorized.
- Pygmalion effect Domain-specific is a kind of Feedback
The proposed strict upward parent is `prime:feedback`.Expectations alter treatment, which changes performance and can confirm the expectation; social interaction supplies the residual. This is a proposal-only workspace relationship: the accepted Prime supplies a genuinely instantiated structural prerequisite or superclass, while Pygmalion effect adds domain-specific constraints. The entry does not collapse into that parent because interpersonal positive expectancy loop studied in classrooms and organizations It also declines a nearby thematic catalog node: the neighbor does not literally subsume the constitutive identity of Pygmalion effect. This explicit assert-and-decline pattern keeps the proposed DAG narrow and prevents a merely thematic edge. The prospective workspace queue contains one strict upward edge to `prime:feedback`. No live DAG mutation is authorized.
- Quantum master equation Domain-specific is a kind of Feedback
The proposed strict upward parent is `prime:feedback`.Environmental coupling feeds into reduced quantum evolution; open-system dissipation supplies the residual. This is a proposal-only workspace relationship: the accepted Prime supplies a genuinely instantiated structural prerequisite or superclass, while Quantum master equation adds domain-specific constraints. The entry does not collapse into that parent because reduced-state dynamics combining quantum coherence with open-system irreversibility It also declines a nearby thematic catalog node: the neighbor does not literally subsume the constitutive identity of Quantum master equation. This explicit assert-and-decline pattern keeps the proposed DAG narrow and prevents a merely thematic edge. The prospective workspace queue contains one strict upward edge to `prime:feedback`. No live DAG mutation is authorized.
- Rat running Domain-specific is a kind of Feedback
The proposed strict upward parent is `prime:feedback`.prime:feedback is the nearest broader Prime while the source-domain carrier and invariant supply the autonomous residual. This is a proposal-only workspace relationship: the accepted Prime supplies a genuinely instantiated structural prerequisite or superclass, while Rat running adds domain-specific constraints. The entry does not collapse into that parent because the domain-specific identity fixed by the origin destination and congested primary route, alternative local street or property path, network hierarchy and intended use, perceived travel-time advantage, driver route choice, navigation information, through-traffic volume, impacts on residents pedestrians and local access, legality and access restrictions and policy responses and displacement effects are explicit It also declines a nearby thematic catalog node: the neighbor does not literally subsume the constitutive identity of Rat running. This explicit assert-and-decline pattern keeps the proposed DAG narrow and prevents a merely thematic edge. The prospective workspace queue contains one strict upward edge to `prime:feedback`. No live DAG mutation is authorized.
- Reflective practice Domain-specific is a kind of Feedback
The proposed strict upward parent is `prime:feedback`.The candidate literally instantiates prime:feedback; its professional_learning constraints provide the residual. This is a proposal-only workspace relationship: the accepted Prime supplies a genuinely instantiated structural prerequisite or superclass, while Reflective practice adds domain-specific constraints. The entry does not collapse into that parent because A disciplined cycle of examining one's actions, assumptions, emotions and outcomes to improve professional judgment and future practice It also declines a nearby thematic catalog node: the neighbor does not literally subsume the constitutive identity of Reflective practice. This explicit assert-and-decline pattern keeps the proposed DAG narrow and prevents a merely thematic edge. The prospective workspace queue contains one strict upward edge to `prime:feedback`. No live DAG mutation is authorized.
- Reflexive modernization Domain-specific is a kind of Feedback
The proposed strict upward parent is `prime:feedback`.Modernization's outputs feed back to destabilize and reorganize its institutions; reflexive sociology supplies the residual. This is a proposal-only workspace relationship: the accepted Prime supplies a genuinely instantiated structural prerequisite or superclass, while Reflexive modernization adds domain-specific constraints. The entry does not collapse into that parent because self-transforming phase of modernity driven by manufactured risk and institutional side effects It also declines a nearby thematic catalog node: the neighbor does not literally subsume the constitutive identity of Reflexive modernization. This explicit assert-and-decline pattern keeps the proposed DAG narrow and prevents a merely thematic edge. The prospective workspace queue contains one strict upward edge to `prime:feedback`. No live DAG mutation is authorized.
- Results-Based Management Domain-specific is a kind of Feedback
**`feedback` — instantiates.** Observed results and context are returned to planning, delivery, and resource decisions.A report that cannot influence a later input leaves the loop open.
- SEED-SCALE Domain-specific is a kind of Feedback
The proposed strict upward parent is `prime:feedback`.prime:feedback is the nearest broader Prime; the source-domain carrier and recognition invariant supply the autonomous residual. This is a proposal-only workspace relationship: the accepted Prime supplies a genuinely instantiated structural prerequisite or superclass, while SEED-SCALE adds domain-specific constraints. The entry does not collapse into that parent because the domain-specific identity fixed by the community and desired change, locally owned seed, self-evaluation evidence, behavior and human-energy mechanism, partnership roles, adaptation process, scaling pathway, equity and durability outcomes are explicit It also declines a nearby thematic catalog node: the neighbor does not literally subsume the constitutive identity of SEED-SCALE. This explicit assert-and-decline pattern keeps the proposed DAG narrow and prevents a merely thematic edge. The prospective workspace queue contains one strict upward edge to `prime:feedback`. No live DAG mutation is authorized.
- Servo (radio control) Domain-specific is a kind of Feedback
The proposed strict upward parent is `prime:feedback`.prime:feedback is the nearest broader Prime; the source domain and invariant supply the residual. This is a proposal-only workspace relationship: the accepted Prime supplies a genuinely instantiated structural prerequisite or superclass, while Servo (radio control) adds domain-specific constraints. The entry does not collapse into that parent because the domain-specific identity determined by the device closes an internal position loop between command, sensor, controller, motor, and output under the declared interface convention It also declines a nearby thematic catalog node: the neighbor does not literally subsume the constitutive identity of Servo (radio control). This explicit assert-and-decline pattern keeps the proposed DAG narrow and prevents a merely thematic edge. The prospective workspace queue contains one strict upward edge to `prime:feedback`. No live DAG mutation is authorized.
- Sethi model Domain-specific is a kind of Feedback
The proposed strict upward parent is `prime:feedback`.The candidate literally instantiates prime:feedback; its marketing_dynamics constraints provide the residual. This is a proposal-only workspace relationship: the accepted Prime supplies a genuinely instantiated structural prerequisite or superclass, while Sethi model adds domain-specific constraints. The entry does not collapse into that parent because A dynamic advertising model in which sales growth depends positively on advertising applied to the unsold market and negatively on forgetting or competitive decay It also declines a nearby thematic catalog node: the neighbor does not literally subsume the constitutive identity of Sethi model. This explicit assert-and-decline pattern keeps the proposed DAG narrow and prevents a merely thematic edge. The prospective workspace queue contains one strict upward edge to `prime:feedback`. No live DAG mutation is authorized.
- Shewhart individuals control chart Domain-specific is a kind of Feedback
The proposed strict upward parent is `prime:feedback`.The chart detects process change to trigger investigation and correction; single-observation SPC supplies the residual. This is a proposal-only workspace relationship: the accepted Prime supplies a genuinely instantiated structural prerequisite or superclass, while Shewhart individuals control chart adds domain-specific constraints. The entry does not collapse into that parent because single-observation process monitoring with dispersion estimated from successive differences It also declines a nearby thematic catalog node: the neighbor does not literally subsume the constitutive identity of Shewhart individuals control chart. This explicit assert-and-decline pattern keeps the proposed DAG narrow and prevents a merely thematic edge. The prospective workspace queue contains one strict upward edge to `prime:feedback`. No live DAG mutation is authorized.
- Sliding mode control Domain-specific is a kind of Feedback
The proposed strict upward parent is `prime:feedback`.The candidate literally instantiates prime:feedback; its control_theory restrictions supply the domain-specific residual. This is a proposal-only workspace relationship: the accepted Prime supplies a genuinely instantiated structural prerequisite or superclass, while Sliding mode control adds domain-specific constraints. The entry does not collapse into that parent because A nonlinear variable-structure control method using discontinuous feedback to drive trajectories onto a designed switching manifold and maintain reduced-order motion along it It also declines a nearby thematic catalog node: the neighbor does not literally subsume the constitutive identity of Sliding mode control. This explicit assert-and-decline pattern keeps the proposed DAG narrow and prevents a merely thematic edge. The prospective workspace queue contains one strict upward edge to `prime:feedback`. No live DAG mutation is authorized.
- Social Media Language Learning Domain-specific is a kind of Feedback
The proposed strict upward parent is `prime:feedback`.prime:feedback is the nearest broader Prime; the source-domain carrier and recognition invariant supply the autonomous residual. This is a proposal-only workspace relationship: the accepted Prime supplies a genuinely instantiated structural prerequisite or superclass, while Social Media Language Learning adds domain-specific constraints. The entry does not collapse into that parent because the domain-specific identity fixed by the target language and learner group, platform and affordances, formal or informal setting, interaction partners, tasks and multimodal modes, feedback, privacy and moderation conditions and learning evidence are explicit It also declines a nearby thematic catalog node: the neighbor does not literally subsume the constitutive identity of Social Media Language Learning. This explicit assert-and-decline pattern keeps the proposed DAG narrow and prevents a merely thematic edge. The prospective workspace queue contains one strict upward edge to `prime:feedback`. No live DAG mutation is authorized.
- Strategic energy management Domain-specific is a kind of Feedback
The proposed strict upward parent is `prime:feedback`.prime:feedback is the nearest broader Prime; the source domain and invariant supply the autonomous residual. This is a proposal-only workspace relationship: the accepted Prime supplies a genuinely instantiated structural prerequisite or superclass, while Strategic energy management adds domain-specific constraints. The entry does not collapse into that parent because the domain-specific identity determined by the organizational and facility boundary, energy sources and significant uses, baseline and normalization, policy and objectives, roles, metering, opportunity selection, operational controls, verification, persistence, review cadence, and claimed savings are explicit It also declines a nearby thematic catalog node: the neighbor does not literally subsume the constitutive identity of Strategic energy management. This explicit assert-and-decline pattern keeps the proposed DAG narrow and prevents a merely thematic edge. The prospective workspace queue contains one strict upward edge to `prime:feedback`. No live DAG mutation is authorized.
- System dynamics Domain-specific is a kind of Feedback
The proposed strict upward parent is `prime:feedback`.Feedback among accumulations and rates is the methodology's organizing mechanism; simulation practice supplies the residual. This is a proposal-only workspace relationship: the accepted Prime supplies a genuinely instantiated structural prerequisite or superclass, while System dynamics adds domain-specific constraints. The entry does not collapse into that parent because feedback-centered continuous-time modeling of endogenous system behavior It also declines a nearby thematic catalog node: the neighbor does not literally subsume the constitutive identity of System dynamics. This explicit assert-and-decline pattern keeps the proposed DAG narrow and prevents a merely thematic edge. The prospective workspace queue contains one strict upward edge to `prime:feedback`. No live DAG mutation is authorized.
- Tampering (quality control) Domain-specific is a kind of Feedback
The proposed strict upward parent is `prime:feedback`.prime:feedback is the nearest broader Prime; the source-domain carrier and recognition invariant supply the autonomous residual. This is a proposal-only workspace relationship: the accepted Prime supplies a genuinely instantiated structural prerequisite or superclass, while Tampering (quality control) adds domain-specific constraints. The entry does not collapse into that parent because the domain-specific identity fixed by the process and quality characteristic, stable baseline and common-cause model, observation and adjustment rule, control limits or absence, sequence of interventions and before-after variation or out-of-specification rate are explicit It also declines a nearby thematic catalog node: the neighbor does not literally subsume the constitutive identity of Tampering (quality control). This explicit assert-and-decline pattern keeps the proposed DAG narrow and prevents a merely thematic edge. The prospective workspace queue contains one strict upward edge to `prime:feedback`. No live DAG mutation is authorized.
- Taylor rule Domain-specific is a kind of Feedback
The proposed strict upward parent is `prime:feedback`.prime:feedback is the nearest broader Prime; the source domain and invariant supply the autonomous residual. This is a proposal-only workspace relationship: the accepted Prime supplies a genuinely instantiated structural prerequisite or superclass, while Taylor rule adds domain-specific constraints. The entry does not collapse into that parent because the domain-specific identity determined by the central bank and period, policy rate, inflation measure and target, output and potential-output estimate, equilibrium real rate, coefficients, lag or forecast timing, smoothing, effective lower bound, data revisions, normative versus descriptive use, and uncertainty are explicit It also declines a nearby thematic catalog node: the neighbor does not literally subsume the constitutive identity of Taylor rule. This explicit assert-and-decline pattern keeps the proposed DAG narrow and prevents a merely thematic edge. The prospective workspace queue contains one strict upward edge to `prime:feedback`. No live DAG mutation is authorized.
- TCP congestion control Domain-specific is a kind of Feedback
The proposed strict upward parent is `prime:feedback`.prime:feedback is the nearest broader Prime while the source-domain invariant supplies the autonomous residual. This is a proposal-only workspace relationship: the accepted Prime supplies a genuinely instantiated structural prerequisite or superclass, while TCP congestion control adds domain-specific constraints. The entry does not collapse into that parent because the domain-specific identity fixed by the TCP and algorithm version, sender and path, congestion and receive windows, acknowledgment and loss signals, slow-start threshold, increase and decrease rules, recovery state, timers, fairness and performance conditions are explicit It also declines a nearby thematic catalog node: the neighbor does not literally subsume the constitutive identity of TCP congestion control. This explicit assert-and-decline pattern keeps the proposed DAG narrow and prevents a merely thematic edge. The prospective workspace queue contains one strict upward edge to `prime:feedback`. No live DAG mutation is authorized.
- Traced monoidal category Domain-specific is a kind of Feedback
The proposed strict upward parent is `prime:feedback`.prime:feedback is the nearest broader Prime; the source domain and invariant supply the autonomous residual. This is a proposal-only workspace relationship: the accepted Prime supplies a genuinely instantiated structural prerequisite or superclass, while Traced monoidal category adds domain-specific constraints. The entry does not collapse into that parent because the domain-specific identity determined by the category and monoidal product, unit and associators, symmetry or braiding assumptions, trace family and typed domain, naturality in input and output, dinaturality in feedback object, vanishing, superposing and yanking equations, diagram convention and examples are explicit It also declines a nearby thematic catalog node: the neighbor does not literally subsume the constitutive identity of Traced monoidal category. This explicit assert-and-decline pattern keeps the proposed DAG narrow and prevents a merely thematic edge. The prospective workspace queue contains one strict upward edge to `prime:feedback`. No live DAG mutation is authorized.
- Tracking signal Domain-specific is a kind of Feedback
The proposed strict upward parent is `prime:feedback`.prime:feedback is the nearest broader Prime; the source domain and invariant supply the autonomous residual. This is a proposal-only workspace relationship: the accepted Prime supplies a genuinely instantiated structural prerequisite or superclass, while Tracking signal adds domain-specific constraints. The entry does not collapse into that parent because the domain-specific identity determined by forecast target, horizon, error sign, update frequency, numerator, scale denominator, initialization, threshold, missing data, interventions, and false-alarm policy are explicit It also declines a nearby thematic catalog node: the neighbor does not literally subsume the constitutive identity of Tracking signal. This explicit assert-and-decline pattern keeps the proposed DAG narrow and prevents a merely thematic edge. The prospective workspace queue contains one strict upward edge to `prime:feedback`. No live DAG mutation is authorized.
- Transformation design Domain-specific is a kind of Feedback
The proposed strict upward parent is `prime:feedback`.prime:feedback is the nearest broader Prime; the source-domain carrier and recognition invariant supply the autonomous residual. This is a proposal-only workspace relationship: the accepted Prime supplies a genuinely instantiated structural prerequisite or superclass, while Transformation design adds domain-specific constraints. The entry does not collapse into that parent because the domain-specific identity fixed by the affected system and stakeholders, desired behavioral and structural change, participation method, holistic system model, prototype, feedback evidence, scaling path and durability criterion are explicit It also declines a nearby thematic catalog node: the neighbor does not literally subsume the constitutive identity of Transformation design. This explicit assert-and-decline pattern keeps the proposed DAG narrow and prevents a merely thematic edge. The prospective workspace queue contains one strict upward edge to `prime:feedback`. No live DAG mutation is authorized.
- Tropical cyclone Domain-specific is a kind of Feedback
The proposed strict upward parent is `prime:feedback`.Latent heating, pressure fall and surface inflow create the storm's amplifying heat-engine feedback; tropical rotation supplies the residual. This is a proposal-only workspace relationship: the accepted Prime supplies a genuinely instantiated structural prerequisite or superclass, while Tropical cyclone adds domain-specific constraints. The entry does not collapse into that parent because ocean-fueled warm-core cyclone distinct from frontal low-pressure systems It also declines a nearby thematic catalog node: the neighbor does not literally subsume the constitutive identity of Tropical cyclone. This explicit assert-and-decline pattern keeps the proposed DAG narrow and prevents a merely thematic edge. The prospective workspace queue contains one strict upward edge to `prime:feedback`. No live DAG mutation is authorized.
- Video feedback Domain-specific is a kind of Feedback
The proposed strict upward parent is `prime:feedback`.prime:feedback is the nearest broader Prime while the source-domain invariant supplies the autonomous residual. This is a proposal-only workspace relationship: the accepted Prime supplies a genuinely instantiated structural prerequisite or superclass, while Video feedback adds domain-specific constraints. The entry does not collapse into that parent because the domain-specific identity fixed by the camera and display or virtual loop, optical alignment, frame delay, gain and exposure, geometric and color transformation, initialization, stability or saturation and recording context are explicit It also declines a nearby thematic catalog node: the neighbor does not literally subsume the constitutive identity of Video feedback. This explicit assert-and-decline pattern keeps the proposed DAG narrow and prevents a merely thematic edge. The prospective workspace queue contains one strict upward edge to `prime:feedback`. No live DAG mutation is authorized.
- Backpressure Prime is a kind of Feedback
Backpressure is a specific negative-feedback loop whose controlled variable is capacity-headroom and whose effect is to throttle production toward the bottleneck rate — a specialization of feedback (the genus, which also covers positive/non-throttling loops).Feedback supplies the genus: Outputs influence inputs. Backpressure preserves that general structure while adding its differentia: A return signal from a downstream stage throttles upstream production to its own capacity, converting a one-way push into a two-way conversation that holds the system at the bottleneck's throughput instead of accumulating hidden queue debt. The parent can occur without those added commitments, whereas removing the parent structure leaves no basis for classifying the child as this subtype. That asymmetry establishes subsumption rather than mere association.
- Broken Windows Theory Prime is a kind of, typical Feedback
Broken windows is a positive-feedback signal-inference-response loop with a density threshold (same algebra as an epidemic R0-crossing) — a specialization of feedback restricted to agents inferring a hidden enforcement-cost regime from observable disorder residue.Feedback supplies the genus: Outputs influence inputs. Broken Windows Theory preserves that general structure while adding its differentia: Visible unrepaired disorder signals weakened enforcement, lowering the perceived cost of further violation in a self-reinforcing cascade. The parent can occur without those added commitments, whereas removing the parent structure leaves no basis for classifying the child as this subtype. That asymmetry establishes subsumption rather than mere association. The typical qualifier limits the claim to the characteristic route, not a constitutive requirement of every instance; exceptions must retain the child's identity through another mechanism.
- Discrepancy-Driven Correction Prime is a kind of Feedback
'feedback's goal-directed specialisation — feedback structured around an explicit target and a signed gap that the action is keyed to.' A strict subspecies of feedback (which has no target).Feedback supplies the genus: Outputs influence inputs. Discrepancy-Driven Correction preserves that general structure while adding its differentia: Iteratively close the signed gap between a target and an observation. The parent can occur without those added commitments, whereas removing the parent structure leaves no basis for classifying the child as this subtype. That asymmetry establishes subsumption rather than mere association.
- Enforcement Prime is a kind of Feedback
The accepted reference-grade review places Enforcement under Feedback because the child instantiates or depends on the parent's broader structure while retaining its own constitutive identity.Cause a rule, requirement, agreement or boundary to be complied with by monitoring conduct and applying credible consequences or corrective action. The parent is defined more broadly: Outputs influence inputs.
- Fail-fast system Prime is a kind of Feedback
The accepted reference-grade review places Fail-fast system under Feedback because the child instantiates or depends on the parent's broader structure while retaining its own constitutive identity.Detect an invalid state at the earliest trustworthy boundary, report it explicitly and stop the affected operation before corruption propagates. The parent is defined more broadly: Outputs influence inputs.
- Niche Construction Prime is a kind of Feedback
Niche_construction is a SPECIALIZATION of feedback where the fed-back variable is specifically the ENVIRONMENT OF SELECTION (which variants are favored), not any state the agent influences.feedback is the parent. Feedback supplies the genus: Outputs influence inputs. Niche Construction preserves that general structure while adding its differentia: An agent modifies its environment, and the modified environment changes the selection pressures acting back on the modifier — the environment is endogenous. The parent can occur without those added commitments, whereas removing the parent structure leaves no basis for classifying the child as this subtype. That asymmetry establishes subsumption rather than mere association.
- Perception Action Loop Prime is a kind of Feedback
The perception-action loop is the specific feedback structure in which 'action moves the sensing apparatus itself' — a constitutive coupling, not merely an error signal.Genus=feedback, differentia=acting-moves-sensing and reafference. Feedback supplies the genus: Outputs influence inputs. Perception Action Loop preserves that general structure while adding its differentia: Perception and action are constitutively coupled: action moves the sensing apparatus, that movement changes what is sensed, and what is sensed becomes the basis for the next action, in one closed loop with no clean sense-think-act stages. The parent can occur without those added commitments, whereas removing the parent structure leaves no basis for classifying the child as this subtype. That asymmetry establishes subsumption rather than mere association.
- Action Research Domain-specific is part of Feedback
Action research contains feedback because documented consequences and joint interpretation return to revise both the next practical change and the theory that guides it.The plan-act-observe-reflect phases form a closed corrective path whose output becomes a later input. Feedback supplies an internal constituent: Outputs influence inputs. Action Research requires that role within this mechanism: Braid inquiry and situation-change into one repeating plan-act-observe-reflect cycle in which researchers and participants overlap, pursuing usable practical change and transferable knowledge together under the rule that neither may be sacrificed for the other. Remove the parent-role and the child loses a required internal operation, even though the parent can exist outside the child. The child is therefore built from the parent rather than being a taxonomic kind of it.
- Agenda Building Domain-specific is part of Feedback
The multi-actor agenda process contains a reinforcing Feedback loop in which visibility produces coverage, advocacy, elite response, and further visibility.Media, entrepreneurs, elites, and publics respond partly to one another's attention. The constructed agenda therefore cannot be reduced to a one-way selection chain: its prior output becomes an input to the next allocation cycle.
- Allee Effect Domain-specific is part of Feedback
The Allee effect contains feedback because current conspecific density changes per-capita performance, which changes the next population density fed back into the same relationship.Removing the density-to-performance-to-density return path leaves only a one-time small-population handicap, not the density-dependent dynamic that defines weak and strong Allee effects. Feedback supplies an internal constituent: Outputs influence inputs. Allee Effect requires that role within this mechanism: Below a critical density a population's per-capita growth falls instead of rising, because the processes that need conspecifics break down — so low density itself becomes a demographic liability that can drive extinction even with ample resources. Remove the parent-role and the child loses a required internal operation, even though the parent can exist outside the child. The child is therefore built from the parent rather than being a taxonomic kind of it.
- Big Rip Domain-specific presupposes Feedback
**Feedback** is the minimal prospective parent.In a constant phantom regime, expansion increases dark-energy density; increased density raises the Hubble rate; the higher rate expands the universe faster. This is a literal reinforcing loop and is necessary to the simple Big-Rip mechanism. **Criticality** is related only loosely. Approaching the phantom divide (w=-1) changes whether the constant-(w) remaining-time expression is finite, but the Big Rip is not a scale-free critical regime in the encyclopedia's strict sense. **Cascade** is a tempting but incorrect parent: clusters, galaxies, solar systems, and atoms fail in sequence because one global cosmological driver overtakes different binding scales, not because each failed structure triggers the next. **Heavy-Tailed Distributions**, the frozen semantic top match, has no role in the identity. The proposed DAG therefore uses one composition/presupposition edge to Feedback. It does not claim that every positive-feedback system is cosmological or that Feedback alone entails a finite-time singularity.
- Biogeochemical Cycle Domain-specific is part of Feedback
Biogeochemical-cycle analysis contains feedback because reservoir stocks and climate variables alter flux rates whose redistribution changes those later stocks and forcings.Carbonate buffering, temperature-sensitive respiration versus photosynthesis, and ice-albedo coupling are not incidental examples; feedback couplings are one of the framework's five simultaneous commitments. Feedback supplies an internal constituent: Outputs influence inputs. Biogeochemical Cycle requires that role within this mechanism: Track how a chemical element moves through Earth's reservoirs via biological, geological, and chemical transformations, treating its conserved mass as a closeable budget of stocks, fluxes, and residence times. Remove the parent-role and the child loses a required internal operation, even though the parent can exist outside the child. The child is therefore built from the parent rather than being a taxonomic kind of it.
- Business Cycle Domain-specific is part of, typical Feedback
Standard endogenous business-cycle models typically contain feedback as output, income, investment, collateral, and credit conditions return to change subsequent aggregate activity.The live child describes contractionary propagation in which lower output reduces income and investment, further lowering output until capital and credit conditions stabilize. That return path is an internal mechanism in the standard RBC, New Keynesian, and financial-friction accounts, but the empirical dating concept intentionally commits to no generating theory.
- Central Pattern Generator Domain-specific is part of Feedback
Every source-defined CPG mechanism closes an internal state-to-next-state loop, even though external sensory feedback is not required.Voltage-dependent conductances return membrane state as current input; half-centres reciprocally inhibit and release one another; recurrent excitation and synaptic delay route network output back into later network input. This internal closure is distinct from optional afferent feedback from the body.
- Collateral-Damage Blowback Domain-specific is part of Feedback
A delayed reaction channel feeds the peripheral harm back into the initiating actor's future capacity.Blowback is distinguished by output returning as a new input to the actor's strategic position, often amplified and delayed through opinion, recruitment, litigation, alliance, or exit channels.
- Control Valve Domain-specific is part of Feedback
controlled flow supports stable process quantities.The prospective DAG uses composition under `prime:feedback`.
- Corrections Policy Domain-specific is part of Feedback
A corrections policy contains a closed feedback loop in which detected error acts back on the public claims record through a visible repair.The policy does more than state a preference for accuracy: it defines how an observed error is returned to the published record as a corrective action. Detection, attributed repair, and retention of the result form a strict output-to-input feedback loop inside every corrections policy.
- Direct Manipulation Domain-specific is part of Feedback
Direct Manipulation contains a tight feedback loop in which every incremental action immediately returns a perceptible state change.Remove the action-to-visible-effect return path and the user must reconstruct state after issuing commands, destroying the perception-action closure that produces felt directness. The child constrains loop latency and routes it through a rendered object.
- Emotional Response Domain-specific is part of Feedback
Interoceptive Feedback is an internal constituent of Emotional Response because physiology and expression return as inputs to the next appraisal.The response package does not terminate after outward expression. The agent senses its own arousal, posture, and action readiness and routes that output back into subsequent appraisal, allowing the package to amplify, settle, or be altered by regulation. Break the return path and the four stages become a one-way cascade with no recursive emotion-regulation leverage. Feedback is therefore contained in the live assembled construct while remaining far broader than affective systems.
- Entrepreneurial Discovery Domain-specific is part of Feedback
Entrepreneurial Discovery contains Feedback because profit or loss grades the conjecture embodied in action and successful exploitation changes prices and allocations, narrowing the gap that triggered it.The outcome returns information to the actor and the market, confirming or rejecting the perceived opportunity and altering the conditions for subsequent action; this closes the endogenous error-correction loop.
- Estuarine Turbidity Maximum Domain-specific is part of Feedback
An estuarine turbidity maximum contains feedback because sediment deposited from one tidal cycle becomes the bed and fluid-mud stock resuspended into the next cycle's suspended input.Landward advection, settling, bed storage, and tidal resuspension form a return path through which prior output helps sustain subsequent concentration. Feedback supplies an internal constituent: Outputs influence inputs. Estuarine Turbidity Maximum requires that role within this mechanism: A persistent zone of anomalously high suspended sediment near the head of salt intrusion in an estuary, sustained by a closed recirculation loop — landward near-bed advection, salt-induced flocculation, and tidal resuspension — rather than a passive deposit. Remove the parent-role and the child loses a required internal operation, even though the parent can exist outside the child. The child is therefore built from the parent rather than being a taxonomic kind of it.
- Exception Management Domain-specific is part of Feedback
Exception frequency and type are routed upstream so recurring deviations revise the normal-flow specification instead of merely enlarging the exception desk.A separate channel without an upstream return signal becomes a permanent dumping ground. The feedback constituent converts the exception stream into evidence about the normal design, allowing systematic deviations to change inputs, rules, and capacity rather than being handled forever downstream.
- Filter bubble Domain-specific is part of Feedback
A filter bubble contains the self-reinforcing loop from served items through engagement signals and model updates back to narrower serving.Algorithmic narrowing persists because each recommendation changes the observations used to rank the next one; remove that return path and the system may filter once, but it does not progressively tighten a bubble around revealed preference.
- Financial Accelerator Domain-specific is part of Feedback
A reinforcing collateral-credit-output loop is the constitutive amplification mechanism inside the financial accelerator.Feedback supplies an internal constituent: Outputs influence inputs. Financial Accelerator requires that role within this mechanism: The credit-market feedback loop by which a modest shock is amplified — falling asset prices erode collateral, raising the external-finance premium, which cuts investment and depresses prices further — its whole strength read off one elasticity: the premium's sensitivity to borrower net worth. Remove the parent-role and the child loses a required internal operation, even though the parent can exist outside the child. The child is therefore built from the parent rather than being a taxonomic kind of it.
- Firestorm Domain-specific is part of Feedback
ordinary spread and self-organized circulation behave as distinguishable regimes.The prospective DAG uses strict composition under `prime:feedback` because feedback is constitutive but a firestorm is not a subtype of feedback in the taxonomic sense.
- Flow State Domain-specific presupposes Feedback
Flow state presupposes feedback because the merging of action and awareness requires immediate, continuous return of information about the activity's progress.Flow state requires immediate feedback as a structural condition: the attentional fusion of action and awareness depends on the activity continuously returning information about its own unfolding, so that adjustment can occur without breaking the absorbed engagement. Without the feedback loop closing tightly between the performer's action and its perceptible consequence, the challenge-skill matching cannot be tracked moment-to-moment and the self-monitoring processes cannot fall silent. Csikszentmihalyi's clarity-of-goals-and-immediacy-of-feedback condition is the parent prime's structure operating as the substrate of flow.
- Genetic Assimilation Domain-specific is part of Feedback
Genetic Assimilation contains a cross-generation return path from plastic expression through differential reproduction to later expression propensity.The phenotype expressed in one generation changes reproductive success; differential reproduction changes the frequencies of heritable variants controlling the phenotype's threshold or reliability; those changed frequencies alter how readily the phenotype is expressed in later generations. Remove that return path and plastic expression cannot ratchet into increasing trigger independence.
- Harrod-Domar Model Domain-specific is part of Feedback
Reinforcing Feedback around the warranted path is the strict mechanism that turns small Harrod–Domar deviations into cumulative expansion or contraction.Growth above the warranted rate creates excess demand and induces investment that pushes growth farther above it; growth below the rate weakens demand and investment, pushing the system farther below. Output is routed back into the next investment input with the same sign rather than corrected.
- Indian Ocean Dipole Domain-specific presupposes Feedback
**Feedback.** This is the minimal prospective DAG parent through a strict composition/presupposes relation.SST, convection, winds, thermocline depth, and upwelling form a closed amplifying loop during event growth; without coupled return paths the candidate degenerates into a descriptive gradient.
- Isostasy Domain-specific is part of Feedback
Isostasy contains a delayed negative-feedback loop in which displacement changes buoyant support so the response opposes the applied or removed load.Added load drives sinking and greater displacement of the dense substrate, increasing the restoring buoyant contribution; removed load drives rebound and reduces excess support. Output displacement therefore changes the next force balance through a delayed rheological return path.
- Janzen-Connell Hypothesis Domain-specific is part of Feedback
Janzen-Connell contains stabilizing feedback because a species' local abundance recruits the specialist-enemy load that lowers its later recruitment.Without the abundance-to-enemy-to-recruitment return path, host-specific mortality is only an external loss and no longer makes dominance self-undermining or rarity advantageous. Feedback supplies an internal constituent: Outputs influence inputs. Janzen-Connell Hypothesis requires that role within this mechanism: Tropical tree diversity is maintained because host-specific enemies accumulate near adult conspecifics, so seedling survival rises with distance from the parent and falls with local conspecific density — a frequency-dependent penalty on local abundance that makes dominance self-undermining. Remove the parent-role and the child loses a required internal operation, even though the parent can exist outside the child. The child is therefore built from the parent rather than being a taxonomic kind of it.
- Karst Domain-specific is part of Feedback
Karst conduit growth contains a reinforcing flow-dissolution feedback.Remove the loop in which wider openings capture more flow, dissolve faster, and widen further, and the characteristic channelisation mechanism disappears. Feedback supplies an internal constituent: Outputs influence inputs. Karst requires that role within this mechanism: Diagnose a landscape where acidic groundwater has dissolved soluble bedrock into a self-reinforcing hidden conduit network, so the surface no longer maps the subsurface drainage and porous-media terrain rules are suspended. Remove the parent-role and the child loses a required internal operation, even though the parent can exist outside the child. The child is therefore built from the parent rather than being a taxonomic kind of it.
- Malthusian Trap Domain-specific is part of Feedback
A negative population-resource feedback loop is an internal constituent of the trap and restores per-capita welfare toward subsistence after a gain.Income above subsistence raises births and lowers deaths; population then increases pressure on the resource base, returning per-capita income toward the floor. The demographic transition breaks the trap by reversing this loop's sign, confirming that loop closure is constitutive.
- Maneuver Warfare Domain-specific is part of Feedback
The OODA competition is a feedback constituent in which observed effects update orientation and subsequent action.Maneuver warfare's out-cycling mechanism depends on repeated observe–orient–decide–act closure, using outputs and environmental changes to revise the next input and action. Feedback supplies an internal constituent: Outputs influence inputs. Maneuver Warfare requires that role within this mechanism: Win by targeting the enemy's cohesion and decision-making rather than their mass — out-cycling and dislocating their command-and-control through five coupled commitments (schwerpunkt, OODA dominance, gaps-and-surfaces, mission command, maneuver) so their force cannot be brought to bear. Remove the parent-role and the child loses a required internal operation, even though the parent can exist outside the child. The child is therefore built from the parent rather than being a taxonomic kind of it.
- Mark-to-Market Cliff Domain-specific is part of Feedback
The activated consequence feeds back into the same marked reference, pushing it farther beyond the threshold that triggered enforcement.A mere cutoff is not this cliff. Forced selling or collateral demand must worsen the price or balance-sheet measure that fired the rule, increasing breach and inducing further enforcement. That same-reference return path is an internal positive-feedback constituent of the financial mechanism.
- Market Pull Domain-specific is part of Feedback
Demand signals return to developers and investors and alter which variants are generated, funded, and refined next.Pull is not merely a static ranking of completed offerings. Observed need and buying response feed back into the innovation search, changing subsequent investment and variation. Feedback is therefore a constituent loop; the demand-side direction distinguishes Market Pull from supply-led Technology Push.
- Meander Cutoff Domain-specific is part of Feedback
Meander cutoff contains the reinforcing erosion loop that both enlarges a bend and narrows its neck.Remove the loop from outer-bank erosion to longer path to narrower neck to enhanced breach susceptibility, and the slow buildup toward cutoff loses its generative mechanism.
- Placemaking Domain-specific is part of Feedback
Placemaking contains feedback because form, recurring use, shared identity, and stewardship route their outputs into one another in a closed mutual-reinforcement circuit.Form enables use, repeated use produces identity, identity recruits stewards, and stewardship changes form and programming; a slack loop propagates decline through the same return paths.
- Responsiveness channel Domain-specific is part of Feedback
Feedback from users or contributors is the information flow the responsiveness channel receives and processes.Responsiveness Channel contains Feedback as the requests, objections, and observations that move from the served community to the maintaining body and receive a documented response.
- River Channel Migration Domain-specific is part of Feedback
changed planform redirects the flow and sediment field that causes subsequent change.changed planform redirects the flow and sediment field that causes subsequent change.
- Urban Heat Island Domain-specific is part of, typical Feedback
Urban Heat Island typically contains a cooling-demand feedback where HVAC waste heat feeds outdoor temperature upward.Feedback supplies an internal constituent: Outputs influence inputs. Urban Heat Island requires that role within this mechanism: Explain the persistent urban-rural temperature offset, especially after sunset, through heat-absorbing materials, thermal storage, reduced evapotranspiration and ventilation, canyon radiation trapping, and anthropogenic waste heat. Remove the parent-role and the child loses a required internal operation, even though the parent can exist outside the child. The child is therefore built from the parent rather than being a taxonomic kind of it. The typical qualifier limits the claim to the characteristic route, not a constitutive requirement of every instance; exceptions must retain the child's identity through another mechanism. The recorded exception is: The heat island exists without this loop in pre-HVAC, mild-climate, or weak-cooling contexts.
Condition / exception The heat island exists without this loop in pre-HVAC, mild-climate, or weak-cooling contexts.
- Uses and Gratifications Domain-specific is part of Feedback
Gratification obtained feeds back into future seeking and retention, making Feedback a strict constituent of the U&G cycle.The framework distinguishes anticipated from experienced satisfaction precisely so their gap can update later preferences and selection. Removing the return path leaves a one-shot choice account and loses its cyclical prediction of persistence or drift.
- Checks and Balances Prime presupposes Feedback
Checks and Balances presupposes Feedback: each branch's checks become inputs to the others' subsequent decisions and behavior.Checks and balances arranges authorities so that one branch's actions feed back to other branches as inputs that constrain their next moves: a veto, audit finding, or override returns to alter what the affected actor does next. That return path is exactly Feedback — output routed back to influence subsequent input — and it is what makes the reciprocal restraint dynamic rather than purely structural. Checks and balances presupposes feedback as the channel through which mutual restraint actually operates.
- Circuit Breaker Prime presupposes Feedback
Circuit breaker presupposes feedback because the monitor-trip-reset loop routes the protected flow's state back to control its own continuation.A circuit breaker watches a flow for a danger threshold and, when crossed, trips to interrupt the protected process until reset. This presupposes feedback: the structural arrangement in which a portion of a system's output is routed back to influence its subsequent input, closing a loop between cause and effect. The monitor observes the flow's current state and conditions the next-cycle behaviour (continue or interrupt) on what it sees. Without feedback's closed loop returning the flow's state to the trip decision, the breaker has no mechanism to act on the flow it is protecting.
- Communication Repair Prime is part of Feedback
Communication repair contains a feedback loop in which detected divergence is returned through a meta-channel to change the shared state before the primary exchange resumes.A repair episode observes the state produced by the primary exchange, compares the participants' interpretations, routes evidence of divergence back into the interaction, and uses the response to update shared state. Output from one pass therefore becomes corrective input to the next. The meta-channel, divergence detector, and resumption gate specialize that loop for communication, but without feedback there is no return path by which a misunderstanding can alter the exchange that produced it.
- Conditioning (Behavioral) Prime presupposes Feedback
Behavioral conditioning presupposes feedback because learned associations are forged by routing the consequence of a response back to modulate the response itself.Behavioral conditioning depends on the closure of a loop between behavior and consequence: the organism emits a response, the environment delivers reinforcement or punishment, and the returned signal modulates the probability of the response on the next cycle. Without the feedback arrangement — output measured, returned along a path, coupled with a sign that strengthens or weakens — the contingencies that conditioning detects could not be detected, and the response-strengthening and extinction dynamics could not arise. Feedback is the structural substrate on which conditioning operates.
- Echo Chamber Prime presupposes Feedback
Echo chamber is constituted by a self-reinforcing positive-feedback loop plus loss of the corrective negative-feedback signal.Feedback supplies the prerequisite condition: Outputs influence inputs. Echo Chamber operates against that background: A bounded community whose input filter and internal reinforcement gradient amplify shared beliefs and strip out the corrective signal that would moderate them, while members experience the environment as complete rather than filtered. If the parent condition is removed, the child relation becomes undefined or loses the mechanism asserted by this edge; the parent can obtain independently, so the relation is presupposition rather than subsumption.
- External Analytic Challenge Prime is part of Feedback
External analytic challenge contains feedback because its probes must return to alter or explicitly re-justify the next state of the work.Cut the challenge-to-response return path and the outsider can comment but cannot correct the work; the structure becomes observation or later judgment rather than pre-commitment challenge.
- Formative Assessment Prime presupposes Feedback
Formative assessment implements a measure-compare-act feedback loop routing learning evidence back to instruction.Feedback supplies the prerequisite condition: Outputs influence inputs. Formative Assessment operates against that background: Ongoing feedback. If the parent condition is removed, the child relation becomes undefined or loses the mechanism asserted by this edge; the parent can obtain independently, so the relation is presupposition rather than subsumption.
- Incentive Prime is part of Feedback
An incentive contains a consequence-to-future-choice feedback path linking payoff signals to subsequent behavior.A payoff attached to an act functions as an incentive only when its consequence can alter later selection or effort; without that return path it is merely an outcome, not a behavior-shaping signal.
- Inquiry-Change Learning Loop Prime is part of Feedback
The loop contains feedback because observed consequences must return to alter the next model-guided action.Cut the evidence return path and changes can be observed but cannot correct later understanding or action, destroying the loop.
- Instability Prime presupposes Feedback
Instability presupposes feedback because perturbations grow only when an amplification loop routes output back into input.Instability is the property whereby small perturbations grow rather than decay, characterized by an amplification mechanism that overcomes restorative or dissipative tendencies. This presupposes feedback: the structural arrangement in which a portion of a system's output is routed back to influence its subsequent input, with the sign and strength of coupling determining whether the loop opposes or reinforces. Positive feedback supplies exactly the amplification that turns small disturbances into growing deviations. Without a closed loop returning the system's behaviour to its own input, perturbations have no channel through which to compound into instability.
- Lateral Inhibition Prime presupposes Feedback
Lateral inhibition presupposes feedback because peer-to-peer mutual suppression is a closed loop in which each element's activity controls its neighbors' inputs.Lateral inhibition operates as mutual sideways suppression among peers: the more strongly an element is excited, the harder it pushes its neighbours down. This presupposes feedback: the structural arrangement in which a portion of a system's output is routed back to influence subsequent input, closing a loop between cause and effect. Each element's activity becomes a (negative-signed) input to its neighbours' subsequent state. The contrast-enhancing dynamic that produces edges and winners depends on the closed mutual loop; without feedback's routing of output back into input, peer suppression has no mechanism by which to act on the field.
- Leverage Points Prime presupposes, typical Feedback
Leverage points typically presuppose feedback because the disproportionate effect of small interventions runs through reinforcing or balancing loops.A leverage point is a location where a small change produces disproportionate effects on system trajectory. The mechanism that amplifies small interventions into large outcomes is typically feedback: a reinforcing loop magnifies the change as it cycles, or a balancing loop transmits the change through compensating dynamics that reshape goals or rules. Feedback supplies the closure A-B-A in which the system's output becomes its own input. Leverage operates through such loops in most cases, though some high-leverage paradigm-level interventions act through belief-restructuring without immediate feedback, hence typical.
- Livelock Prime is part of Feedback
Livelock contains a coupled feedback loop in which each responsive move elicits the compensating move that sustains non-progress.The recurrent active-but-stalled state is constituted by outputs from each participant feeding back as inputs to the other; without that response loop there may be delay or blockage, but not livelock.
- Logistic Growth Prime is part of Feedback
Logistic Growth contains the coupled positive engine and negative ceiling brake whose loop interaction produces its sigmoid trajectory.Growth proportional to the current quantity supplies reinforcing feedback; proximity to the finite ceiling supplies a multiplicative balancing feedback. Their conjunction produces takeoff, inflection, and decelerating saturation, while Feedback alone commits to neither a ceiling nor a logistic form.
- Metacognition Prime presupposes Feedback
Metacognition is built on a self-monitoring-and-regulation feedback loop over the agent's own cognitive processes.Feedback supplies the prerequisite condition: Outputs influence inputs. Metacognition operates against that background: Awareness of thinking processes. If the parent condition is removed, the child relation becomes undefined or loses the mechanism asserted by this edge; the parent can obtain independently, so the relation is presupposition rather than subsumption.
- Monitoring Prime presupposes Feedback
Monitoring is the observe-compare-trigger sensing arm that closes a regulatory feedback loop.Feedback supplies the prerequisite condition: Outputs influence inputs. Monitoring operates against that background: Continuously observing a system's state to detect deviation from expected behavior and trigger a response, separating genuine signal from routine noise. If the parent condition is removed, the child relation becomes undefined or loses the mechanism asserted by this edge; the parent can obtain independently, so the relation is presupposition rather than subsumption.
- Moral Panic Prime presupposes Feedback
Moral panic presupposes feedback because its self-amplifying wave of concern requires output-to-input loop closure across media, public, and authority.A moral panic is a self-amplifying episode of concern about a perceived threat, disproportionate to actual threat magnitude, following a recognizable life cycle. The self-amplification is constitutively a feedback structure: media coverage drives public concern, public concern drives political response, political response drives more coverage. Each round's output feeds back as the next round's input. Feedback supplies the closure between cause and effect that makes self-amplification possible. Without a loop routing output back to input, the wave could not build to disproportionate magnitude or run its characteristic course.
- Potentiation Prime presupposes Feedback
Potentiation presupposes feedback because history-dependent sensitization requires past output to route back and modify the system's response gain.Potentiation is the structural pattern in which prior exposure causes a system to respond disproportionately to a subsequent stimulus — the system's responsiveness, not the stimulus, has changed. This history-dependence requires that the past response be routed back to alter the parameters governing the next response, closing a loop between output and gain. The feedback structure supplies exactly that: a portion of the output influences subsequent input handling. Without that loop closure, no history-dependent sensitization could persist beyond the initial exposure.
- Predictive Coding Prime presupposes Feedback
Predictive coding presupposes feedback because the predict-compare-correct loop routes prediction-error output back to update the generative model.Predictive coding maintains an internal generative model that predicts incoming signal, compares prediction to actual input, and transmits or acts upon only the residual error — which then updates the model. The construct is constitutively a closed loop: the error output feeds back to update the predictor that generated the prediction. Feedback supplies that loop closure between output and subsequent input. Without a feedback structure routing the residual back to revise the model, there would be no improvement of predictions over time and no closed predict-compare-correct cycle.
- Quality Control Prime presupposes Feedback
Quality control is a measure-compare-act feedback gate binding process variation to defined tolerances.Feedback supplies the prerequisite condition: Outputs influence inputs. Quality Control operates against that background: Checking output against a specification before release and rejecting or reworking non-conforming items, binding process variation to defined tolerances through a measure-compare-act feedback gate. If the parent condition is removed, the child relation becomes undefined or loses the mechanism asserted by this edge; the parent can obtain independently, so the relation is presupposition rather than subsumption.
- Reference Cadence Exceeds Tracking Bandwidth Prime presupposes Feedback
Reference Cadence Exceeds Tracking Bandwidth presupposes Feedback, whose structure must already obtain for the child mechanism to be meaningful or operational.Feedback supplies the prerequisite condition: Outputs influence inputs. Reference Cadence Exceeds Tracking Bandwidth operates against that background: When the signal a closed loop must track changes faster than the loop's bandwidth, persistent error follows that no amount of executor effort can close. If the parent condition is removed, the child relation becomes undefined or loses the mechanism asserted by this edge; the parent can obtain independently, so the relation is presupposition rather than subsumption.
- Refinement Prime presupposes Feedback
Refinement presupposes feedback because each iterative improvement requires evaluating the current candidate and routing that judgment back to adjust the next pass.Refinement is the iterative sharpening of a candidate through repeated cycles of evaluation and adjustment, which structurally requires that the output of each round (the current candidate's quality) be routed back to shape the next round's input. Without feedback's closed loop — output measured, signal returned, input modified — there would be no mechanism by which iterations could accumulate progress; refinement would collapse into one-shot creation or undirected variation rather than the directed convergence that defines the pattern.
- Resonance Prime presupposes Feedback
Resonance presupposes Feedback: amplitude builds because energy returned through the system's own dynamics constructively reinforces the input.Resonance is the disproportionate amplification that occurs when driving forces match a system's natural frequencies, with the buildup arising because the system's prior oscillatory output returns in phase to constructively amplify subsequent input. That accumulation requires Feedback — output rerouted back to influence subsequent input — as the underlying structural arrangement. Without the loop, energy cannot accumulate selectively at the natural frequency, so resonance presupposes feedback as the substrate on which frequency-selective amplification rides.
- Schismogenesis Prime is part of Feedback
The accepted reference-grade review places Schismogenesis under Feedback because the child instantiates or depends on the parent's broader structure while retaining its own constitutive identity.A cumulative interaction pattern in which each side's response intensifies the relation—through matching escalation or mutually amplifying opposites—driving progressive differentiation unless balancing processes intervene. The parent is defined more broadly: Outputs influence inputs.
- Self-Defeating Prediction Prime presupposes Feedback
Self-Defeating Prediction presupposes Feedback, whose structure must already obtain for the child mechanism to be meaningful or operational.Feedback supplies the prerequisite condition: Outputs influence inputs. Self-Defeating Prediction operates against that background: Belief in a forecast moves conditions against it. If the parent condition is removed, the child relation becomes undefined or loses the mechanism asserted by this edge; the parent can obtain independently, so the relation is presupposition rather than subsumption.
- Spiral Of Silence In Publics Prime presupposes Feedback
Spiral of Silence presupposes the positive feedback loop through which visible suppression changes perceived opinion climate and induces further suppression.Each round of silence makes one side look less prevalent, which raises the perceived cost of expressing that side and produces more silence. Without this recursive return from public expression to later expression choices, isolated preference falsification would not become a population-level spiral.
- Stability-Induced Fragility Prime presupposes, typical Feedback
A positive-feedback loop running through agents/components inside a system (low volatility -> relaxed vigilance -> raised exposure -> more fragility).Presupposes feedback. (feedback canonical.). Feedback supplies the prerequisite condition: Outputs influence inputs. Stability-Induced Fragility operates against that background: Prolonged calm endogenously erodes the response capacity that stressors keep exercised. If the parent condition is removed, the child relation becomes undefined or loses the mechanism asserted by this edge; the parent can obtain independently, so the relation is presupposition rather than subsumption. The typical qualifier limits the claim to the characteristic route, not a constitutive requirement of every instance; exceptions must retain the child's identity through another mechanism.
- Streisand Effect Prime is part of Feedback
The Streisand effect contains a reinforcing loop in which visible suppression generates attention that further increases the suppressed information's reach.The control action becomes a new signal, audience response republishes both signal and target, and the growing visibility recruits still more response; without that return path there is only a failed removal attempt.
- Stressor Induced Adaptation Prime presupposes Feedback
Stressor-Induced Adaptation presupposes Feedback: applied strain must be sensed and routed back into the system to drive compensatory build-up.Stressor-induced adaptation requires the system to detect strain, route that signal back into its own reconfiguration, and grow capacity in proportion to repeated load. Without that loop the strain merely degrades function rather than building lasting strength. Feedback — output routed back to influence subsequent input — supplies the structural arrangement that converts current stress into future capacity. Stressor-induced adaptation presupposes feedback as the mechanism by which strain becomes a build signal rather than damage.
- System Archetypes Prime presupposes Feedback
System archetypes presupposes feedback because the recurring problematic dynamics they catalog are characteristic loop structures.System archetypes name recurring patterns of feedback loops and structures that produce characteristic system behavior across domains — limits to growth, shifting the burden, eroding goals, escalation, and others. Each archetype is constitutively a configuration of reinforcing and balancing loops; the diagnostic and intervention value comes from recognizing the loop structure beneath surface differences. Feedback supplies the underlying loop-closure structure that makes each archetype intelligible. Without feedback as a first-class structural object, the archetypes would have no shared substrate and would reduce to coincidental surface similarities.
- Systems Thinking Prime presupposes Feedback
Systems thinking presupposes feedback because its core analytical move is to model loops and circular causation rather than linear cause–effect chains.Systems thinking presupposes feedback because its defining analytical commitment is to shift the unit of analysis from elements to loops — modeling circular causation, delay, and stock-and-flow structure rather than linear chains. It inherits feedback's structural arrangement in which a system's output becomes a driver of its own subsequent input, treating this closure as the dominant causal pattern to be diagnosed. Without feedback's loop-closure structure, systems thinking would collapse to ordinary causal analysis.
- Threshold Bounded Vicious Cycle Prime presupposes, typical Feedback
Feedback is the underlying primitive; this prime SPECIALIZES it by adding a threshold, a two-attractor structure, and active consumption of input as maintenance in the low regime.A positive feedback loop alone is not a trap. Feedback supplies the prerequisite condition: Outputs influence inputs. Threshold Bounded Vicious Cycle operates against that background: A system has a low regime that consumes any small input as maintenance and a high self-sustaining regime, separated by a threshold an intervention must clear in both magnitude and duration. If the parent condition is removed, the child relation becomes undefined or loses the mechanism asserted by this edge; the parent can obtain independently, so the relation is presupposition rather than subsumption. The typical qualifier limits the claim to the characteristic route, not a constitutive requirement of every instance; exceptions must retain the child's identity through another mechanism.
- Ultra-Stability (Ashby's Concept) Prime presupposes Feedback
Ultra-Stability presupposes Feedback: essential-variable regulation requires measuring deviation and routing it back to drive corrective reorganization.Ultra-stability holds essential variables within viable bounds by sensing excursions and triggering parameter reorganization when first-tier regulation fails. Both the inner regulation and the outer reorganization loop require Feedback — output rerouted back to influence subsequent input — as the structural arrangement. Without the loop, the system has no way to detect that essential variables have departed bounds or to drive corrective change. Ultra-stability presupposes feedback at both control tiers.
- Validation Prime presupposes Feedback
Validation presupposes Feedback: confirming fitness for purpose requires routing real-world observations back to test the artifact against intended use.Validation asks whether the artifact solves the right problem in its actual operational context, which requires observations of the artifact under realistic use to be routed back as evidence against the intended-purpose specification. That return path is exactly Feedback: output measured and routed back to influence subsequent decisions about the artifact. Without the loop there is no fitness-for-purpose verdict; validation presupposes feedback as the channel through which operational reality informs the verification verdict.
- Circular Flow Domain-specific is a decomposition of Feedback
The household-firm loop contains literal return-as-input closure: firms' payments become household income and household expenditure returns as firms' receipts.The live child expressly identifies feedback as one of its portable parent structures. The opposed real and monetary loops close causal and accounting paths rather than forming a one-way chain. The child remains more than feedback because it fixes economic sectors, two carried quantities, injection/leakage categories, and national-income closure.
- Declinism Domain-specific is a decomposition of Feedback
The inflated past steepens the apparent decline, the tilted present supplies a worse slope, and the pessimistic forecast feeds back to confirm the frame that governs later memory and evaluation.The three stages are not merely additive. Their outputs re-enter later judgments as inputs, which explains why correcting one component can leave the remaining stages able to regenerate the same perceived downslope.
- Passivation Domain-specific is a decomposition of Feedback
Surface reaction creates a barrier that suppresses later reaction, closing a sign-opposing loop that converges to a low passive rate.The film is not merely correlated with slower corrosion: output from one cycle returns as reduced transport and charge transfer on the next, and film damage reopens the reaction that rebuilds it where self-healing is available.
- Validated Learning Domain-specific is a decomposition of Feedback
Build–measure–learn routes observed customer behavior back into the next hypothesis and test, so measured output changes subsequent input and action.The loop is not decorative startup vocabulary: without the return path from behavior to belief and the next experiment there is no accumulated validated learning, only disconnected tests.
- Vorticity confinement Domain-specific is a decomposition of Feedback
**Feedback** (`prime:feedback`).A measured loss signature in the resolved field drives a localized corrective source. These are prose placement proposals only. They create no `dag_edges`; endpoint, redundancy, and cycle checks are recorded separately in the bundle's placement memo.
- Coevolution Prime is a decomposition of Feedback
Coevolution is the specific shape feedback takes when two adapting entities each become persistent selective pressures on each other.Coevolution is the structurally-particularized form feedback takes in the evolutionary case: each species' adaptation is the output that returns as the input (the changed selective pressure) on its partner, closing a reciprocal loop between cause and effect across generations. It inherits feedback's structural arrangement in which output routes back to influence subsequent input — particularized to the case where the timescale is generational, the variable is the fitness landscape, and the coupling is mutually reinforcing. Mutual entanglement of trajectories is precisely loop closure.
- Network Effect Prime is a decomposition of Feedback
Network effects is the specific shape feedback takes when each new user makes the system more valuable to all existing users, reinforcing further adoption.Feedback is the closure in which a system's output is routed back to influence its subsequent input, with the present depending on the system's own prior output. Network effects is the particular shape this closure takes in adoption dynamics: each additional user raises the platform's value to all users, which raises the probability that further potential users adopt, which raises the value again. It is a structurally-particularized instance of positive feedback whose specific tap is installed-base size and whose specific coupling is the value-to-adoption-probability relation.
- Reputation Prime is a decomposition of Feedback
Reputation is the specific shape feedback takes when an agent's prior conduct loops back through third parties to shape future treatment.Reputation is the specific shape feedback takes when the output is an agent's conduct and the return path runs across time and across observers. The agent's behavior at t feeds into a public record; that record shapes how third parties treat the agent at t+1, which feeds back into the agent's incentives for behavior at t+1. The loop closure feedback requires is realized through the information channel third parties maintain, and the present value of future reputation premiums disciplines current quality through the same input-from-prior-output structure feedback names.
- Self-Fulfilling Prophecy Prime is a decomposition of Feedback
A self-fulfilling prophecy is the specific shape feedback takes when a belief's expression alters behavior so that the belief is validated.A self-fulfilling prophecy is the specific shape feedback takes when the looped variable is a prediction or expectation about an outcome and the return path runs through the behavior of the people who hold or hear the prediction. The prediction's expression alters action, action alters the outcome, and the outcome confirms the prediction — closing the loop. It is a structurally-particularized instance of output routed back to influence subsequent input, with the added specification that the looped quantity is a belief about the future and the coupling sign is positive enough to drive the world toward the predicted state.
- Speculative Bubble Prime is a decomposition of Feedback
A speculative bubble is the specific shape feedback takes when valuation and expectation of future rises form a self-reinforcing loop that overshoots and collapses.A speculative bubble is the positive-feedback particularization of feedback applied to asset valuation: rising prices feed expectations of further rises, which drive more buying, which drives prices higher still, until the loop exhausts its inflow and reverses sharply. Where feedback names the closure of a loop between system output and subsequent input generally, the bubble fixes the variable (price), the sign (reinforcing), the medium (collective expectation), and the characteristic boom-then-bust signature of an overshoot-and-collapse trajectory.
Neighborhood in Abstraction Space¶
Feedback sits among the more crowded primes in the catalog (27th percentile for distinctiveness): several abstractions describe nearly the same structure, so a description that fits it will tend to fit its neighbors too — transporting it usually means disambiguating within this family rather than landing on it exactly.
Family — Signal Gain, Feedback & Control Dynamics (24 primes)
Nearest neighbors
- Gain Control — 0.74
- Amplification — 0.73
- Homeostasis — 0.73
- Instability — 0.73
- Distortion — 0.72
Computed from structural-signature embeddings · 2026-09-10
Not to Be Confused With¶
Feedback must be distinguished from System Archetypes, its nearest structural neighbor (similarity 0.723). Both concepts describe cyclic causal patterns, but they operate at different levels of specificity and abstraction. Feedback is the general mechanism by which a system's output is routed back to influence its input—any closed causal loop with a sensed return path, a comparison to reference, and a corrective action. System Archetypes are recurring named patterns that emerge from particular combinations of feedback structures: reinforcing loops (positive feedback producing exponential growth or collapse), balancing loops (negative feedback seeking equilibrium), delays (lag between action and consequence), and their interactions. Archetypes are patterns made from feedback loops; feedback is the primitive building block. A thermostat is a feedback system; an S-curve growth pattern (slow takeoff, explosive growth, saturation) is an archetype made from interacting feedbacks. The distinction matters because understanding feedback teaches you how loops work (signs, gains, delays), while understanding archetypes teaches you which combinations of loops produce predictable behaviors. A system designer armed with feedback thinking can reason about control parameters; a designer with archetype thinking can recognize "this looks like a tragedy of the commons" and know in advance that simple reinforcing loops will produce collapse. Archetypes are feedback patterns you've seen before; feedback is the underlying mechanism those patterns exemplify.
Feedback is also distinct from Homeostasis, even though homeostasis is a product of negative feedback. Homeostasis describes a state—a living system maintaining internal variables (temperature, pH, glucose levels) within a narrow operating range despite external disturbances. Feedback is the mechanism that produces homeostasis. A living organism is homeostatic; the feedback loops that regulate temperature, hormone levels, and water balance are what enable that homeostasis. The confusion arises because negative feedback is often called "homeostatic feedback," but the term conflates mechanism with outcome. Not all feedback produces homeostasis: positive feedback produces runaway amplification (viral spread, chain reactions, speculative bubbles), not stability. Mixed-sign feedback systems can oscillate indefinitely around a setpoint without achieving homeostasis. Homeostasis is one possible outcome of well-tuned negative feedback; feedback is the broader category that includes stabilizing, amplifying, and oscillating behaviors. An organism maintaining body temperature despite cold weather is homeostatic (outcome) and uses negative feedback (mechanism); a population entering a boom-bust cycle is using positive feedback (mechanism) and is decidedly not homeostatic (outcome).
Nor is feedback identical to Reflexivity or Self-Reference, concepts sometimes confused with it because both involve a system relating to itself. Reflexivity is the capacity of an entity to take itself as an object of attention or modification—to observe itself, to revise its own rules, to critique its own reasoning. A person reflecting on their assumptions, a legislature rewriting its own operating procedures, a machine-learning system adjusting its own parameters are all exhibiting reflexivity. Feedback, by contrast, does not require awareness or intention. A thermostat feeds back information about temperature to adjust heating without "knowing" what it is doing; a chemical equilibrium feeds back concentration changes to shift reaction rates without intention. A reflexive system can include feedback loops (a person learns by observing consequences of their actions—feedback), and a feedback system can become reflexive (a system might observe and recalibrate its own feedback parameters), but the concepts are distinct. Reflexivity is about meta-level modification (changing how you change); feedback is about first-order correction (changing behavior based on output). A recursive function calling itself is neither feedback (no output is sensed and returned to modify input) nor reflexivity in the sophisticated sense (no self-awareness). The distinction clarifies why some systems can be tightly feedback-controlled but not reflexive (industrial control systems are precise feedback machines but have no self-awareness), and why some reflexive systems can be poorly designed to extract information from their own feedback (people often ignore feedback about their behavior, despite the capacity to reflect on it).
These distinctions are critical for practitioners because confusing feedback with archetypes leads to mistaking patterns for mechanisms; confusing feedback with homeostasis leads to assuming all feedback stabilizes (it doesn't); and confusing feedback with reflexivity leads to over-attributing intentionality to systems that are merely mechanically responsive. Clear separation enables clearer diagnosis: "Is this system oscillating because of poor feedback tuning, or because it is following a known archetype pattern?" "Is the system failing to maintain homeostasis despite negative feedback, or is negative feedback absent entirely?" "Is this behavior reflexive self-correction or mechanical feedback response?"
Solution Archetypes¶
Solution archetypes in the catalog that build on this prime — directly (this prime is a source ingredient) or as a related prime.
Built directly on this prime (112)
- Absolute Acquisition–Incremental Tracking: Acquire an unambiguous absolute anchor, track fine change through a cheaper incremental channel, and reacquire when accumulated uncertainty can no longer be bounded.
- Adaptive Barrier-Circumvention Response: Treat a successful barrier as a changing selection environment: monitor which variants survive, then renew and
diversify protection before uncovered survivors become the population.▸ Mechanisms (17)
- Adverse Adaptation Red Team — A chartered, safety-bounded exercise in which defenders imagine how an adaptive adversary would evolve to slip past the current barrier set — and whether the nominally independent layers would fall to the same move.
- Agent-Based Experiment or Simulation — Plays the arms race forward in silico — a population of heterogeneous adaptive variants meets a candidate barrier portfolio over many rounds, so escape dynamics surface in simulation before they surface in the field.
- Barrier Coverage Matrix — A cross-tabulation of control layers against variant classes and contexts that marks demonstrated coverage apart from unknown, stale, correlated, or merely-inferred coverage — making uncovered cells and shared blind spots visible before escape finds them.
- Champion–Challenger Barrier Revalidation — Runs a candidate replacement control alongside the incumbent against current and stressed variant classes, promoting it only when it demonstrably improves population-level coverage without opening a transition gap.
- Common-Mode Escape Review — Tests whether nominally independent barriers would actually fail together — against the same feature, data gap, assumption, or context — so apparent defense-in-depth is not a single point of failure wearing several hats.
- Conditional Control-Rotation Protocol — Switches or alternates among genuinely independent controls on evidence-based triggers rather than a predictable schedule, spreading selection pressure so no single blind spot is rewarded long enough to take over.
- Coverage-Decay Trigger and Release Gate — Turns evidence of coverage decay into a pre-authorized, owned response — escalate, contain, renew, or roll back — bounded by a hard floor on the protection that must never drop.
- Cross-Boundary Escape Incident Review — Investigates an apparent escape event across teams or jurisdictions to establish whether it is real selection-driven circumvention or an impostor — migration, a protected refuge, an implementation failure, or measurement drift.
- Escape Variant Watchlist — A governed, evidence-graded register of known and plausible escape variants — what each is, how strong the evidence is, who owns it, when it is next reviewed, and its response status — so uncertain classes are tracked over time without being treated as confirmed threats.
- Escape-Variant Sentinel Network — A standing web of watch-posts across sites and contexts that catches an emerging escape variant early and tells reproducible population change apart from one site's local noise.
- Fitness Proxy Audit — Audits what your barrier and its metrics actually reward for surviving — exposing proxies that let an escape variant look 'handled' precisely because it has become harder to see.
- Layered Independent-Control Design Workshop — A facilitated design session that assembles a portfolio of controls whose failure modes are genuinely independent, so no single adaptation can defeat the whole defense at once.
- Safe Transition and Rollback Drill — Rehearses switching, layering, and falling back between controls so that replacing a decaying barrier never opens a worse protection gap than the one it closes.
- Selection-Differential Cohort Analysis — Compares survival or persistence across exposed and unexposed cohorts to test whether the barrier is actively selecting for the escape variant, rather than merely coinciding with a drift it never caused.
- Source-Pressure Reduction Review — Looks for ways to shrink the underlying demand, opportunity, or payoff that keeps generating escape pressure — so protection leans less on an ever-stronger filter that only breeds fitter survivors.
- System-Wide Net-Risk Dashboard — Sets local barrier performance beside system-wide net harm — displaced risk, shifting variant mix, uncertainty, and who bears the burden — so a control that looks like it is winning locally cannot hide that protection is decaying or merely moving.
- Variant-Composition Surveillance Dashboard — Tracks the shifting share of each variant class over time — not just total incidence — so population-weighted protection loss shows up before the surviving forms take over.
- Adaptive Gain Retuning: Retune the sensitivity of a fast pathway with a slower adaptive loop so outputs stay discriminating, bounded, and useful as input conditions change.▸ Mechanisms (12)
- Adaptive Normalization Layer — Rescales each incoming signal against its own recent statistics so a downstream pathway always sees inputs on a comparable, standardized footing.
- Automatic Gain Control Loop — A closed feedback loop that watches its own output level and continuously drives the gain up or down to hold that output inside a useful band.
- Contextual Gain-Scheduling Table — A lookup table that pairs each named operating regime with a pre-chosen gain, so the system switches sensitivity by recognizing its context rather than by watching a signal.
- Contrast Adaptation Protocol — After sustained exposure to a prevailing level, deliberately re-centers sensitivity on that level so the system stays responsive to meaningful differences instead of the background it has stopped noticing.
- Exposure or Alarm Sensitivity Adjuster — An operated procedure for retuning how readily a detector fires as background rates and false-alarm burden shift, trading misses against noise through a deliberate human-reviewed decision.
- Fixed-Gain Degraded Mode — When the adaptation signal can no longer be trusted or the stakes rise too high, it suspends retuning and pins the gain at a safe fixed value so the fast pathway keeps running predictably.
- Gain Floor/Ceiling Rule — A hard clamp on the gain parameter — a floor that stops the pathway going numb and a ceiling that stops it running away — that the adaptive loop may retune within but never breach.
- Gain-Change Review Log — A dated, append-only record of every gain change — what moved, on what evidence, the effect expected, the bounds it stayed within, who approved it, and what actually happened.
- High-Load Clipping Test — A deliberate stress probe that drives the pathway with a high-input regime to find where it starts to saturate, flood, or clip — before the real surge does.
- Hysteretic Gain-Update Filter — A dwell requirement on the retuning loop: gain moves only after the evidence for moving it has persisted, so transient spikes can't rewrite sensitivity and the loop stops chasing noise.
- Saturation Occupancy Dashboard — A live view of where the pathway's outputs land — clipping at the top, dying unused at the bottom, weak signals missed — beside the current gain and the input load driving it.
- Weak-Signal Recovery Test — A held-out battery of known-important faint cases, replayed to confirm that turning the gain down to cut false alarms hasn't turned the signals that matter invisible.
- Adaptive Response Recalibration: Adjust response rules when conditions change so the system remains fit for its environment.▸ Mechanisms (8)
- Adaptive Operating Rule Update — Makes a team's implicit operating rule — its triage, routing, or escalation logic — explicit, then re-maps it to a shifted demand or risk mix through a bounded, evidence-triggered update.
- Clinical Treatment Adjustment — Adjusts a treatment's dose, intensity, timing, or support in response to a patient's changing state and side effects — monitored closely and reversed the moment the change does harm.
- Governance Rule Revision — Revises who holds authority to decide and what review a decision must pass, re-fitting the governance rule to a changed risk or accountability context while preserving auditability.
- Model Retuning — Deliberately re-fits the predictive model — its parameters, features, and calibration — to current data so its forecasts stay accurate as the tracked relation drifts, on a turnaround that must beat the drift it is correcting.
- Policy Recalibration — The deliberate procedure for revising an operating policy when the moving objective makes the prior rule unfit — escalating when no policy can meet the target, and rolling back a recalibration that misfires.
- Service-Level Recalibration — Revises the service commitments a system promises — response-time targets, escalation tiers, staffing triggers — when demand and capacity assumptions no longer hold, judged by whether the targets are actually met.
- Training Plan Adjustment — Revises a learner's or athlete's plan — its intensity, volume, difficulty, or pacing — as evidence of progress, plateau, or fatigue shows the plan no longer matches their current state.
- Workflow Adaptation — Re-sequences the steps, handoffs, and exception paths of a workflow to fit a shifted work mix — keeping the change inside a scope boundary so it stays recalibration, not redesign.
- Adaptive Scheduling: Continuously revise task timing and resource allocation as demand, priority, capacity, or risk changes.▸ Mechanisms (8)
- Adaptive Appointment System — A booking or service-slot system that revises appointments as no-shows, cancellations, urgency, duration, or capacity changes.
- Adaptive Production Schedule — A production scheduling workflow that revises sequencing and resource use as orders, inputs, machines, or bottlenecks change.
- Dispatch Rescheduling System — A tool or workflow that revises dispatch assignments during execution as live conditions change.
- Dynamic Staffing Schedule — Continuously reassigns a shared pool of people to the fronts that need them, floating only those eligible to move and never stripping any front below its protected coverage floor.
- Incident Response Rotation — A response-coverage schedule that adapts to incident severity, fatigue, role availability, or coverage needs.
- Maintenance Window Replanning — A procedure for moving or reshaping maintenance windows when readiness, risk, dependency, or service impact changes.
- Real-Time Job Scheduler — A runtime tool that schedules jobs or tasks according to live load, priority, dependency, and capacity signals.
- Rolling Planning Cycle — A recurring planning cadence that folds each authorized target change into a rolling multi-horizon schedule, so replanning happens on a predictable rhythm instead of on impulse.
- Agentic Control Loop Design: Agency becomes real when goals, situation models, available actions, authority, execution, feedback, and learning are coupled into a loop that can intentionally change outcomes.▸ Mechanisms (10)
- Action-Effect Feedback Review — A recurring review that attributes what an action did and did not change, updating the actor's read on what is now within their control.
- After-Action Learning Cycle — A recurring, blame-free review that turns what actually happened into concrete revisions of the model and the next action.
- Agency Health Dashboard — Turns the live health of an agency loop — is feedback timely, is the actor actually acting, is discretion being used — into a small set of continuously-watched signals.
- Agency Loop Map — Lays the agent's full goal-to-feedback loop out as one connected diagram so a missing or broken coupling becomes visible at a glance.
- Briefback or Intent Confirmation — Before acting, the actor restates the goal, constraints, and plan back to the tasker to confirm shared understanding and surface conflicts early.
- Controllability Mapping Checklist — Sorts a situation into controllable, influenceable, constrained, and uncontrollable parts before any action is chosen.
- Decision-Rights Matrix — Maps each class of decision to who may decide, approve, be consulted, or merely be informed — fixing the agent's authority before any single choice arises.
- Graduated Autonomy Ramp — A staged schedule that widens an actor's decision authority as evidence of competence accumulates, with support fading as autonomy grows.
- Model Assumption Register — A living list of every assumption the agent's world model rests on, each with an owner, a confidence, and a stated trigger for when it must be revisited.
- Safe Action Menu — A fixed template of pre-approved, in-bounds actions for a high-risk setting, with an escalate path for anything the menu does not cover.
- Agent–Environment Co-Shaping: Shape the environment an agent or population inhabits so the resulting conditions improve future behavior and adaptation—and keep governing the feedback as both sides change.▸ Mechanisms (12)
- Adaptive Management Cycle — Governs a co-shaping environment as a running act→monitor→learn→adjust loop, updating the intervention from evidence as agents and their surroundings keep changing each other.
- Agent-Based Niche Simulation — Runs the co-shaping loop forward in silico with many adaptive agents, so you can watch which environmental changes stay viable — and which get gamed — before committing them for real.
- Causal-Loop and Environment-State Map — A single diagram of the environment's boundary, its state variables, and the reinforcing and balancing feedback loops through which agents and their surroundings change each other.
- Ecological Restoration Pilot — A bounded field intervention that jump-starts a self-sustaining successional trajectory in a degraded habitat, then hands the recovery over to the system's own feedbacks.
- Environmental Indicator Dashboard — A live instrument panel that tracks how agents and their environment are co-adapting — and flags when someone is adapting to game the very signals you steer by.
- Habitat or Spatial Reconfiguration — Rearranges physical space so its new adjacencies, sightlines, and barriers quietly reshape how the people or organisms moving through it behave.
- Infrastructure and Default Redesign — Rebuilds the shared substrate and default settings people act within, so the behaviour you want becomes the path of least resistance instead of an act of willpower.
- Institutional Rule and Incentive Redesign — Rewrites the rules, sanctions, and payoffs of a shared setting so the environment itself selects for the behaviour you want — and those who act bear its consequences.
- Legacy and Maintenance Register — Keeps a standing record of what past shaping left behind — the constructions, dependencies, and obligations later agents inherit — so nothing load-bearing is forgotten, retired blindly, or left to rot.
- Platform-Ecosystem Rule Change — Changes the rules of a live digital ecosystem and governs the fast, often adversarial way participants re-adapt to them.
- Staged Reversible Environment Pilot — Tests an environmental change on a bounded, undoable slice first — keeping an escape path and preserving options — so you learn what it does before it hardens into something you can't take back.
- Stakeholder Boundary Review — Decides who counts as inside the system being shaped — constructors, beneficiaries, and the affected outsiders who bear the spillovers — before the boundary is drawn implicitly by whoever holds the pen.
- Alertness-Capacity Maintenance: Maintain the standing ability to notice important change without forcing continuous attention, alarm overload, or permanent hypervigilance.▸ Mechanisms (11)
- Alert-Fatigue Review — Periodically audits whether alarms and cues have been fired so often that people have stopped noticing them, and retunes their intensity before a real one is tuned out.
- Environmental Scan Checklist — Turns 'keep an eye out' into a fixed-cadence sweep of named places to look, each paired with a cue for telling a real signal from ordinary background.
- Heartbeat or Ping Check — Requires a channel, device, or person to confirm itself alive on a fixed beat, and treats silence — not just a bad reading — as the signal that trips a response.
- Micro-Recovery Schedule — Builds short, scheduled recovery and role-switch breaks into watch work, so alertness is topped up on a cadence instead of quietly draining to nothing.
- Near-Miss Notice Review — Studies the times a signal was almost missed — the catches that only just happened — and feeds what nearly failed back into the readiness, scan design, and cues that let it slip.
- Red-Team Noticeability Probe — Plants controlled test signals into a live watch to verify the system actually notices — and escalates — what it claims to be watching for.
- Sentinel Dashboard — Gathers the few signals worth watching onto one always-on surface, so a single unhurried glance tells a watcher whether anything meaningful has changed.
- Shift Handoff Briefing — Transfers the live watch across a change of personnel — active anomalies, what's been ruled out, fatigue and staffing, and any changed assumptions — so vigilance survives the handover.
- Signal-Detection Calibration Drill — Sharpens an operator's ability to tell signal from noise and re-sets where they draw the line, by drilling on known-truth cases and feeding back every hit, miss, and false alarm.
- Standby-Mode Interface — Keeps the normal state quietly visible and reserves loud, high-salience interruption for the moments that genuinely cross the threshold.
- Watch Rotation Roster — Spreads vigilance duty across people and time on a fixed rotation, so notice-capacity is always staffed and no single watcher is held past the point their alertness decays.
- Anti-Herding Signal Design: Preserve independent judgment by reducing blind imitation signals and surfacing diverse,
reliable information.▸ Mechanisms (7)
- Blind Independent Review Round — Requires reviewers, forecasters, jurors, or evaluators to record a private assessment before they see anyone else's score or the group's discussion.
- Circuit Breaker Pause — Trips an automatic, temporary halt on one runaway activity the instant a cascade metric crosses a preset threshold, then releases on its own once conditions cool.
- Diverse Recommendation Exposure — Rebalances a feed or search ranking so raw popularity is offset by source diversity, minority evidence, uncertainty, and independent quality signals.
- Hidden or Delayed Popularity Counts — Withholds, delays, or buckets the visible like, view, or vote count on an item until the viewer has formed their own first impression.
- Minority Report Requirement — Requires the decision record to preserve dissenting views and contrary evidence on the record before the group's consensus is finalized.
- Rumor Verification Notice — Attaches verification status, context, and recommended action to a fast-spreading claim so circulation is not mistaken for proof.
- Staggered Information Release — Releases social, ranking, or aggregate information to participants in phases so early movers do not disproportionately anchor everyone who comes later.
- Associative Cue Redesign: Change the cues and contexts that trigger automatic responses so behavior can shift at the moment it happens.▸ Mechanisms (11)
- Behavior Substitution — Installs a specific competing response in the exact window the old routine used to fill, so removing a habit doesn't leave a vacuum the old loop rushes back into.
- Context Restructuring — Re-architects the surrounding workflow or sequence so the old cue-response pairing can no longer assemble and the desired response becomes the structural default.
- Environmental Cue Change — Changes the physical cue objects in a space — their placement, salience, or presence — so the old trigger fades from view and the intended one is right where the hand and eye land.
- Friction or Salience Adjustment — Re-weights the effort and attention around existing options — adding friction to the old response, salience to the new — so the desired action becomes the path of least resistance without removing any choice.
- Habit Loop Mapping — Charts the existing cue → routine → reward loop so the association driving a behavior is visible before anything is changed.
- Implementation Intention Script — Pre-scripts an if-[specific cue]-then-[goal action] plan so the focal goal fires automatically on its trigger instead of waiting on in-the-moment willpower.
- Point-of-Action Prompting — Fires the cue at the exact moment and place the intended response can be taken, so the prompt lands where it can actually be acted on.
- Prompt Redesign — Rewrites, recodes, and repositions an existing prompt so it cues the intended response instead of the old one — and reads clearly without steering people covertly.
- Relapse Trigger Review — Reviews the episodes where the old response came back to find which cue, context, or substitution failure was responsible — turning each recurrence into a targeted repair.
- Safety Cue Redesign — Repositions and clarifies the cues that trigger safe action so the safe response fires before hazard exposure, and refreshes them so they never fade into background.
- Trigger Removal — Takes the triggering cue out of the environment — removing, blocking, delaying, or decoupling it — so the old response is never started, then checks it did not just reappear elsewhere.
- Backpressure: Propagate downstream capacity pressure upstream so producers slow before overload accumulates into failure.
- Balancing Loop Stabilization: Strengthen or retune self-correcting feedback so a system returns toward a viable range after disturbance.▸ Mechanisms (9)
- Budget Variance Review — Compares planned against actual spending or revenue on a fixed cadence and routes each material variance to the owner who can reallocate, rescope, or retime — while keeping the money signal honest against gaming.
- Control Loop Tuning — Sets the standing gains, damping, and deadband of a fixed-structure controller so the loop is fast enough to follow the moving target yet damped enough not to oscillate or amplify noise.
- Corrective Action Review — After a corrective action has been taken, verifies that the deviation actually shrank and that no compensating failure appeared elsewhere — escalating when the fix did not hold.
- Hysteresis Band — Sets separate switch-on and switch-off thresholds with a deliberate gap between them, so a controller stops flip-flopping when the signal hovers near a single boundary.
- Quality Control Chart — Plots a process metric over time against a centerline and statistically-derived limits, so genuine drift stands out from the routine random variation that should not be chased.
- Service-Level Autoscaling — Adds or removes serving capacity in response to load, latency, or saturation signals to hold a service inside its target range — sized around the provisioning delay and the ceiling on how much capacity it can add.
- Thermostat-Like Controller — Bundles a sensor, a setpoint, a comparator, and an on/off actuator into one self-contained regulator that switches to hold a variable near a target.
- Threshold-Based Correction — Holds off on any corrective action until the deviation crosses a defined threshold, then fires a preset response — trading fine responsiveness for freedom from chasing noise.
- Variance Correction Cycle — Runs a fixed-cadence loop — measure the gap to target, explain it, trigger a corrective adjustment, then recheck it next cycle — turning drift into routine self-correction rather than periodic reporting.
- Batch Size Calibration: Set batch size as a controllable design variable, not a habit: make the batch large enough to amortize setup cost but small enough to preserve flow, safety, responsiveness, and timely feedback.▸ Mechanisms (10)
- Batch Quality Review Window — A recurring review of grouped work sized to balance signal reliability against correction delay.
- Batch Release Gate — A release-control protocol that checks batch size, rollback capacity, risk, and downstream absorption before release.
- Batch Size Guardrail Dashboard — A dashboard tracking lead time, queue age, setup utilization, defect discovery delay, and batch-risk exposure.
- Batch Size Tuning — Sets how many items are grouped before they move to the next stage, trading per-item overhead against the residence time and pile-up that large batches create.
- Economic Order Quantity Model — A formulaic inventory mechanism for balancing ordering or setup cost against holding cost.
- Production Lot Size Review — A review procedure for comparing production lot sizes against changeover, storage, quality, and downstream-flow costs.
- Queue Simulation Sweep — A simulation that evaluates candidate batch sizes under stochastic arrivals, service times, and capacity.
- Rolling Batch Size A/B Test — A controlled comparison of candidate batch sizes using operational metrics.
- Setup Time Reduction and Recalibration — A workflow that lowers setup or switching cost and then recalculates the batch-size operating band.
- Transfer Batch Split — A mechanism that decouples production batch size from the smaller batch moved to the next stage.
- Beneficial-Input Inversion Control: Keep a helpful input below the receiver's assimilation ceiling, and if it crosses, reduce the source, break the bloom, and restore the depleted secondary resource before a worse regime locks in.▸ Mechanisms (12)
- Assimilation Capacity Assay — Measures how much of the beneficial input a bounded receiver can actually take up before more turns harmful — the assimilation ceiling and the reserve it quietly spends to hold the line.
- Bloom Harvest or Suppression Intervention — Breaks a bloom already underway — dampening the self-amplifying loop and harvesting the accumulated surplus — for the case where shutting off the source is no longer enough.
- Bloom Sentinel Dashboard — Watches the live approach to the inversion — current input pressure against the ceiling, plus leading sentinels that turn positive before the bloom starts — to buy lead time while source control is still cheap.
- Clearance Acceleration Protocol — Speeds the receiver's own clearance of an accumulated surplus so the system falls back below the ceiling faster — and the depleted second resource is given room to rebuild.
- Dose-Response Inversion Curve — Maps the whole input-to-outcome relationship, marking the dose where rising input stops helping and starts harming — and why the harm runs away once it begins.
- Hysteresis Recovery Threshold Test — Finds how far below the onset point the input must be pulled to actually reverse a bloom-locked regime — the recovery threshold is lower than the trigger, and returning to the old 'safe' level is not enough.
- Nutrient or Input Load Budget — Sets a total permissible load for a beneficial input — below the receiver's assimilation ceiling, with margin — and allocates it across every contributing source.
- Pretreatment or Filtering Gate — A boundary stage that strips the harmful fraction out of an incoming beneficial input before it reaches the receiver, capturing what it removes.
- Rate Limit or Admission Cap — Caps the rate at which a beneficial input reaches the receiver, throttling, queuing, or turning away arrivals the moment inflow presses against the safe ceiling.
- Secondary Resource Replenishment Reserve — Holds and rebuilds a buffer of the secondary resource a bloom depletes, so the receiver can recover even after the original input is cut off.
- Source Tracing and Reduction Program — Traces an aggregate overload back to the many diffuse sources that produce it, assigns each its measured share, and makes each bear the cost so it reduces at origin.
- Staged Reloading Trial — Re-introduces a previously-harmful beneficial input in small, monitored increments after recovery, backing off at the first sign of re-inversion.
- Bidirectional Consistency Mapping: Keep two independently changing representations meaningfully consistent by defining both directional mappings, controlling update propagation and echo, resolving conflict, and testing round-trip and convergence behavior.▸ Mechanisms (12)
- Bidirectional Change-Data-Capture Adapter — Captures origin-tagged changes from both sides and routes them through governed transforms.
- Dual-Write Outbox and Inbox Pattern — Persists intended changes and idempotent receipt so propagation survives partial failure.
- Field-Level Authority Matrix — States which side or decision rule governs each field and operation under defined conditions.
- Forward/Reverse Field-Mapping Specification — Records each directional mapping, loss, default, authority, and version.
- Idempotency and Deduplication Ledger — Records applied change identities and outcomes so retry does not compound effects.
- Mapping-Version Backfill and Rollback Plan — Governs coexistence, historical backfill, cutover, validation, and rollback for semantic mapping changes.
- Round-Trip Property-Test Suite — Generates representative and boundary values and tests both directional cycles against allowed equivalence and loss.
- Shadow Sync and Diff Run — Executes a new mapping or policy without authoritative writes and compares predicted state before migration.
- Synchronization Conflict Queue — Holds nonautomatic conflicts with evidence, authority class, affected action, owner, and resolution status.
- Synchronization Lag and Oscillation Dashboard — Exposes frontier lag, repeated value bounce, conflicts, failed transforms, dropped fields, and stale tombstones.
- Synchronization Origin Token — Marks propagated changes so the reverse path can suppress echo without discarding independent edits.
- Tombstone and Revocation Propagation — Preserves deletion or revocation evidence long enough to prevent resurrection across delayed paths.
- Boundary-Cost Coarsening Management: When boundary maintenance cost pushes many small units into fewer larger ones, measure the size distribution, preserve valuable boundaries, and channel or reverse consolidation before useful microstructure disappears.▸ Mechanisms (7)
- Anti-Coarsening Inhibitor Protocol — A materials-inspired protocol for adding pinning agents, stabilizers, membranes, standards, or constraints that slow undesired unit growth.
- Capped-Growth or Split Rule — A rule that triggers splitting, spin-outs, local autonomy, or added interfaces when a unit crosses diseconomy or concentration limits.
- Controlled Consolidation Gate — A checklist that permits mergers or aggregation only when boundary-cost savings outweigh lost diversity, resilience, and reversibility.
- Interface-Cost Accounting — A method for separating the real cost of maintaining boundaries from the value those boundaries preserve.
- Reseeding or Nucleation Program — A workflow for introducing new small units, pilots, categories, teams, grains, entrants, or local nodes after excessive coarsening.
- Size-Distribution Dashboard — A dashboard that tracks unit count, size skew, merger rate, small-unit attrition, and concentration over time.
- Target Granularity Review — A recurring review that asks whether the current number and scale of units still match the system’s purpose.
- Bycatch-Aware Selective Intervention Design: When a selector catches more than its intended target, count the non-target capture, redesign the selector, and make success depend on bycatch reduction as well as target yield.▸ Mechanisms (11)
- Bycatch Rate Dashboard — A live scoreboard that keeps off-target capture and its cumulative harm on screen next to target yield, broken out by non-target class, so bycatch can't hide behind a good headline number.
- Bycatch Tolerance Stop Rule — A pre-committed limit on off-target harm that halts or forces redesign the moment bycatch crosses it — no matter how good target yield looks.
- Compensation and Restoration Trigger — A standing rule that, once collateral harm is confirmed, automatically opens a route to make non-targets whole and pins the bill on a named accountable party.
- Escape Hatch or Release Protocol — A built-in route by which a non-target that has already been caught can get back out before the harm is locked in.
- False-Capture Audit — An arm's-length review that samples what the selector actually caught, sorts true target from non-target, and reports a false-capture rate the operator can't self-certify away.
- Negative Filter or Exclusion Device — A front-end cutoff, built into the selector, that admits the target while turning non-targets away before they are ever caught.
- Non-Target Impact Pre-Mortem — Before deployment, imagines the intervention has already caused off-target harm and works backward to name who gets caught and how — turning bycatch into a design input rather than a post-mortem finding.
- Non-Target Sentinel Sampling — Watches a small, deliberately chosen panel of non-target classes as early-warning sentinels, sampling them directly so off-target harm surfaces in the field before it becomes systemic.
- Selectivity Window Test — Sweeps the selector across its control variable to map where it separates target from non-target, locating the operating window in which selectivity holds and the edges where it collapses.
- Selector Retuning Cycle — A repeating loop that feeds observed bycatch back into the selector's settings, tightening specificity iteration by iteration and escalating to a different method when tuning stops paying off.
- Success Metric Reweighting — Rewrites the scorecard so a bycatch term counts against success, making off-target harm subtract from the headline number instead of sitting outside it, and names who owns that term.
- Circuit Breaker: Interrupt or restrict a coupled flow when overload signals indicate cascade risk, then re-open cautiously under feedback.
- Circular Causality Mapping: Map feedback loops where effects become causes so reinforcing or balancing cycles can be understood and changed.▸ Mechanisms (10)
- Behavior-over-Time Graph — Plots a variable or outcome over time so recurring growth, collapse, oscillation, drift, or stabilization patterns can be recognized before mapping causes.
- Causal Loop Diagram — Draws the pressure behind a hazard, the feedback loops that regenerate it, and the delays between them, so a control can be aimed at the loop rather than the symptom it displaces.
- Feedback Analysis Workshop — Gathers stakeholders to identify loop variables, test causal stories, surface disagreements, and select follow-up questions or interventions.
- Influence Mapping Interviews — Uses interviews or structured elicitation to reveal perceived causal links, delays, and feedback paths that are not visible in data alone.
- Intervention Point Review — Uses the loop map to compare candidate places for damping, amplifying, redirecting, monitoring, or redesigning the feedback structure.
- Loop Polarity Review — Checks whether link polarities and overall loop type have been assigned consistently and whether a balancing loop has been mistaken for a reinforcing loop or vice versa.
- Policy Resistance Map — Maps how a policy intervention changes incentives, expectations, or behavior in ways that push the system back toward the old pattern.
- Root-Cause Loop Analysis — Extends root-cause analysis beyond a one-way chain by asking how the effect feeds back into causes and keeps the problem recurring.
- Scenario or Simulation Testing — Tests whether the mapped loop could plausibly produce the behavior pattern under different assumptions, delays, or intervention choices.
- System Dynamics Mapping — Represents feedback, accumulations, flows, and delays in a form that can support qualitative reasoning or simulation.
- Co-Activation Coupling Design: Strengthen useful links by arranging valid repeated co-activation, then bound the update so accidental pairings do not become durable shortcuts.▸ Mechanisms (10)
- Association Matrix Update Rule — Specifies the local law that turns each valid co-activation into a small, bounded change in the stored link strength, so associations grow from experience without any weight running away.
- Co-Occurrence Weighting Pipeline — Counts how often units appear together inside a defined window and re-weights the raw tallies so that frequency artifacts don't masquerade as meaningful association.
- Competitive Inhibition Review — Reviews links that compete for the same cue and lets the strongest suppress its rivals, so one intended association sharpens instead of many near-neighbors all strengthening indiscriminately.
- Context-Gated Pairing Exercise — Practices the target pairing only inside the contexts where it should hold, so the association becomes conditional on context instead of firing everywhere the cue appears.
- Decorrelation Separation Protocol — Breaks the incidental correlation between units that should stay independent — by re-representing or re-sampling them — so a valid signal and a confounder can no longer wire together as one.
- Paired Activation Rehearsal Protocol — Drives a named pair of units into genuine joint activation, again and again, until the cue reliably recruits its target — the deliberate 'make them fire together' drill.
- Pruning & Decay Maintenance Cycle — Runs on a cadence to weaken unused links and cut the ones that fall below a keep threshold, so the association store stays lean and stale or harmful couplings don't accumulate forever.
- Replay Consolidation Window — Re-activates already-experienced pairs offline, in spaced bouts, to move a link from a fragile fresh trace to a stable consolidated one without needing the original event to recur.
- Spurious Association Probe Set — A standing battery of targeted test cases that deliberately try to trip a learned link into revealing that it rides on a shortcut, a stereotype, or a leaked cue rather than the real signal.
- Temporal Contiguity Training Schedule — Arranges when cue and outcome are presented — the interval between them and the spacing of repetitions — so they fall inside the window where joint activation actually binds them.
- Coevolutionary Response-Coupling Design: Design the observation, response, damping, and learning structure for systems that adapt in response to each other’s adaptations.▸ Mechanisms (10)
- Arms-Race Risk Register — A register of escalation risks — moves that could trigger a counter-move ratchet or lock both sides into a costly spiral — each paired with the expected adversary response and a trip-wire.
- Coadaptation Cadence Review — A recurring review whose interval is deliberately matched to how fast the other side adapts, so strategies and defenses are refreshed before they go stale — no slower, and no more churn than needed.
- Coevolution Map Workshop — A facilitated session that draws the coupled system's boundary and maps who is adapting to whom, so the move–countermove loop is visible before anyone optimizes a single side.
- Damped Escalation Protocol — A pre-agreed rule set that lowers the gain on the move–countermove loop — capping retaliation, adding delay, or buffering the coupling — so an escalation spiral loses energy instead of ratcheting.
- Diversity Floor or Option Reserve — A standing policy that keeps a minimum reserve of diverse strategies or variants in play, so a coevolving adversary can't exploit a monoculture and there is always an un-obsoleted move to fall back on.
- Move-Countermove Log — A running, time-stamped record of each side's moves and the other side's countermoves — and the lag between them — that turns a coevolution into an inspectable sequence.
- Mutualism Alignment Review — A periodic check on whether a partnership still creates value for both sides and for the wider system, catching the slow drift from mutualism into one-sided extraction before it breaks the relationship.
- Opponent or Partner Response Simulation — A model that plays the interaction forward — you move, the other side responds per a model of its incentives, and both payoffs are scored — to reveal counter-moves before you commit.
- Reciprocal Adaptation Scenario Planning — Builds a small set of divergent futures in which the other side adapts differently, so strategy is chosen to be robust across how the coupling might evolve — not optimized against today's opponent.
- Red Queen Dynamics Review — A periodic check on whether both sides are investing heavily yet neither is gaining relative advantage — the running-to-stay-in-place signature — and what regime the coupling is actually in.
- Compensation-Aware Safeguard Design: Design safeguards so their apparent safety gains are not consumed by compensating increases in risky behavior, exposure, speed, leverage, or carelessness.▸ Mechanisms (8)
- Adaptive Safeguard Recalibration Gate — A standing review that re-tightens or redesigns the safeguard once evidence shows behavioral offset is eating the intended gain.
- Before / After Behavior Monitor — Measures the risk-relevant behaviors before and after a safeguard so offset shows up as a change in conduct, not only in the final harm rate.
- Exposure Cap or Rate Limiter — Turns the tolerated risk level into an enforced ceiling or rate limit, so a safeguard's new margin can't be cashed out as raw depth, throughput, or leverage.
- Post-Safeguard Incentive Audit — Re-maps who now pays, benefits, observes, and controls after a safeguard lands, exposing where the risk budget and accountability actually moved.
- Risk Compensation Premortem — Before a safeguard ships, imagines how users will spend the safety gain — so the offset is anticipated and wired into monitoring instead of discovered after harm.
- Safety-Gain Offset Dashboard — Nets technical failure reduction against behavioral offset, displaced exposure, and bystander harm so a safeguard's real gain is read as a total, not a local win.
- Shared Downside or Deductible Rule — Keeps the protected actor exposed to a calibrated slice of the loss — a deductible or co-risk — so failure stays costly enough to hold care in place.
- Use-Conditioned Protection Policy — Makes protection contingent on maintaining stated operating standards, and states the coverage boundary plainly, so the safeguard rewards careful use rather than licensing carelessness.
- Competence Calibration Feedback: Align self-assessed competence with actual performance through feedback, benchmarks, and guided reflection.▸ Mechanisms (12)
- Benchmarked Feedback — Explains a performance gap against an explicit rubric or standard, stating what the evidence shows and the confidence update it warrants.
- Calibration Conversation — A structured two-way conversation that surfaces a person's own self-assessment, sets the evidence beside it without triggering shame, and lands on one concrete next step.
- Calibration Exercise — Has people commit a confidence estimate before the outcome is revealed, then repeats, so the running gap between stated confidence and actual result becomes visible and trainable.
- Competency Framework — A leveled map of what capability looks like at each stage of a domain, giving the calibration loop a fixed reference to measure self-assessment and evidence against.
- Confidence Rating Scale — A defined instrument for recording perceived readiness or certainty, making self-assessment explicit and comparable so it can later be checked against evidence.
- Decision Rights by Competence — A governance rule tying each level of demonstrated competence to a matching authority — act alone, act with review, or must escalate — so calibration changes what a person is permitted to do.
- Exemplar Comparison — Sets someone's own work beside concrete exemplars at known quality levels so the gap between what they produced and what good looks like becomes visible to them directly.
- Peer Review — Brings the external judgment of domain peers to bear on someone's work, supplying an outside perspective the person cannot see from the inside — while guarding against slippage into status judgment.
- Reflective Error Log — A running log where a person records their own errors and surprises alongside the confidence they held at the time, so patterns of miscalibration surface over the long run.
- Simulation or Case Test — Puts a person into a realistic simulated scenario or case and measures how they actually perform, generating high-fidelity evidence — including on unfamiliar situations — without real-world risk.
- Skills Assessment — A formal, domain-scoped evaluation that scores actual performance against an explicit standard, producing the evidence a calibration loop compares self-assessment to.
- Supervised Practice — A staged process in which a person performs real work under a supervisor's observation, earning independence one demonstrated case at a time rather than by assertion.
- Compounding Advantage Flywheel Design: Turn cumulative use, learning, scale, data, or reputation into a bounded flywheel where each added unit improves the return to the next unit, while guarding against runaway lock-in, exclusion, fragility, and bubbles.▸ Mechanisms (10)
- Bubble and Lock-In Red Team — Attacks a claimed flywheel to expose where its growth is speculative froth and where its concentration has become dangerously fragile — before the story is believed.
- Compounding Curve Review — Reads the shape of the marginal-return curve across successive increments to tell a still-improving flywheel from one that has quietly flattened or begun to reverse.
- Cumulative Reputation System — Accumulates verified track-record into a persistent, portable reputation stock so that each additional trusted interaction makes the next one easier to win.
- Data Flywheel Dashboard — Instruments the data-improvement loop on one live view — use to data to model quality to user value to more use — so a team can see whether the flywheel is actually turning.
- Experience Curve Review — Certifies whether cost or quality is genuinely improving through learning-by-doing as cumulative production grows — and captures the lessons that drive it — separating a real experience effect from ordinary scale or price moves.
- Fixed-Cost Amortization Plan — Spreads a large fixed investment across a growing volume of units so average cost falls as the base grows — and pins the volume threshold at which the investment pays for itself.
- Open Standard or Portability Rule — Guarantees open interfaces, data portability, and exit rights so a compounding platform's participants keep the freedom to leave — bounding lock-in before the loop becomes too entrenched to govern.
- Platform Seeding Program — Bootstraps a cold two-sided or complement-driven loop by recruiting anchor participants and seeding early complements until the flywheel can spin on its own.
- Reinvestment Cadence — A standing rule that routes a fixed share of each cycle's gains back into the flywheel's driver on a regular schedule — and throttles the reinvestment as the curve saturates.
- Reusable Asset Library — Curates the outputs of past work into a reusable, searchable store so every new effort starts from what the last one produced instead of from scratch.
- Compounding Control: Interrupt, dampen, redirect, or govern compounding growth or decay before it becomes runaway.▸ Mechanisms (8)
- Anti-Snowball Intervention — Breaks a self-reinforcing loss path early, such as escalating fines, cascading missed work, repeated disciplinary penalties, or accumulating service barriers.
- Concentration Limit — Caps accumulated share, exposure, authority, risk, or market power when compounding advantage would crowd out resilience or fairness.
- Decay Countermeasure Program — Offsets compounding deterioration by adding maintenance, practice, replenishment, retention, or renewal before capability falls below viability.
- Epidemic Growth Control — Reduces transmission or reproduction so each cycle generates fewer subsequent cases rather than more.
- Interest Cap — Limits compounding financial obligations so debt does not grow faster than repayment capacity or social legitimacy.
- Progressive Friction — Makes additional accumulation increasingly costly or review-heavy as the compounding variable approaches a dangerous range.
- Runaway Feedback Damping — Attenuates reinforcing signals, escalation loops, or attention loops before they amplify into systemic instability.
- Technical Debt Paydown Cadence — Schedules recurring repair so shortcuts do not compound into fragility, opacity, or change paralysis.
- Compounding Leverage: Deliberately structure repeated gains so small improvements accumulate into disproportionately large effects.▸ Mechanisms (12)
- Automatic Verified-Gain Reinvestment — A standing rule that automatically routes a fixed, verified fraction of every real gain back into the productive base — so retention happens by default, not by anyone remembering to do it.
- Automation Capability Reinvestment — Plows the time and capacity freed by each automation into building the next one, so the ability to automate compounds instead of the savings being quietly absorbed elsewhere.
- Compounding Loop Map — Diagrams the specific feedback loop by which a gain feeds the next cycle — base, yield, retained fraction, reinvestment — so a team can check the loop actually closes and see where it leaks.
- Effective-Rate and Doubling-Time Dashboard — Tracks the effective compounding rate and its doubling time, and tests the trajectory against an additive baseline so ordinary accumulation isn't mistaken for exponential growth.
- Harvest — The periodic decision of how much accumulated gain to take out now versus leave compounding — set so harvesting never draws the productive base below the rate it can regrow.
- Learning Capture and Reuse Cycle — Turns each cycle's hard-won lessons into reusable, traceable capability so the team starts every next cycle from a higher floor instead of relearning the same thing.
- Progressive Reinvestment Allocation — Reinvests a deliberately growing but bounded share of each cycle's yield, ramping the fraction up as compounding is proven and capping it before it over-commits.
- Referral or Participation Reinvestment Loop — Channels part of the value each participant receives back into recruiting the next, so the base of participants becomes the engine that grows the base.
- Retained Earnings or Resource Pool — Holds retained gains as a durable, deployable reserve — the war-chest a compounding loop draws on to fund its own next round of reinvestment.
- Retention — Keeps a won gain from leaking or decaying after the fact, so the improvement becomes a new floor to build on instead of ground that has to be re-won each cycle.
- Reusable Asset Library — Curates the outputs of past work into a reusable, searchable store so every new effort starts from what the last one produced instead of from scratch.
- Staged Capacity Expansion Gate — Releases capacity expansion in evidence-gated stages, enlarging the base only when the current stage is healthy and saturation is still far off.
- Conformance Control and Corrective Feedback: Measure output against an explicit specification, gate release on conformance, contain and disposition failures, and feed defect evidence upstream until recurrence risk falls.▸ Mechanisms (10)
- Automated Conformance Check — Encodes the acceptance criteria as machine-executable checks that evaluate every unit inline and block nonconforming output automatically.
- Control Chart and Trigger Rule — Plots a characteristic over time against statistical control limits so a drifting process trips a predeclared trigger before its output crosses the spec.
- Corrective and Preventive Action Cycle — Turns a significant or recurring defect into a root-cause investigation, a durable process change, and a verified check that it stops recurring.
- First-Article and Setup Approval — Verifies the first piece off a new setup against the full specification before authorizing the production run, so a bad setup is caught before it is repeated thousands of times.
- Measurement-System Capability Analysis — Quantifies how much of the observed variation is the measurement system rather than the product, so a gauge can be trusted at the decision boundary.
- Nonconformance Report and Review Board — Records each nonconformance and convenes an authorized board to bound the affected population and decide its disposition.
- Release Hold and Signoff — Holds output in a controlled, non-released state until an authorized signoff — or a scoped, time-bounded waiver — permits it to move.
- Rework and Reinspection Route — Routes nonconforming output through an authorized repair and mandatory reinspection, with a hard limit on repeat cycles.
- Risk-Stratified Acceptance Sampling Plan — Sets inspection intensity by defect risk and criticality, then accepts or rejects each lot on a predeclared sample rather than checking every unit.
- Upstream Quality Feedback Packet — Packages downstream defect and field-failure evidence into a structured signal the producing process, design, or supplier can actually act on.
- Conformity Pressure Calibration: Calibrate the pressure to match a group standard by protecting private judgment, exposing social-pressure channels, and preserving safe divergence before alignment becomes automatic.▸ Mechanisms (10)
- Anonymous Ballot or Survey — Collects each person's judgment through an identity-stripped channel so what surfaces reflects belief rather than fear of being seen to dissent.
- Delayed Popularity Count — Withholds a running popularity signal until each viewer has had a window to react on the content itself, so early votes don't stampede later ones.
- Leader-Last Protocol — Requires the highest-status person in a discussion to state their view only after everyone else has, so their preference does not become the group standard by default.
- Minority Report Template
- Norm Recalibration Review — A scheduled review that re-examines an established norm against current evidence, consent, and drift, and pulls the trigger to revise it when it no longer earns its pressure.
- Norm Source Mapping Workshop — A facilitated session that traces a taken-for-granted norm back to whose practice it actually is and what, if anything, that reference group knows.
- Opt-Out and Exception Pathway — A defined, low-retaliation route by which a person can decline or seek exception from a standard, with bounds that separate protected divergence from unsafe deviation.
- Pressure Channel Audit — A systematic inventory of every route through which aligning is rewarded and diverging is punished, sorting each into informational versus normative pressure.
- Silent Start / Private Precommitment — Opens a decision with each person writing and committing their own judgment before any discussion, so the first view spoken cannot anchor the rest.
- Social-Proof Context Label — An annotation attached to a popularity signal that tells the viewer what the number does and does not mean, so a crowd count isn't read as an endorsement of quality.
- Conserved Reservoir-Flux Balancing: Name the reservoirs, name the conserved fluxes between them, and close the balance so interventions change the whole stock-flow network rather than merely moving imbalance out of sight.▸ Mechanisms (14)
- Capacity Headroom Alert — Watches each reservoir's level against its capacity and fires before the headroom runs out, turning a slow fill or drain into a warning with lead time to act.
- Compartment Model — Abstracts a system into a few well-bounded compartments linked by transfer rates, so accumulation and turnover follow from residence times instead of being watched flow by flow.
- Data Lineage Balance Check — Asserts that every step of a data pipeline conserves its records and totals — what enters equals what leaves plus what was intentionally dropped — and flags any hop where the count silently breaks.
- Flow Gate or Valve Rule — A control rule that opens, throttles, or closes a flux channel on a defined trigger, steering the network's balance by adjusting flows in real time rather than cleaning up after.
- Inventory Reconciliation Workflow — A recurring workflow that brings recorded stock back into agreement with a physical count, assigns each discrepancy a cause and an owner, and closes the books on a set cadence.
- Loss-Sink Audit — Hunts the gap between what should be in the system and what is, tracing the missing quantity to the leak or unmonitored sink absorbing it — and to whoever quietly bears the loss.
- Mass-Balance Table — Lays every measured inflow and outflow of a conserved quantity into one ledger so inputs minus outputs must equal the change in stock — and any residual is flagged, not buried.
- Material Flow Analysis — Traces a conserved substance across a defined system — inputs, stocks, transfers, and outputs — so every unit is accounted for from source to sink.
- Reservoir Balance Dashboard — Puts the current level, headroom, and net flow of every reservoir on one live display, so drift and an impending fill-or-drain are seen while there is still time to act.
- Sankey Flow Map — Draws the whole flow network as ribbons whose width is proportional to quantity, so you see at a glance where a conserved flow concentrates, splits, and disappears.
- Stock-and-Flow Diagram — Draws the conserved quantity as stocks (accumulations) connected by flows (rates), exposing the reservoir-and-pipe structure — and the feedback loops — behind a flow problem.
- System Dynamics Simulation — Turns a stock-and-flow structure into equations and runs it forward in time, so you can watch reservoirs fill, drain, and oscillate under a policy before trying it for real.
- Unit Conversion Crosswalk — A shared table of equivalences that converts every flow and stock into one common unit, so quantities measured differently can actually be added, balanced, and compared.
- Water or Resource Budget — Balances a specific resource over a defined boundary and period — sources in versus uses and losses out, against available storage — to see whether the account closes and whether it is over-committed.
- Constraint Envelope Adjustment: Tighten, relax, or reshape the constraints defining a system's permissible action space to remove harmful freedom or restore needed flexibility.
- Constraint-Guided Improvisation: Generate competent next moves in real time by recombining an internalized repertoire inside stable constraints and continually updating from the developing situation.▸ Mechanisms (12)
- After-Action Review — Turns a just-finished episode into validated lessons by reconstructing what was intended versus what actually happened and deciding which improvised moves earned a place in the repertoire.
- Call-and-Response Pattern — Alternates a leader's call with the group's answer so that every response is a live, audible readout of who is with you — synchrony through call-and-answer turn-taking rather than unison.
- Constraint Backbone Brief — States the fixed purpose, hard limits, and non-negotiable invariants up front — plus the conditions under which improvising is authorized — so people can invent freely without breaking what must not break.
- Decision-Rights Matrix — Maps each class of decision to who may decide, approve, be consulted, or merely be informed — fixing the agent's authority before any single choice arises.
- Facilitated Turn-Taking — Keeps a group's overlapping contributions coherent by having someone allocate whose move comes next, so improvisation stays collision-free and builds on itself instead of fragmenting.
- Improvisation Learning Harvest — Reviews the novel moves people improvised in the field and decides which to promote into the sanctioned repertoire and grammar — turning one-off saves into reusable, reviewed practice and catching precedent before it sets unreviewed.
- Minimum Safe Stabilization — Buys time under pressure by taking the smallest in-bounds set of actions that reaches a safe, holdable state rather than a full fix — trading completeness for a stable footing to reassess from.
- Move-Announce-Acknowledge Cycle — Before or as an improviser acts, they announce the move and wait for an explicit acknowledgment — so independent, unscripted moves don't collide and everyone's picture stays current.
- Rollback or Pause Protocol — Defines in advance who may halt, slow, or reverse an improvised course the moment agreed danger signals are crossed, and the routine for unwinding it to a known-safe state.
- Shared Situation Model — Gives everyone acting in the moment one continuously-updated picture of the situation, risks, and who's doing what, so improvised moves are fitted to what is actually happening rather than to stale or private assumptions.
- Tactical Reset Point — A pre-designated known-good state plus the trip-wire that says stop improvising and fall back to it — so a line of invention that goes wrong has a cheap, rehearsed way back.
- Variable Scenario Rehearsal — Drills people against deliberately varied, unpredictable scenarios before the real event, so the repertoire of moves is fluent and the skill floor is met when improvisation is actually needed.
- Control Surface Creation: Create actionable points of intervention so a system that is hard to steer becomes controllable.▸ Mechanisms (10)
- Actuator Installation — Adds the physical, technical, procedural, or organizational means by which a surface can cause actual change.
- Adjustable Threshold — Implements the surface as a cutoff, trigger, tolerance, eligibility rule, or operating limit that authorized actors can change.
- Admin Console — Provides a visible operator interface for changing settings, permissions, routing, quotas, or system behavior.
- Configuration Template — Standardizes how control variables are represented, reviewed, and changed across instances.
- Control API — Provides a programmable surface through which trusted systems or operators can change controlled variables.
- Control Knob — Gives an operator a constrained adjustment point, often for intensity, speed, allocation, pressure, or tolerance.
- Delegated Approval Rule — Creates a control surface by granting specific actors authority to adjust a state within limits.
- Feature Flag — Implements a software control surface by allowing behavior to be enabled, disabled, targeted, or rolled out without redeploying the whole system.
- Manual Override — Creates a bounded path for human intervention when automated or default control is insufficient, unsafe, or too slow.
- Policy Lever — Creates an institutional surface by changing eligibility, incentives, penalties, permissions, caps, or administrative rules.
- Controlled Reentry: Reintroduce flow, load, or exposure in bounded stages under feedback so recovery does not recreate the failure that required protection.
- Convergence Guidance: Guide an iterative process toward a stable target by using feedback, constraints, and correction rules.▸ Mechanisms (8)
- Behavioral Coaching Loop — Moves a person's performance toward a target behavior through observation, feedback, and supported practice, then checks the behavior holds across contexts without overriding their agency.
- Convergence Dashboard — Renders a converging process on one screen — target distance, update history, stability windows, and divergence alarms — so settling is visible and a stall raises an alert, without itself applying any correction.
- Facilitated Alignment Session — Steers a group from scattered interpretations toward a stable-enough shared direction by surfacing disagreement, protecting dissent, and escalating when alignment stalls.
- Iterative Design Review Cycle — Drives a design toward release-readiness by judging each version against a fixed acceptance brief and test evidence, applying revision rules until reviews stop surfacing severe problems.
- Learning Progression Feedback Loop — Advances a learner through scaffolded practice, formative feedback, and remediation until performance stabilizes and transfers to unfamiliar tasks.
- Model Fitting Loop — Repeatedly adjusts a model's parameters against an error signal until fit stabilizes, with held-out checks guarding against converging on noise.
- Policy Refinement Cycle — Revises a rule toward workable stability using implementation feedback, exceptions, and compliance data on a fixed review cadence, within legal and budget bounds.
- Process Control Tuning — Tunes a controller's parameters so a dynamic system settles on its setpoint instead of drifting, overshooting, or oscillating, within the actuator's limits.
- Coordination Scaffold Load Control: Keep the support machinery for coordination from becoming a second workload larger than the work it exists to coordinate.▸ Mechanisms (10)
- Async Decision Log — Replaces standing status and decision meetings with a durable written record — each decision captured with its rationale, owner, and the artifact it governs — so coordination happens by reading, not by convening.
- Coordination Artifact Kill Switch — A standing rule that lets a named owner unilaterally and reversibly pause or remove any coordination artifact that can no longer name the decision it improves — putting the burden of proof on keeping it, not killing it.
- Coordination Load Audit — A point-in-time investigation that inventories every coordination scaffold on an activity, measures the burden it consumes, flags recursion, and computes what value it actually returns.
- Delegation Authority Matrix — A document that maps which role holds decision authority for each class of decision, so routine matters resolve locally instead of climbing an escalation chain.
- Exception-Based Oversight — Leaves routine work to run on local autonomy and engages oversight only when a predefined exception tripwire fires — so attention is spent on the anomalies, not the normal case.
- Governance Forum Consolidation — Merges overlapping committees, boards, and review forums into a smaller set with clear remits, collapsing the meetings-about-meetings that recursive governance breeds.
- Handoff Path Pruning — Removes redundant handoff and approval hops from a workflow so work traverses only the coordination edges that actually change the outcome.
- Meeting Budget — Caps the coordination capacity a team may spend — meeting-hours, standing forums, recurring syncs — as a hard budget, so adding one coordination event requires retiring another.
- Support Layer Sunset Review — Attaches an expiry date to every support layer and forces a scheduled review at which it must re-justify its existence or lapse by default.
- Work-Before-Metawork Ratio Dashboard — Continuously tracks the ratio of primary work to coordination overhead against the activity it serves, turning creeping metawork into a visible, watched signal.
- Cycle Breaking: Interrupt a recurring harmful cycle at a point where the next recurrence can be prevented.▸ Mechanisms (8)
- Commitment Device — Locks in the focal goal ahead of time by making defection to a competing goal costly, penalized, or impossible — so the choice is settled before willpower is tested.
- Conflict Cycle Interruption Protocol — Rewrites the timing, repair, and communication rules of a recurring clash so each side's reaction stops becoming the other side's next trigger.
- Debt Cycle Interruption — Breaks a self-financing shortfall by attacking the rollover point and standing up a substitute buffer, so one money emergency stops funding the next.
- Environmental Trigger Removal — Removes or redesigns the surroundings, defaults, and exposures that fire the recurring behavior, so the cue is gone before the loop can restart.
- Habit Loop Disruption — Rewires the cue-routine-reward loop of an automatic behavior — keeping the reward, swapping the routine — so the habit no longer restarts on its own.
- Recurring Incident Prevention — Closes the loop on repeat failures by pairing each corrective action with verification that the same incident class does not come back.
- Relapse Prevention Plan — Maps the high-risk states of a fragile recovery and pre-loads early support, so a single lapse does not restore the full pattern.
- Root-Cause Corrective Action — Drills past the visible failure to the one condition that keeps producing it, and removes that condition so the failure mode stops recurring.
- Displacement-Aware Capacity Admission: Before admitting or expanding one activity in a finite shared substrate, identify what it will displace and protect, resize, phase, offset, relocate, or reject the expansion accordingly.▸ Mechanisms (9)
- Capacity Reservation Rule — A rule that reserves part of the shared substrate for incumbent, public-good, safety, ecological, or vulnerable uses.
- Crowding-Out Monitoring Dashboard — A dashboard tracking substrate utilization, entrant growth, incumbent shrinkage, protected-floor violations, and mitigation status.
- Displacement Impact Assessment — A pre-admission assessment estimating which incumbent uses will shrink when a new activity consumes shared substrate.
- Incumbent Use Register — A register of existing formal and informal uses of a shared substrate, including protected functions and dependency strength.
- Moratorium and Reversal Gate — A stop rule that pauses or reverses expansion when observed displacement crosses protected thresholds.
- Offset or Relocation Plan — A plan for relocating displaced activity, expanding substrate, compensating affected parties, or substituting alternate capacity.
- Phased Admission Trial — A staged rollout of the entrant with measurement gates, rollback authority, and incumbent impact review.
- Shadow Displacement Accounting — A counterfactual accounting method that estimates what incumbent activity would have remained without the entrant.
- Substrate Capacity Budget — A budget stating total shared capacity, reserved floors, discretionary slack, phase-in allowance, and emergency reserve.
- Distributed Authority Checks and Balances: Prevent any one authority from becoming final over its own consequential actions by distributing power, information, review, and correction across independently capable and mutually constrained bodies.
- Divergence Detection and Correction: Detect when a process is moving away from its target and correct course before divergence compounds.▸ Mechanisms (8)
- Learning Remediation Loop — Detects when practice is reinforcing an error rather than building mastery and changes the explanation, sequence, or feedback before the wrong pattern sets.
- Loss-Limit Correction Rule — Fires a pre-set exit when cumulative loss or exposure crosses a hard limit, cutting risk mechanically before divergence compounds — regardless of the story behind it.
- Model Training Divergence Monitor — Watches training and validation curves to catch when repeated updates are worsening fit, separating a real divergent trend from ordinary noise before compute is wasted.
- Negotiation Derailment Repair Protocol — Detects when a negotiation is hardening positions instead of converging, and applies structured repair moves — reframe, separate issues, caucus, escalate — without coercing false agreement.
- Policy Drift Review — Audits how a policy is actually being implemented in the field against its stated intent, using independent evidence, and escalates the gap to the policy owner.
- Process Control Alarm and Tuning — Trips an alarm when a running process moves outside its operating target, then tunes parameters or restores the last good configuration to bring it back.
- Project Drift Correction Review — Periodically compares a project's current work against its own charter, scope, and decision record to tell disciplined adaptation apart from unjustified drift — and resets scope when it has drifted.
- Runbook-Based Course Correction — Maps known divergence signatures to pre-written diagnosis checks and corrective actions for fast, repeatable response — with an escalation path when the pattern is unfamiliar.
- Donor-Coupled Capacity Governance: When a recipient appears viable because a donor/source continuously sustains it across a boundary, make the subsidy explicit, test real capacity, and choose continuation, formalization, transition, or withdrawal safeguards.▸ Mechanisms (9)
- Capacity Milestone Agreement — Defines the recipient capabilities and evidence required before support changes or autonomy claims are accepted.
- Cross-Boundary Support Agreement — Formalizes rights, obligations, data sharing, support levels, review cadence, and exit/continuation rules.
- Donor Stress Test — Examines whether the donor can maintain the subsidy under shocks without degrading its own critical functions.
- Source-Sink Monitoring Dashboard — Tracks donor flow, recipient baseline, support share, donor stress, and autonomy-claim status over time.
- Subsidy Dependency Assessment — Assesses how much of recipient performance depends on donor flow and which functions would fail without it.
- Subsidy Ledger — Maintains a visible record of support flows, costs, beneficiaries, duration, and governance terms.
- Support Load Quota — Caps donor obligation or hidden subsidy share until support is diversified, repriced, or capacity is increased.
- Taper and Handoff Plan — Coordinates staged reduction, localization, substitution, or formalization of support with contingency buffers.
- Withdrawal Rebound Drill — Simulates or rehearses support loss to reveal rebound failure paths and needed buffers.
- Emergent Pattern Detection: Detect system-level patterns that arise from local interactions before they become entrenched, harmful, or missed opportunities.▸ Mechanisms (8)
- Anomaly Detection — Flags unusual deviations in local or aggregated signals that may indicate a newly forming macro-pattern.
- Ecosystem Monitoring — Collects distributed environmental or ecosystem observations to detect emergent changes in populations, habitats, flows, or interactions.
- Emergent Behavior Dashboard — Displays aggregated local signals, pattern hypotheses, uncertainty, and response status in a visible review surface.
- Incident Pattern Mining — Analyzes many incidents, near misses, support cases, or complaints to discover system-level patterns no single incident reveals.
- Organizational Sensing — Uses surveys, interviews, retrospectives, behavior traces, and local reports to detect patterns forming inside an organization.
- Social Pattern Monitoring — Observes recurrent shifts in norms, roles, rumor, participation, exclusion, or informal coordination across a social system.
- Trend Detection — Tracks directional change across repeated local events or behaviors to identify patterns that are becoming stronger or more widespread.
- Weak-Signal Aggregation — Combines small, ambiguous local signals so a faint system-level pattern can become visible before it is obvious.
- Equilibrium Restoration: Restore a destabilized system toward a viable balance among opposing forces, flows, demands, constraints, or incentives.▸ Mechanisms (8)
- Budget Rebalancing Cycle — A recurring cycle that realigns commitments, reserves, and inflows to a target risk-and-reserve band when spending drifts out of balance.
- Conflict Mediation Process — A structured process for restoring workable relation among parties in conflict.
- Ecological Restoration Action — A staged intervention that returns a degraded living system to a resilient dynamic range by adjusting species pressure, habitat, and flows.
- Homeostatic Adjustment Protocol — A sensor-feedback-actuator protocol that drives a disturbed variable back inside its setpoint band and holds it there.
- Market Stabilization Operation — A procedure for dampening destabilizing market shortages, liquidity problems, or price swings.
- Operational Stabilization Playbook — A documented set of triggers, actions, owners, and monitoring rules for restoring system stability.
- Supply-Demand Rebalancing — A method for restoring workable relation between available supply or capacity and demand or need.
- Workload Rebalancing Workflow — A workflow for redistributing work, queue position, staffing, or support when burden has become destabilizing.
- Experience Curve Cost Reduction: Turn repeated production or practice into a measurable experience curve so each accumulated unit teaches the system how to make the next unit cheaper, faster, safer, or less error-prone without hiding quality loss.▸ Mechanisms (11)
- After-Action Review — Turns a just-finished episode into validated lessons by reconstructing what was intended versus what actually happened and deciding which improvised moves earned a place in the repertoire.
- Cumulative Volume Cohort Analysis — Groups output into cohorts by cumulative experience and compares them under controlled conditions, so a cost or quality gain can be credited to real learning rather than scale, accounting, or an easier mix of work.
- Experience Curve Model — Fits the power-law between cumulative volume and unit cost into a single learning rate and a forecast — and flags when the curve is flattening and extrapolation should stop.
- Learning Rate Dashboard — Tracks the learning rate across sites side by side and pins every cost metric to a quality metric, so a cost that falls by hiding harm is caught on sight.
- Playbook Revision Cadence — A scheduled review that folds captured learning into the official playbook, pushes the update to everyone, and periodically asks whether to keep patching or redesign.
- Production Learning Log — A record kept at the workbench where each discovery, snag, and trick is written down the moment it surfaces, before it evaporates into tacit memory.
- Setup Reduction Workshop — A focused team event that re-engineers the changeover between runs — separating what must be done while stopped from what can be prepped while running — to collapse setup time and make small batches affordable.
- Simulation Drill Ladder — A graduated ladder of realistic drills that manufactures experience on purpose, so a team descends the learning curve in the simulator before the stakes are real.
- Standard Work Revision — The standing path that turns a validated improvement into the new canonical procedure — writing down the tacit knack, versioning the change, and making the better way the default way.
- Time-and-Motion Study — Decomposes a repeated task into standard, timed work elements so a unit's cost is measured element-by-element — turning a vague sense of slowness into a map of where the seconds actually go.
- Yield and Defect Pareto Review — A recurring review that ranks defects and yield loss by the vital few, checking that cost gains are real quality-neutral savings and aiming improvement effort where the losses actually are.
- Feedback Loop Redirection: Alter what an existing feedback loop senses, how strongly it acts, or what it targets so it drives the system toward a viable trajectory instead of reinforcing a bad one.
- Flow Channel Design: Match challenge, skill, feedback, and interruption boundaries so focused engagement can emerge.
- Flow Diversion / Rerouting: Redirect flow through an alternate viable path when the current route becomes blocked, overloaded, or harmful, rather than stopping the flow.
- Formative Feedback Loop: Use ongoing evidence of progress to adjust learning, support, and instruction before final performance is judged.▸ Mechanisms (11)
- Adaptive Practice Set — Reads each attempt and automatically picks the next item, difficulty, or scaffold, so the practice set continuously reshapes itself around exactly where the learner is still weak.
- Coaching Check-In — A recurring one-to-one conversation that reads recent evidence of progress together and turns it into concrete next actions — some the learner takes, some the coach commits to.
- Draft Feedback Cycle — Circulates an unfinished work product for feedback, has the author revise it, and re-reviews the revision, so the artifact improves across versions before it is ever finalized.
- Exit Ticket — A one-or-two-question prompt at the very end of a session that captures what landed and what's still murky, timed so the teacher can adjust the next session before the class moves on.
- Formative Rubric — Breaks 'quality' into named dimensions with described levels, so feedback can point at which dimension is weak and what the next level up actually looks like.
- Low-Stakes Quiz — Elicits a quick, ungraded read of current understanding across the material, timed early enough that the result can still change what happens next.
- Misconception Probe — Uses questions engineered so that each wrong answer reveals a specific misconception, turning a response directly into a named diagnosis rather than a score.
- Peer Review Protocol — Structures learners to critique each other's work against shared criteria before final judgment, so authors get early feedback and reviewers learn the standard by applying it.
- Practice Review — Reviews recorded practice attempts after the fact to pinpoint the error or strategy flaw and prescribe the specific next drill to fix it, before it matters in competition.
- Progress Dashboard — Aggregates progress indicators into a visible, persistent display so patterns and at-risk learners surface early enough to trigger support before it's too late.
- Rapid Feedback Cycle — Compresses the whole signal-feedback-response-recheck loop into very short, repeated intervals, so a learner corrects and re-attempts almost immediately rather than waiting for a later review.
- Fundamental-Anchor Bubble Damping: Separate genuine value discovery from self-reinforcing speculation by anchoring decisions to independent fundamentals, monitoring divergence, and adding damping rules before commitments become fragile.▸ Mechanisms (8)
- Blind Independent Valuation Review — Has an evaluator estimate value with recent price, popularity, and sponsor identity hidden, producing a valuation signal that cannot simply be an echo of the momentum it is meant to test.
- Bubble Premortem — Assumes the boom has already collapsed and works backward to name what future observers will call obvious — the ignored anchor, the channels that amplified the loop, and the doubts nobody wrote down.
- Concentration and Exit-Capacity Test — Stress-tests whether a crowded position could actually be unwound — measuring realizable exit capacity against paper value for the case where everyone heads for the same door at once.
- Leverage and Margin Limit — Caps how much borrowed exposure the credit channel can add and tightens the cap automatically as leverage climbs, so no participant is forced to rely on continued appreciation just to stay solvent.
- Momentum Cooling-Off Rule — Inserts a mandatory delay — an individual waiting period, and a venue-wide halt when moves go extreme — between the impulse to commit and the commitment itself, so a decision driven by momentum has to survive a cooling interval before it executes.
- Narrative Red-Team Review — Assigns a designated challenger to attack the bull case on its merits, testing whether 'this time is different' is real evidence or just the loop describing itself — and logging the exchange.
- Staged Commitment Gate — Releases commitment in tranches, opening each gate only when the independent anchor has actually improved — so irreversible expansion never runs ahead of the evidence that would justify it.
- Valuation-Anchor Dashboard — Displays the momentum signal beside its independent value anchor on one live view, so the divergence between them — and the bands where damping is meant to fire — is legible at a glance instead of reconstructed after the fact.
- Harmful Emergence Containment: Constrain or redirect unintended emergent behavior before local interactions create system-level harm.▸ Mechanisms (10)
- Anti-Herding Interventions — Breaks pile-on and panic dynamics by restructuring the imitation signals — visibility, timing, and diversity — so local actors decide from their own information instead of copying the crowd.
- Anti-Spam Rules — Places local posting, account, and message constraints — with allow-listed exceptions — on the channels where many small sends aggregate into systemic spam or abuse.
- Autonomous Agent Safety Constraints — Bounds the permissions, rates, and objectives of autonomous agents inside a defined interaction boundary, re-tuning the limits as the agents adapt, so their local actions cannot aggregate into unsafe system behavior.
- Commons Governance Rules — Caps and coordinates local use of a shared resource through participant-set, monitored, adjustable limits so aggregate use stays within collective viability.
- Emergent-Risk Moderation — Moderates behavior by its contribution to a forming harmful macro-pattern rather than by isolated rule violations, adjusting thresholds as the pattern shifts.
- Friction Insertion — Adds delay, effort, cost, or confirmation at the precise points where a harmful pattern accelerates, damping the loop without banning the action.
- Market Circuit Breakers — Automatically halts or slows trading in staged steps when an aggregate volatility threshold is crossed, damping a self-reinforcing panic without closing the market for good.
- Platform Abuse Controls — Runs distributed abuse through an end-to-end pipeline — detect the pattern, throttle or restrict, adjudicate appeals, and watch for displacement — to contain coordinated misuse.
- Quota or Rate-Limit Mechanisms — Bounds how much or how fast any actor may act — content-blind, per-actor caps scoped to a class or channel — and monitors aggregate throughput to keep it from driving system harm.
- Rumor Containment Protocol — Interrupts a propagating false claim by damping its forwarding, injecting a verified counter-signal, and tracking whether it mutates or jumps channels.
- Helplessness Reversal: Restore perceived controllability through small real choices, visible effects, and agency feedback.▸ Mechanisms (8)
- Action-Effect Feedback Review — A recurring review that attributes what an action did and did not change, updating the actor's read on what is now within their control.
- Choice Reintroduction Protocol — Reintroduces a bounded menu of real, non-token choices after a period in which choosing was absent, ignored, or punished.
- Controllability Mapping Checklist — Sorts a situation into controllable, influenceable, constrained, and uncontrollable parts before any action is chosen.
- Graduated Responsibility Ramp — Widens the scope and difficulty of a controllable action step by step, only after each prior step has produced a credible success.
- Setback Reset Protocol — After a blocked or failed action, re-separates what remains controllable from what failed and picks the next feasible step before the setback hardens into global futility.
- Small-Win Loop — Repeatedly turns one small, genuinely controllable action into a completed and observed win, banking action-effect evidence a single cycle at a time.
- Supported Problem-Solving Session — A facilitated working session that surfaces the controllable slice of a problem and clears its barriers without the helper taking the action over.
- Visible Progress Tracker — A persistent record that externalizes accumulated small wins so the actor can see, across attempts, that effort has produced change.
- Homeostatic Regulation: Regulate key variables within a viable range through sensing, comparison, and corrective response.▸ Mechanisms (10)
- Alert Threshold and Escalation — A monitoring protocol that raises graded alerts and routes them to progressively higher authority when a variable crosses a warning threshold or ordinary correction is failing — handing control to a human rather than correcting itself.
- Budget Variance Correction Cycle — A periodic governance review that compares actual spending and revenue against an approved plan, judges whether the variance is material, and orders corrective decisions when it is.
- Control Loop Tuning — Sets the standing gains, damping, and deadband of a fixed-structure controller so the loop is fast enough to follow the moving target yet damped enough not to oscillate or amplify noise.
- Inventory Reorder Point Control — A standing rule that triggers a replenishment order of a set quantity whenever stock falls to a reorder point sized to cover demand over the supplier's lead time.
- Physiological Regulation Protocol — A clinical protocol that keeps a physiological variable inside a therapeutic window by titrating a corrective intervention in graded steps and escalating care when titration cannot hold the range.
- Policy Feedback Control — A governance method that adjusts policy levers when a monitored societal indicator drifts outside agreed bounds, contending with a contested setpoint and an authorized override on the levers.
- Quality Control Loop — An inspect-and-correct workflow that adjusts the process when output quality drifts out of tolerance, and scraps, reworks, or halts the line when correction cannot recover it.
- Staffing Level Adjustment — A workflow that senses live workload and flexes the number and assignment of staff toward a service target, bounded by the finite pool of people actually available to deploy.
- Statistical Process Control — Charts a process variable against statistically derived control limits so that genuine drift is distinguished from ordinary random variation and flagged before it becomes a defect.
- Thermostat Control — A self-contained device that senses a physical variable, compares it to a setpoint, and switches an actuator on or off to hold the environment inside a narrow band with no human in the loop.
- Instability Dampening: Reduce the tendency of small disturbances to amplify into larger failures or swings.
- Intermediate-State Throughput Control: Treat a named transient state as a controllable intervention surface: regulate how fast it forms, how long it persists, how its quality changes, and how reliably it converts into the desired next state.▸ Mechanisms (12)
- Batch Size Tuning — Sets how many items are grouped before they move to the next stage, trading per-item overhead against the residence time and pile-up that large batches create.
- Conversion Capacity Boost — Raises the throughput of the stage that converts the intermediate into the next state, so a growing in-process pool is drained rather than throttled at the source.
- Formation Throttle — Regulates how fast the intermediate is created, applying backpressure at the source so it forms no faster than the next stage can consume it.
- Holding Condition Control — Maintains the conditions under which the intermediate is held so its quality decays as slowly as possible during the time it must wait.
- Intermediate State Tagging — Attaches a machine-readable label to each in-process item recording which intermediate state it is in and since when, turning an invisible middle into something you can see and query.
- Priority by Age or Risk — Orders which in-process items are converted next by their age or their risk, so the oldest or most dangerous intermediates don't linger while newer, safer ones jump ahead.
- Quench or Stabilization Step — Deliberately arrests the intermediate's tendency to degrade or react further — freezing it into a stable, hold-able form — so its quality and hazard stop being a function of time.
- Residence-Time Dashboard — Makes the invisible dwell time of in-process items visible, tracking how long each has sat in a state against an acceptable residence-time window so aging is caught before it becomes failure.
- Side-Path Suppression — Raises the fraction of the intermediate that exits down the desired branch by blocking the competing side-paths that leak, divert, or spoil it.
- Stage Handoff Check — Gates each transfer between stages, verifying the in-process item meets the next stage's entry criteria and routing it forward or back for rework at the boundary.
- Stale Item Sweep — Periodically finds in-process items that have aged past usefulness and routes them out of the state via a defined disposition path, so stale work stops occupying and contaminating the pipeline.
- WIP Limit by Intermediate State — Caps how many items may occupy a named in-process state at once, so the ceiling itself becomes a backpressure valve that forces inflow to match outflow.
- Inversion of Control: Shift initiative or control from the usual actor to another layer, framework, recipient, or environment to reduce coupling, improve fit to context, or coordinate action more cleanly.▸ Mechanisms (8)
- Callback Function — Allows one part of a system to provide behavior that another part invokes later when a lifecycle event, completion condition, or external signal occurs.
- Dependency Injection Framework — Implements software inversion by letting a framework supply dependencies or call application behavior through configured interfaces instead of having application code directly construct or control everything.
- Event Listener or Webhook — Lets external events or remote systems initiate behavior through a registered interface rather than requiring continuous polling or upstream push.
- Just-in-Time Replenishment Rule — Triggers production or replenishment from actual downstream demand or threshold signals rather than forecast push alone.
- Kanban Pull System — Uses downstream readiness or consumption to authorize upstream work, turning a push process into a governed pull process.
- Learner-Led Inquiry Protocol — Lets learners initiate questions, projects, or evidence-seeking activity while instructors provide constraints, scaffolds, and feedback.
- Participant Agenda Setting — Lets affected participants initiate topics, decisions, or priorities within a governed forum instead of only receiving a centrally defined agenda.
- Recipient-Triggered Support Channel — Lets the person or unit experiencing need activate support when conditions are met rather than waiting for a provider-driven schedule.
- Iterative Refinement Loop: Improve an output through repeated cycles of attempt, feedback, correction, and reevaluation.▸ Mechanisms (9)
- Agile Sprint — Provides a time-boxed cadence for building, reviewing, learning, and adjusting work, when sprint outputs actually feed revision decisions.
- Coaching Session — Implements behavior refinement by observing a performance attempt, providing targeted feedback, and setting the next practice focus.
- Design Iteration — Implements refinement by using sketches, prototypes, user feedback, design changes, and retesting to improve a designed artifact or service.
- Draft Review Cycle — Implements the archetype for documents, plans, designs, or analyses by routing drafts through critique, revision, and approval.
- Model Tuning Loop — Implements refinement for statistical, machine-learning, or simulation models by adjusting model choices based on validation feedback and constraints.
- Plan-Do-Check-Act Cycle — Refines a repeating process by planning a small change, trying it, checking the result against the prediction, and standardizing or adjusting on the learning.
- Policy Pilot Cycle — Implements refinement for policy or program change by trying a bounded version, measuring effects, revising design, and deciding whether to scale, stop, or modify.
- Retrospective Action-Item Loop — Implements team or operational refinement by turning review observations into specific changes that are checked in the next cycle.
- Scientific Experimentation Cycle — Implements refinement through hypothesis, test, evidence interpretation, and revised hypothesis or design.
- Leverage Point Intervention: Target a small, strategic intervention point where change produces disproportionate system-wide effects.▸ Mechanisms (10)
- Bottleneck Intervention — Relieves the single capacity-limiting stage whose constraint governs the throughput of the whole flow, so the system speeds up without adding effort everywhere.
- Default Setting Shift — Changes the pre-selected option or normal path so repeated choices aggregate differently, without asking every actor to decide anew.
- Feedback Loop Rewiring — Alters the gain, delay, or polarity of a reinforcing or balancing loop that is maintaining an unwanted pattern.
- Goal Reframing — Changes the stated objective or success criterion so that local optimization begins to serve a different system-level aim.
- Incentive Change — Adjusts rewards, costs, or recognition at a compact point so the strategic behavior of many actors shifts in the intended direction.
- Information Flow Change — Changes who sees which signal, when, and in what form, so decisions across the system shift without commanding any of them directly.
- Policy Lever Targeting — Acts through a formal instrument of authority — a permit, tax, subsidy, eligibility rule, or enforcement trigger — calibrated and legitimated as the point of intervention.
- Rule Change — Alters the formal or informal rule that structures many downstream actions, permissions, and interpretations at once.
- Small Safe-to-Fail Probe — A deliberately small, contained trial that tests whether a proposed facilitator really lowers the barrier — and preserves selectivity — before it is trusted at scale.
- Structural Leverage Analysis — Compares candidate intervention points by depth, coupling, amplification, tractability, and risk, and records why one point was chosen over the visible alternatives.
- Load Balancing: Distribute incoming work across multiple viable receivers by capacity, health, or policy so no part is overloaded while usable capacity sits idle.
- Load Leveling / Demand Smoothing: Redistribute demand or work over time to smooth destabilizing peaks and preserve stable utilization.
- Mental Model Mismatch Repair: Detect and repair mismatches between a person's mental model and how the system actually behaves.▸ Mechanisms (8)
- Documentation Revision — Rewrites the reference text — stale wording, missing examples, hidden edge cases — so the correct model is retrievable at the moment of action.
- Expectation Audit — Traces where an expectation, label, or score enters a process and maps the behavior channels through which it may be quietly manufacturing its own confirmation.
- Incident Mental-Model Review — Reconstructs what operators believed during a real failure, infers what the system actually did from triangulated traces, and diagnoses why the two diverged.
- Interface Affordance Redesign — Changes the labels, defaults, previews, and status cues a system emits so it stops inviting the wrong expectation, repairing the system rather than blaming the user.
- Simulation-Based Correction — Lets people live the mismatch safely in a realistic replica, rehearse the corrected model, and prove it transfers to a new scenario before real consequences occur.
- Training Feedback Loop — Turns recurring expectation failures across a population into revised training and monitors whether the same mismatch keeps coming back.
- Usability Testing — Puts fresh users in front of the system, asks what they expect before they act, and records what it actually does — turning the expected-versus-actual gap into observed evidence.
- User Journey Diagnostics — Traces a whole sequence of touchpoints to find where a wrong expectation accretes, mapping the assumptions that build up when no single screen or message created the mismatch alone.
- Minimum Viable Learning Release: Release the smallest usable solution that can validate core need and guide the next design step.▸ Mechanisms (8)
- Alpha Release — Puts a rough, still-unstable build in front of a small circle of trusted users in real conditions to surface defects and interaction problems early.
- Concierge Test — Delivers the promised outcome entirely by hand, before any product exists, to learn whether the value is real and wanted.
- Feature-Flag Release — Wraps a change in a runtime toggle so it can be exposed to a controlled slice of live traffic and ramped up or rolled back instantly on evidence.
- Limited Cohort Rollout — Exposes a finished change to a defined, representative slice of users so the evidence generalizes beyond enthusiasts and early adopters.
- Minimum Viable Process — Runs the smallest real version of a workflow that still does actual work, to reveal handoffs, exceptions, and throughput before formalizing it.
- Minimum Viable Product — Ships the smallest usable product that still delivers the one core benefit, so real usage — not opinion — decides whether the rest gets built.
- Pilot Service — Runs a full but deliberately bounded version of a service for one population or site, with declared support and a fixed window, to see whether it holds up in real delivery.
- Small-Batch Policy Pilot — Tests a new rule or process on one narrow category, with equity safeguards and a fixed review, before writing it into general policy.
- Mode-Setting Gain Modulation: Use a separate noncontent channel to retune how many content channels are processed, so the system changes sensitivity or mode without rewriting the content itself.▸ Mechanisms (10)
- Adaptive Attention Gain Rule — Continuously reads the live context and raises or lowers processing gain across a population of units in a closed loop, so weak-but-important signals surface and routine noise stays quiet.
- Control/Data Channel Separation Test — Probes whether control instructions can leak into the content channel, confirming that setting the mode is structurally walled off from what the content says.
- Gain Schedule Table — A precomputed lookup mapping each named operating regime to its right gain or mode setting, so the system reads its regime and applies stored values instead of re-deriving them.
- Homeostatic Setpoint Retuning — Slowly shifts the baseline setpoint that fast modulation regulates around, so a population keeps its dynamic range as conditions drift over the long run.
- Mode-Effect Backtest — Replays historical mode-state and outcome traces to test whether a gain or mode policy actually improved processing, separating changed posture from a changed world.
- Mode-State Dashboard — A live operator-facing display of the current mode and gain state across processors, so hidden modulation becomes visible before it distorts interpretation.
- Modulator Decay Timer — Automatically decays an elevated modulator back to baseline after a set interval, so a high-gain or alert posture cannot silently persist past the context that justified it.
- Modulatory Release Gate — Gates whether and when a modulator is released to act, firing the mode change only when a guarded trigger condition is met.
- Operating Mode Broadcast — Distributes a decided operating mode to every unit within a bounded scope, changing how they process without touching the content each one carries.
- Precision-Weighting Update Rule — Sets the gain on each incoming signal in proportion to its estimated reliability, so precise evidence moves the system and noisy evidence is discounted.
- Model-Based Regulation: Embed a decision-relevant, continuously tested model of the system inside its regulator so interventions are state-aware, predictive, auditable, and revisable.▸ Mechanisms (15)
- Bayesian State Estimation — Infers the system's hidden state and its uncertainty by recursively updating a probabilistic estimate as each noisy observation arrives.
- Causal Loop Diagram — Draws the pressure behind a hazard, the feedback loops that regenerate it, and the delays between them, so a control can be aimed at the loop rather than the symptom it displaces.
- Champion–Challenger Evaluation — Runs the incumbent regulating model against candidate challengers on the same objective and promotes a challenger only when it beats the champion by a pre-set margin.
- Digital Twin Trial — Exercises a candidate policy against a synthetic, executable replica of the system — including conditions that have never actually occurred — before it is allowed to touch the real thing.
- Forecast Backtesting — Replays a predictor against withheld history — across time, segments, and regimes — to earn or deny the right to suppress its residuals.
- Historical Replay — Reruns a candidate policy over real recorded history to see what it would have decided, then measures those counterfactual decisions against what actually happened.
- Model Predictive Control — At each step, optimizes a whole sequence of near-term actions against a forecast of the moving target — subject to hard constraints — then commits only the first action and re-optimizes when the next observation lands.
- Model Registry — The system of record for every regulating model — its lineage, assumptions, owner, approvals, and deployment status — so any model in production can be traced, re-approved, or rolled back.
- Model-Failure Red Team — An independent team whose mandate is to make the model fail — hunting the conditions under which it gives wrong answers, mapping that failure frontier, and checking the system degrades safely past it.
- Residual-Monitoring Dashboard — Continuously tracks the gap between what the model predicted and what actually happened, so drift surfaces as a signal that triggers the model's revision.
- Scenario Testing — Checks the regulator against a curated set of plausible, extreme, and boundary situations, asking of each: does it stay within safe limits and degrade gracefully?
- Sensitivity Analysis — Sweeps the model's inputs and parameters across their plausible ranges to find which ones actually move its decisions — and whether the model's added complexity earns its keep.
- Shadow-Mode Evaluation — Runs a candidate policy silently on live inputs with zero authority to act, logging what it would have done so its divergences from reality can gate promotion.
- State-Space Model — Specifies the target as a hidden state that evolves by known dynamics and is seen only through a noisy observation equation — the source model an estimator later inverts to pull the state back out.
- System-Identification Experiment — Builds the system model empirically by injecting designed inputs into the real system and fitting the observed response, its disturbances, and the assumptions the fit rests on.
- Moving-Target Tracking: Treat the objective as a time-varying reference and jointly tune target governance, sensing, prediction, planning, and response so cumulative tracking error remains bounded while the target moves.▸ Mechanisms (17)
- Adaptive Control Method — Lets the controller re-tune its own gains in real time as the system's dynamics or the target's behavior shift — self-adjusting within a protected safety envelope rather than waiting for a human to re-tune.
- Change-Point Detection — Flags the moment the target jumps to a new regime — an abrupt discontinuity the current tracking mode can no longer follow — so the loop switches modes instead of chasing a break as if it were noise.
- Control Loop Tuning — Sets the standing gains, damping, and deadband of a fixed-structure controller so the loop is fast enough to follow the moving target yet damped enough not to oscillate or amplify noise.
- Model Drift Monitoring — Watches a live predictor for the slow slide where yesterday's model quietly stops fitting today's world — before the residuals it suppresses start hiding real change.
- Model Predictive Control — At each step, optimizes a whole sequence of near-term actions against a forecast of the moving target — subject to hard constraints — then commits only the first action and re-optimizes when the next observation lands.
- Model Retuning — Deliberately re-fits the predictive model — its parameters, features, and calibration — to current data so its forecasts stay accurate as the tracked relation drifts, on a turnaround that must beat the drift it is correcting.
- Objective Versioning and Change Log — An append-only record of every authorized objective version — each with its effective date, authority, rationale, and dependencies — so exactly one legitimate target governs each decision and target motion is attributable rather than ambient.
- Online Incremental Learning — Keeps a predictive or decision model locked onto a moving target by updating it continuously from validated new evidence, instead of letting it go stale between infrequent full retrains.
- Policy Recalibration — The deliberate procedure for revising an operating policy when the moving objective makes the prior rule unfit — escalating when no policy can meet the target, and rolling back a recalibration that misfires.
- Receding-Horizon Planning — Plans over a look-ahead horizon but commits only the near term, then rolls the horizon forward and re-optimizes as the target and state move — trading plan permanence for continuous course-correction.
- Rolling Forecast Review — A scheduled and event-triggered ritual that re-forecasts where the target is heading and refreshes the scenario spread, so plans always ride current evidence rather than a fixed period boundary.
- Rolling Planning Cycle — A recurring planning cadence that folds each authorized target change into a rolling multi-horizon schedule, so replanning happens on a predictable rhythm instead of on impulse.
- Rolling Window Comparison — Quantifies how much the target, state, and error distributions have drifted by comparing a recent window against earlier ones — turning gradual staleness into a measured magnitude rather than a yes/no event.
- Smith Predictor or Model-Predictive Compensation — Acts on where the system will be when the command actually lands, using a model to see past a known delay instead of chasing the stale state the sensor still reports.
- State-Estimation Filter — Fuses noisy, delayed observations into a single best current-state estimate on the target's clock, separating true state from measurement noise and reporting lag.
- Target Freeze or Change Window — Declares bounded windows when the target may be revised and windows when it is frozen, so execution and validation get a stretch of stable ground even while the target is moving.
- Target-Update Rate Limiter — Throttles the size and frequency of discretionary target revisions to what the tracking loop can actually absorb, converting jittery goal-chasing into changes the system can follow without churn.
- Neighbor-Suppression Contrast Sharpening: Sharpen a crowded field by allowing strong focal signals to locally inhibit nearby competitors, while keeping enough context and recovery to avoid erasing valid neighbors.▸ Mechanisms (12)
- Alert Neighbor Dimming Rule — During an active incident, temporarily dims its dependent lower-priority alerts — with guaranteed auto-restore and a logged record of what was hidden and why.
- Boundary-Sharpening Review Map — Lays the raw field beside the sharpened output, marks which neighbors were suppressed, and scores whether the sharpening actually improved detection.
- Center-Surround Filter — Re-expresses every location as its own activation minus a weighted average of its surround, so uniform regions cancel and only edges survive.
- Competitive Priority Board — A shared priority surface where promoting one item to focus visibly demotes its competing neighbors, forcing a few sharp winners out of a flat list.
- Context-Restoration Toggle — A reversible control that brings suppressed neighbors and the original field back on demand, so a reader can see what the sharpening hid before trusting it.
- Contrast-Adaptation Tuning Loop — A closed loop that raises or lowers inhibition strength and neighborhood size to hold a target balance of false positives and false negatives as the field drifts.
- Ecological Spacing Buffer — Keeps similar elements far enough apart that a strong one's influence fades before it reaches its neighbors, so distinctions stay clean without any of them being erased.
- Inhibitory Feedback Circuit — A physical web of negative connections between neighbours, so that whenever one unit fires hard it automatically quiets those around it — sharpening the whole field with no central controller.
- Local Contrast Enhancement Transform — Subtracts a local average from every point so local differences are amplified and edges pop — with a threshold that stops it from turning noise and halos into fake detail.
- Mutual-Exclusion Choice Gate — Lets only one of several competing choices proceed at a time, holding the close rivals back on a timer rather than deleting them, so exactly one wins now and the others get their turn later.
- Non-Maximum Suppression Pass — Scans a field of overlapping candidate detections and, around each local peak, deletes the weaker near-duplicates, so every real feature ends up represented exactly once.
- Over-Suppression Red Team — Deliberately attacks the suppression rule to surface the valid weak signals it has been quietly erasing — the minority views, faint evidence, and rare safety-critical cases hidden among the losers.
- Nested Feedback Alignment: Align feedback loops across nested levels so local correction does not create system-level instability.▸ Mechanisms (10)
- Aggregation/Disaggregation Dashboard — Lets users inspect aggregate patterns while drilling down to local variation so feedback decisions do not hide heterogeneity.
- Balanced Scorecard Cascade — Translates strategic goals into nested local indicators while preserving counterbalancing metrics so units do not optimize one target at the expense of another.
- Bullwhip Effect Review — Checks whether ordering, forecasting, or inventory feedback at one tier is amplifying variability at another tier of a supply chain.
- Cross-Scale Retrospective — Brings participants from multiple levels together after a cycle, disruption, or intervention to identify mismatched signals, timing, gain, and escalation rules.
- Ecological Adaptive Management Cycle
- Governance Escalation Protocol — Specifies when local governance handles a signal, when regional or central governance intervenes, and how authority returns after the condition stabilizes.
- Incident-Command Feedback Rhythm — Coordinates tactical reports, operational decisions, strategic priorities, and after-action updates during incident response.
- Local/System Feedback Cadence — Synchronizes the rhythm of local reviews, aggregate reviews, retrospectives, budget cycles, incident reviews, or policy updates.
- Multi-Level KPI Review — Reviews local, intermediate, and system-level indicators together so a correction that improves one level is checked for consequences at the others.
- Nested Control-System Tuning — Tunes controller thresholds, gains, delays, and override rules when technical or operational control loops interact across nested subsystems.
- Norm Shaping: Deliberately shape shared norms so everyday behavior aligns with the system's desired values and operating model.▸ Mechanisms (10)
- Behavior Default Design — Reshapes ordinary routines, templates, and defaults so the target behavior becomes the path of least resistance — with an explicit low-friction opt-out so the default nudges rather than coerces.
- Culture Ritual — Uses recurring rituals, stories, recognitions, or routines to reinforce the target disposition and make it socially legitimate.
- Leadership Modeling — Has high-status actors visibly perform the target behavior first — and bear its cost publicly — so the norm reads as legitimate and safe for everyone below them to follow.
- Norm Audit — Surfaces the unwritten expectations and quiet sanctions that keep people reproducing a shared reality with no formal rule behind it, then tests whether anyone actually endorses them.
- Norm Drift Review — A recurring backward look that re-diagnoses what the group now treats as normal and flags where tolerated exceptions have quietly hardened into the new default.
- Onboarding Norm Translation — Inducts newcomers into a norm by conveying its purpose, worked examples, and the judgment it calls for — not just the rule text — so it arrives as something to understand rather than merely obey.
- Peer Reinforcement Protocol — A bounded, shared script that lets peers affirm, correct, or repair norm-relevant behavior in the moment — so the norm is held laterally, member to member, without waiting for authority.
- Recognition System — A standing program that gives attention, status, and reward to specific instances of the target behavior — transferring social standing to early adopters so the norm becomes something worth being seen doing.
- Stories and Symbols — Encodes the norm into memorable stories, language, and artifacts — including cautionary tales that mark its edges — so the expectation travels vividly and portably, even where no one is watching.
- Values-to-Behavior Translation — Converts an abstract value into a concrete list of observable behaviors, edge cases, and counterexamples, so people can tell what actually counts as living the value.
- Objective Boundary Governance: Prevent an objective from silently expanding by making sub-objective additions accountable to the original boundary, opportunity cost, and explicit re-charter rules.▸ Mechanisms (10)
- Deferred Objectives Backlog — A durable, visible queue where worthy-but-not-now objectives are parked with their rationale and revisit trigger, so 'no for now' doesn't mean 'lost forever.'
- Mission-Creep Audit — A periodic, backward-looking review — owned by the trajectory owner — that reconstructs how the effective objective has changed and names what has quietly crept in.
- Objective Change-Control Board — A standing forum that reviews each proposed addition against the admission rule, spends from a fixed exception budget, and enforces symmetric add/remove friction.
- Objective Charter — Fixes the original objective, its resource envelope, exclusions, and accountable owner in a written reference that every later addition must be judged against.
- Objective Drift Dashboard — An always-on instrument that renders dilution signals, ledger trends, and distance-from-baseline so objective creep shows up as a rising line, not a surprise.
- Opportunity-Cost Review — Prices what each proposed addition displaces — the next-best use of the same capacity — and puts that cost on the table beside the addition's benefit.
- Plus/Minus Boundary Review — A recurring ritual that admits a new objective only when a matching one is retired or parked, keeping addition and subtraction friction symmetric.
- Re-charter Workshop — A convened event that, when additions have outgrown the original charter, decides whether to prune, defer, or formally replace the objective with a new baseline.
- Sub-objective Decision Record — Captures each proposed addition as a standardized record — rationale, fit, displacement, owner, and removal condition — turning the objective's history into an inspectable ledger.
- Sunset Clause
- Objective Function Alignment: Define what is being optimized so search, incentives, and evaluation do not improve the wrong thing.▸ Mechanisms (10)
- Balanced Scorecard — Tracks multiple performance dimensions to reduce single-metric tunnel vision in organizations.
- Decision Criteria Rubric — Makes selection criteria explicit so ranking, approval, grading, or prioritization follows the intended objective and constraints.
- Guardrail Dashboard — Displays constraint, safety, fairness, quality, or side-effect indicators alongside the main objective score.
- KPI Governance — Manages organizational key performance indicators so targets guide the intended behavior rather than local score maximization.
- Loss Function Design — Translates desired model behavior into a mathematical penalty structure used during training or selection.
- Metric Design — Creates observable measures that approximate the intended outcome closely enough to guide action and review.
- Metric-Gaming Red Team
- Optimization Target Review — Periodically reviews whether the current objective, metric, or reward target still produces the intended outcomes under observed behavior.
- Policy Objective-Setting Workshop — Uses facilitated deliberation to define outcomes, constraints, stakeholder values, and unacceptable side effects before policy optimization begins.
- Reward Function Specification — Specifies what an agent or actor is rewarded for, often in automated, organizational, or behavioral systems.
- Observability Instrumentation: Instrument external signals so hidden internal state becomes inferable enough for monitoring, diagnosis, and control.▸ Mechanisms (10)
- Alerting Rule — Notifies responsible actors when observed signals cross thresholds that imply risk, failure, drift, or urgent state change.
- Audit Log — Keeps an append-only, attributable record of every action on protected data — who, when, and what changed — so integrity events can be investigated and reconstructed after the fact.
- Dashboard
- Health Check — Runs a repeatable test that indicates whether a service, asset, process, or organism is functioning within an acceptable range.
- Process Metric — Measures throughput, delay, error, rework, quality, or other process outputs that help infer hidden operational state.
- Sensor Array — Captures physical, environmental, biological, or machine signals that reveal hidden state such as temperature, pressure, vibration, movement, or exposure.
- Social Indicator — Uses surveys, reports, participation patterns, trust signals, complaints, or observed behavior to infer hidden organizational or social state.
- Synthetic Probe — Generates a controlled test event or request to infer whether the system responds as expected from the outside.
- Telemetry — Automatically emits operational measurements or events so system health, usage, load, or errors can be inferred over time.
- Trace Instrumentation — Links events across a distributed workflow so hidden bottlenecks, dependency failures, and state transitions can be diagnosed.
- Opinion Climate Recalibration Design: Break a silence spiral by making hidden pluralism safely visible, lowering the threshold for expression, and preventing public silence from being treated as proof of consensus.▸ Mechanisms (10)
- Aggregate Pluralism Disclosure — Publishes evidence that more than one position exists in the group while preserving subgroup privacy and avoiding individual targeting.
- Anonymous Pre-Expression Poll — Collects a private signal before public speaking, visible voting, or sequential endorsement creates additional conformity pressure.
- Confidential Opinion Climate Survey — Measures private position, perceived majority, perceived sanction risk, and willingness-to-speak thresholds without public exposure.
- Moderated Minoritarian Voice Window — Creates a protected, time-bounded opportunity for under-expressed views with explicit norms against ridicule, retaliation, or pile-on dynamics.
- No-Retaliation and Follow-Up Protocol — Commits authorities or moderators to monitor and respond to punishment after previously silent views become visible.
- Perceived Consensus Correction Note — Warns decision-makers or audiences that visible agreement is not reliable evidence of private unanimity under silence pressure.
- Post-Intervention Climate Audit — Rechecks fear, willingness to speak, perceived majority, and visible expression after the recalibration intervention.
- Protected First-Speaker Rotation — Assigns or invites first expression through a protected process so under-expressed views do not depend on a lone vulnerable volunteer.
- Silent-Start Written Input — Lets participants commit views or concerns privately before hearing dominant voices, reducing early climate-of-opinion distortion.
- Threshold Release Rule — Releases aggregate or representative signals only when safety, sample size, and anti-identification conditions are met.
- Opponent-Channel Regulation: Shape action through paired enablement and restraint so output comes from a calibrated local balance, not from one-sided activation or after-the-fact correction.▸ Mechanisms (9)
- Complementary Cap-and-Floor Rule — Bounds the pair with a hard ceiling on the activating side and a hard floor on the restraining side, so neither channel can run away or vanish.
- Dual-Actuator Calibration Test — Exercises the activating and restraining channels alone and together to measure each one's gain, timing, and health before they are trusted in service.
- Excitation–Inhibition Ratio Dashboard — Displays the live ratio and timing of the two opposed channels so hidden imbalance shows up before the net output does.
- Feedforward Brake Circuit or Protocol — Routes the same triggering input through an enabling path and a parallel restraining path timed to arrive before the enabled action can overshoot.
- High-Gain Degraded-Mode Trigger — Watches channel integrity and, the moment one side can no longer be trusted, drops the system into a low-gain conservative mode.
- Local Competition and Lateral Suppression Map — Models a field of competing local units in which each active unit suppresses its neighbors, sharpening the winner and the contrast across the field.
- Opponent Signal Subtraction Model — Models net output as the arithmetic difference between one activating and one inhibiting channel meeting at a single locus.
- Paired Enablement and Restraint Policy — Grants a power only when it is issued together with a proportional limit, a review, and a built-in expiry, at the same authority surface.
- Push–Pull Controller Pair — Runs paired opposing actuators as one controller, continuously driving both and rebalancing their gains to hold a shaped setpoint.
- Oscillation Damping: Reduce repeated overshooting and undershooting by tuning feedback, adding friction, widening hysteresis, or smoothing response rules.▸ Mechanisms (8)
- Control Loop Damping — Uses control-system concepts such as proportional response, integral restraint, derivative anticipation, or similar tuning to reduce repeated swings.
- Debounce Rule — Requires a trigger to remain true for a defined interval before the system acts, reducing rapid toggling and repeated false activation.
- Emotional Regulation Routine — Uses breathing, reflection, pause-before-response, or structured reappraisal to reduce rapid affective overcorrection in human behavior.
- Inventory Smoothing — Uses reorder bands, replenishment cadence, or batch sizing to reduce boom-bust cycles in stock, staffing, or capacity.
- Market Circuit Breaker — Pauses or slows trading, escalation, or high-velocity activity after extreme movement so participants can reassess instead of amplifying swings.
- Policy Gradualism — Changes policy in measured steps with observation intervals so corrections do not produce new swings faster than effects can be seen.
- Rate-of-Change Limit — Caps how fast a correction can move per interval — a slew-rate clamp — so the corrective action itself cannot inject overshoot, with an escape hatch for genuine emergencies.
- Staffing Smoothing — Stages hiring, redeployment, and shift changes behind a demand-confirmation band and a headcount-rate cap so an organization stops whipsawing between over- and under-staffing.
- Other-Agent State Model Calibration: Model another agent as having its own partial knowledge, goals, attention, constraints, and interpretations, then update that model from evidence before routing action through it.▸ Mechanisms (11)
- Active Listening Loop — Reflects the other agent's meaning back to them and invites correction, so the actor's model is checked and repaired live — in the exchange — rather than after the misunderstanding lands.
- Belief-Desire-Knowledge Map — Lays out what another agent probably believes, wants, knows, lacks, fears, and expects as an explicit set of hypotheses, each carrying a confidence level.
- Consent and Privacy Boundary Checklist — Gates whether it is legitimate to build, keep, share, and act on a model of another agent's private state — before the model is used, not after.
- Counterparty Model Red Team — Attacks a working model of a strategic counterparty by manufacturing rival explanations for their motives, constraints, and moves, to break the single story the actor has settled on.
- Empathy Map with Evidence Marks — Captures what another agent seems to see, hear, think, feel, say, and do — with every cell tagged as observed evidence or actor assumption.
- False-Belief Check — Tests the single assumption that the other agent knows what you know — catching curse-of-knowledge errors before they distort an explanation, interface, or instruction.
- Interaction After-Action Review — A recurring retrospective that asks where the model of the other agent helped, failed, surprised, or harmed — and rewrites the interaction rules accordingly.
- Perspective-Taking Interview — Replaces inference with direct, open-ended questioning to learn the other agent's actual understanding, constraints, and priorities.
- Prediction and Surprise Log — A running record of what the other agent was predicted to do, what they actually did, and how the model changed — making calibration visible across repeated interactions.
- Role-Reversal Simulation — Steps through the situation from the other agent's information, constraints, and incentives — arguing their case as they would — to expose where the actor's model is really just projection.
- Stakeholder Hidden-Constraint Board — A shared visual board that names each stakeholder and makes their invisible constraints, fears, incentives, and information gaps explicit for a team to design around.
- Overshoot-Crash Load Management: Keep self-amplifying growth inside sustaining capacity and, when decline is unavoidable, manage the unwind so the collapsing stock does not become a larger secondary load.▸ Mechanisms (14)
- Clearance Pathway Enhancement — Expands and speeds the legitimate channel that processes an unwinding stock — treatment, settlement, recycling, migration, disposal — so the crash load clears faster than it arrives.
- Cohort Staggering — Offsets when cohorts, maturities, or zones unwind — spreading correlated exits across time and space so peak crash load stays under capacity even when total load is unchanged.
- Controlled Drawdown Schedule — Sets the permitted rate, order, checkpoints, and stop-conditions for shrinking an over-large stock, so it unwinds fast enough to matter but slow enough not to trigger the very crash it is meant to prevent.
- Early Warning Indicator — Watches leading precursors — accelerating growth, rising variance, slowing recovery, thinning reserves — that flag an approaching crash while there is still time to act.
- Growth-and-Crash Stock-Flow Model — Ties growth, peak, crash-conversion, clearance, and recovery delay into one causal stock-and-flow model, so the size of the coming crash load can be read off the size of the stock.
- Hotspot Containment and Removal — Isolates a zone where collapse has already started and drains the concentrated failing stock through a capped destination before its by-products cascade into the wider system.
- Post-Crash Residual-Load Dashboard — Tracks the delayed secondary load after the visible peak has passed — showing whether the system is truly clearing or only looks quiet while the tail builds.
- Reentry Gate Review — A go/no-go review that lets growth or normal operation resume only on evidence that the secondary resource, the sinks, critical functions, and the original driver have all actually recovered.
- Saturation Dashboard — Displays the signals of a flattening response curve — marginal output, latency, errors, abandonment, fatigue — so approaching saturation is seen while there is still time to act.
- Secondary-Capacity Reserve Activation — Holds a protected reserve of the resource the crash will consume — oxygen, liquidity, staffing, treatment — and releases it when the crash-load forecast approaches the floor that must never be breached.
- Sink Capacity Audit — Verifies that every receiving system — treatment plant, court, landfill, labor market, balance sheet — can actually absorb the planned drawdown without hidden overload, unfair burden-dumping, or delayed failure.
- Source Reduction Program — Lowers how much hazard enters the pathway at its upstream sources, so every barrier, buffer, and filter downstream has less to hold back.
- Staged Harvesting or Decommissioning — Removes a dangerous stock in planned stages before it can crash on its own — capturing residual value and protecting critical functions instead of leaving a disorderly collapse.
- Threshold-Triggered Input Cap — Slows the enabling inflow automatically once the stock enters a precautionary band below the collapse threshold, buying time to act before overshoot forces a crash.
- Payoff Restructuring: Change the rewards, costs, penalties, or risks in a strategic interaction so rational choices move toward a better outcome.▸ Mechanisms (10)
- Access Priority Rule — Grants faster access, preferred queue position, capacity, visibility, or scarce resources to actors who meet desired behavior conditions.
- Clawback or Recovery Clause — Recovers a previously granted payoff when later evidence shows misconduct, underperformance, misrepresentation, or failure to satisfy conditions.
- Contract Incentive Clause — Builds bonuses, penalties, retainage, clawbacks, service credits, warranties, or shared-savings provisions into an agreement.
- Escrow or Holdback — Places the deal's value with a neutral custodian who releases it only on performance, so neither side can grab it early or withhold it at will.
- Liability Shift or Warranty — Moves downside risk toward the actor best positioned to prevent it, changing expected costs of low-quality or risky action.
- Penalty, Tax, or Fee — Adds a cost to behavior that imposes risk, waste, congestion, external harm, or strategic defection.
- Performance Bond or Deposit — Makes a promise of restraint credible by putting the promiser's own value at stake — forfeited on breach — so credibility no longer has to be bought by raising shared catastrophe risk.
- Reputation Score or Public Rating — Changes future opportunities, trust, or status by making behavior visible and comparable to others.
- Shared Savings or Gainsharing — Splits the benefits of improved performance so the party able to change behavior receives part of the system-level gain.
- Targeted Subsidy or Bonus — Adds a positive payoff for desired behavior, usually when the behavior creates system value but actors would otherwise underinvest in it.
- Perception-Comprehension-Projection Loop Design: Keep action aligned with a moving situation by continuously refreshing what is seen, what it means, what is likely next, and what decision it now supports.▸ Mechanisms (10)
- After-Action Awareness Recalibration — Replays a closed episode to compare what the team perceived, understood, and projected against what actually happened, then retunes the perception field and interpretation for the next loop.
- Anomaly Trigger Matrix — A lookup table mapping specific deviations-from-expected to the refresh, escalation, or watch action each must trigger, so a meaningful anomaly forces a new assessment instead of being noticed and shrugged off.
- Common Operating Picture Board — A single live display of the current priorities and open questions that every responder shares, so the team acts on one agreed picture instead of many private ones.
- Perception-Comprehension-Projection Brief — A verbal update format that forces every report to answer, in fixed order: what do we see, what does it mean, what is likely next, and what action follows.
- Projection Horizon Card — A compact artifact that fixes, for one situation, how far ahead the current assessment is trusted, the handful of plausible trajectories, and the moment the projection expires.
- Rolling Situation Update Cadence — A fixed refresh rhythm that expires the current situation picture on a schedule and forces a fresh perceive-comprehend-project pass before it goes stale.
- Scenario Injection Drill — A rehearsal that injects a scripted, evolving situation into the team's real loop to test whether they perceive the cue, project the trajectory, and act before the window closes.
- Situation Handoff Report — A structured shift-change transfer that carries not just status but the projection horizon, open uncertainties, and pending triggers, so awareness survives the change of custody.
- Uncertainty Marker Dashboard — A persistent shared display whose primary job is foregrounding what is missing, inferred, stale, or low-confidence, so a smooth picture cannot masquerade as certainty.
- Watchstander or Situation Cell — A dedicated person or small cell whose sole job is to own the awareness loop — continuously perceiving, comprehending, projecting, and keeping the shared picture current.
- Periodic Review and Reset: Use recurring review points to detect drift, clear accumulated errors, and reset the system before degradation compounds.▸ Mechanisms (9)
- Audit Cycle — Independent, scoped examination of a system against an external standard on a fixed cycle, producing evidence-backed findings and tracked remediation owners rather than fixing anything itself.
- Calibration Check — Compares an instrument's reading against a traceable reference standard at intervals set by its drift rate, and adjusts it back into alignment when the error exceeds tolerance.
- Data Quality Recertification — Requires the named owner of each data asset, definition, or access grant to re-affirm on a cycle that it still meets standard; anything left un-attested is revoked or quarantined by default.
- Financial Reconciliation — Matches two independent records of the same money against each other on a cycle, itemizes every discrepancy, and clears each one until the two balances agree and are documented.
- Health Checkup — Screens a whole living system's vital signs against age- and role-appropriate norms on a recurring schedule to catch developing problems early, referring anything abnormal to deeper diagnosis.
- Policy Review — Re-examines a standing rule against the reality it now governs and revises, renews, or retires it — resetting the reference itself rather than restoring the world to it.
- Preventive Maintenance Check — Services equipment on a usage- or time-based schedule set to intercept wear before failure — inspecting wear indicators and replacing or restoring worn parts on the spot.
- Quarterly Business Review — A recurring executive review of performance against targets across a portfolio, where an accountable owner explains variance, decisions reallocate resources, and off-track bets are escalated.
- Retrospective — A team periodically reflects on its own way of working, surfaces process drift from lived experience, and resets its working agreements — with learning, not blame, as the point.
- Perturbative Error Correction: Correct accumulated drift by applying small, bounded perturbations that steer a system back toward its operating band without shutting it down or rebuilding it.▸ Mechanisms (10)
- Bounded Rebalancing Trade — Restores a portfolio to its target weights with the smallest set of trades a turnover budget allows, correcting allocation drift without a full liquidation.
- Clinical Titration Adjustment — Adjusts a therapy by small, observed increments toward the patient's response, with a clinician gate holding veto over every step.
- Corrective Feedback Nudge — Steers a person or agent back toward a norm with a small, low-authority signal they are free to ignore, kept gentle by a deliberate influence budget.
- Delta Reconciliation Patch — Aligns two states that are supposed to match by computing their difference and applying only that delta, reversibly and with a full audit trail.
- Feature Flag or Canary Toggle — Exposes a change to a small, ring-fenced slice of traffic behind a switch, so it can be watched, widened, or killed instantly without a redeploy.
- Incremental Hotfix or Patch — Ships the smallest code or config change that repairs a live defect, scoped tightly and watched, with a threshold that says when to stop patching and redesign.
- Model Parameter Recalibration Nudge — Corrects a drifting deployed model with a small parameter adjustment, validated on held-out data before it goes live, instead of a full retrain.
- Proportional Trim Adjustment — Continuously trims an actuator in proportion to the live error between a setpoint and the measured state, so drift is corrected the instant it appears.
- Spacecraft Attitude Trim Pulse — Fires brief, discrete thruster pulses to null a spacecraft's attitude drift, spending an irreplaceable propellant budget and dropping to safe mode when drift outpaces it.
- Workflow Queue Rebalancing — Reassigns a modest number of in-flight work items across processing lanes to pull queues back toward balance, without disturbing the downstream stages they feed.
- Prediction-Error Learning Calibration: Teach from the signed gap between expected and received value so surprise updates the model while expected outcomes do not keep pretending to teach.▸ Mechanisms (12)
- Calibration Curve Review — Checks whether a score's predicted probabilities still match observed frequencies before anyone moves the threshold that sits on it.
- Credit Assignment Trace — Traces a delayed outcome back to the specific earlier cue or action that actually earned it, over the right time window, so the credit lands on the true cause and not on whatever happened to be nearby.
- Expectancy-Calibrated Feedback Form — A feedback template that records what a person expected before it records what happened, so praise and correction land on the surprise rather than the raw result.
- Learning Rate Schedule — Sets how big a step each prediction error is allowed to move the model — large when the world is genuinely changing, small when the variation is just noise.
- Negative Prediction Error Review — A recurring review of outcomes that came in worse than expected — separating genuine negative surprises worth learning from, from failures that were already priced in, without turning the lesson into punishment.
- Positive Surprise Capture — A standing practice for catching outcomes that beat expectations before they are normalized away, and turning each genuine upside surprise into a concrete change that makes it repeatable.
- Prediction–Outcome Delta Log — Records every prediction the moment it is made, pairs it with the actual outcome later, and stores the signed gap between them as the unit the rest of the system learns from.
- Reward Baseline Dashboard — Establishes and displays the expected-reward baseline so a result is read as above or below what was already anticipated — not as raw good or bad news.
- Reward Signal Red Team — A standing adversarial team that tries to break a reward signal before it trains anyone — hunting for ways to score high while defeating the intent, and for who gets hurt in the process.
- Shortcut Probe Holdout Set — A curated held-out test set where the suspected shortcut cue is deliberately broken, exposing whether the system learned the real signal or a convenient proxy that merely correlated with reward.
- Surprise Threshold Alert — Fires only when a prediction error is both large enough and clean enough to be real surprise, so ordinary noise never triggers attention or learning.
- Temporal-Difference Update Rule — Updates an estimate from the gap between successive predictions — bootstrapping off the next step rather than waiting for the final outcome — and propagates that error back across the delay.
- Predictive Residual Processing: Reduce bandwidth and focus adaptation by representing expected input through a maintained model and propagating only calibrated deviations, with synchronization, raw-state audits, and full-signal fallback.▸ Mechanisms (22)
- Anomaly Detection Model — Holds a model of what normal looks like and screens the live stream against it, raising a hand only when an observation departs far enough to be worth a second look.
- Bayesian Model Update — Turns each observed surprise into a revised belief — folding new evidence into a prior to yield a posterior over the model, along with honest uncertainty.
- Confidence Threshold Table — A maintained lookup table that turns model confidence and residual size into an action — pass, review, or escalate — indexed by stage and risk level.
- Delta or Differential Encoding — Sends only the difference from what the receiver could already predict — so the wire carries change, not the whole picture each time.
- Efference-Copy Cancellation — Feed a copy of your own outgoing command into a forward model, predict the sensations you're about to cause, and subtract them — so only the world's part of the signal survives.
- Event-Triggered Residual Reporting — Stay silent while the world matches prediction; speak only when a precision-weighted residual crosses a bar worth someone's attention.
- Forecast Backtesting — Replays a predictor against withheld history — across time, segments, and regimes — to earn or deny the right to suppress its residuals.
- Hierarchical Prediction-Error Loop — Stacks predictors in layers where each sends its neighbour a prediction and returns only the error it can't explain, so routine structure is cancelled at the lowest level that accounts for it and only genuine surprise climbs.
- Innovation Residual Filter — Updates a running state estimate using only the innovation — the gap between predicted and measured — weighted by how much to trust the model versus the measurement.
- Model Drift Monitoring — Watches a live predictor for the slow slide where yesterday's model quietly stops fitting today's world — before the residuals it suppresses start hiding real change.
- Model-Version Checksum Handshake — Confirms sender and receiver hold the same predictor version before any residual is trusted, so a delta computed against one model is never applied against another.
- Periodic Full-State Resynchronization — Periodically transmits or reconciles a complete state snapshot so predictor copies living on a diet of residuals are pulled back to ground truth before drift compounds.
- Precision-Weighted Error Gate — Scores each residual by magnitude, uncertainty, source reliability, consequence, and capacity cost, and admits only the ones worth the scarce bandwidth.
- Prediction Error Review — A standing review where people sit with the material misses — building the story of why each gap happened and deciding whether the model, the data, the action, or the boundary should change.
- Prediction-Error Replay Buffer — Stores selected surprises with their full context so they can be replayed later for delayed learning, root-cause analysis, calibration, and regression testing.
- Predictive Codec — Runs matched predictors at both ends of a channel and sends only quantized residuals plus sync metadata, so the decoder rebuilds the full signal as prediction-plus-correction.
- Raw-Signal Fallback Switch — Suspends residual-only processing and reverts to full observations the moment the model's validity conditions fail, trading bandwidth for completeness on demand.
- Residual Comparison Test — Interrogates the shape of the leftover residuals — against a null, a rival model, or a raw sample — to tell honest noise from a model that is quietly wrong.
- Residual Telemetry Dashboard — Surfaces the health of a residual pipeline — suppression rate, reconstruction error, drift, model version, fallback use, rare-event coverage — on one operator-facing display.
- Shadow Raw-Channel Sampling — Quietly routes a sample of full observations down an independent audit path and compares them against what the predictor would have reconstructed, to catch what the residual pipeline silently drops.
- Surprise-to-Action Bridge — The wiring that guarantees a validated surprise doesn't just light up a dashboard — it lands on a specific desk with a defined next move.
- Temporal-Difference Update — Treats the signed gap between expected and realized value as a teaching signal, nudging value or policy estimates one step at a time as outcomes unfold — without waiting for the final result.
- Predictive-Cue Wayfinding Design: Make local cues honestly predict what lies down each path so agents can choose, continue, or recover without needing a complete map.▸ Mechanisms (9)
- Breadcrumb and Landmark Trail — Keeps an agent oriented with a persistent layer of fixed landmarks and a visible trail of where they have been, so a wrong turn is recoverable without a separate rescue step.
- Cue-Destination Alignment Matrix — A living register with one row per cue, recording the destination value it promises, the evidence the promise holds, the owner accountable for it, and the trigger that forces a re-check.
- Destination Preview Card — A compact on-demand snapshot of what sits at the end of one specific path — summary, example, current status, and cost to get there — shown at the branch so the agent can judge that destination before committing.
- Link-Label Scent Audit — A recurring review pass that walks every label, heading, button, and link and checks it against what an agent actually finds after clicking, flagging weak, ambiguous, or mismatched cues.
- Misleading-Cue Red Team — An adversarial exercise that hunts for cues which attract traversal while concealing low relevance, hidden cost, or risk — approaching the interface as an attacker exploiting the gap between attention and truth.
- Progressive Disclosure Preview — Reveals just enough downstream structure at a branch point to sharpen an agent's prediction, holding the rest back so the choice gains scent without cognitive overload.
- Route Recovery Pattern — A defined procedure an agent follows after a wrong turn — backtrack, regain context, compare alternatives, and report the bad scent — turning a dead end into a recoverable step.
- Scent Clickthrough Trace Dashboard — A live instrument that aggregates traversal telemetry — clickthrough, backtracking, abandonment, refinement, successful arrival — and watches it over time for decaying or below-threshold scent.
- Task-Based Wayfinding Test — A facilitated study in which representative agents attempt realistic tasks and are observed choosing routes from local cues alone, measuring whether honest navigation actually succeeds for real intents.
- Price Signal Design: Use prices or price-like signals to communicate scarcity, value, or priority and coordinate decentralized decisions.▸ Mechanisms (10)
- Carbon Pricing
- Congestion Pricing
- Dynamic Pricing — Continuously re-computes the posted price from live demand, inventory, and willingness-to-pay signals, so the number a buyer sees always reflects current conditions instead of a fixed list.
- Internal Transfer Pricing — Charges one internal unit a real price for another unit's goods or services, so the buying unit sees—and its budget carries—the cost of what it draws from the rest of the organization.
- Price Cap or Floor — Bounds a price from above or below with a hard limit—capping spikes that would gouge or destabilize, flooring drops that would strand suppliers or hide scarcity—while watching for the shortages a binding bound can cause.
- Rebate or Credit Scheme — Returns money to targeted users after the fact—dividends, credits, or vouchers—so the marginal price keeps biting while the burden on those least able to pay is softened.
- Shadow Pricing — Imputes a price for a scarce resource or unpriced harm and applies it only inside decisions and plans—never billing anyone—so choices weigh a cost the market does not yet charge.
- Surge Pricing — Raises a bounded price multiplier the moment local demand outstrips available supply, rationing the immediate shortage and calling forth more supply until the imbalance passes.
- Time-of-Use Pricing — Publishes a fixed, predictable peak / off-peak price schedule in advance, so users can plan to shift flexible demand into the cheaper, less-scarce hours.
- Usage-Based Pricing — Ties at least part of what is paid to actual metered use, so an efficiency gain that lowers unit cost never makes marginal consumption feel free — defeating the flat-rate overuse that erases the saving.
- Progress-Guarded Livelock Disruption: Detect active non-progress cycles and break them by adding progress tests, desynchronization, asymmetry, cooldown, or external resolution.▸ Mechanisms (12)
- Bounded Priority Rotation — Breaks a mutual-yielding stalemate by imposing a strict precedence order — but rotates who holds priority on a bound, so the winner keeps changing and no actor is permanently deprived.
- Circuit Breaker and Cooldown — Counts repeated failed or non-progressing attempts, trips 'open' to stop the futile retries for a cooldown, then probes cautiously through a half-open state before resuming.
- Contention Trace Replay — Captures a real contention episode as an ordered event trace and replays it deterministically, so a livelock can be reproduced on demand, dissected, and reduced to a reusable signature.
- Exponential Backoff with Jitter — Turns a retry storm into a decorrelated trickle by making each rejected caller wait an exponentially growing, randomly perturbed delay before trying again.
- External Arbitration/Escalation — When the coupled actors cannot break their own loop, hands the unresolved conflict to an outside authority whose binding ruling forces the state transition neither side would make alone.
- Joint-State Cycle Trace — Records the combined state of the coupled actors over time and flags when that joint state keeps returning to the same region — the fingerprint of a livelock, not a stall.
- Leader Election or Token Passing — Designates exactly one actor — an elected leader or the holder of a single circulating token — as the one allowed to act, so mutually-cancelling moves are serialized into guaranteed progress.
- Liveness Watchdog — Arms a deadline against progress and, when the deadline passes with none, forces a reset to a known-good checkpoint before the stall becomes permanent.
- Progress Counter Heartbeat — Has each actor publish a monotonically increasing count of real, committed steps, so genuine progress — not mere busyness — becomes a signal anyone can watch.
- Quiescence Barrier — Brings every coupled actor to a synchronized halt, lets in-flight moves drain to a quiet state, then releases them from a clean point where no conflicting moves are pending.
- Randomized Retry Desynchronization — Injects randomness into each actor's retry timing so identical, lock-stepped actors scatter in phase and stop making the same move at the same instant.
- State-Machine Cycle Detection — Models the coupled actors as one state machine and finds the non-progress cycle in its reachability graph — the exact set of states they keep revisiting.
- Progressive Stressor Conditioning: Use bounded, progressively calibrated difficulty to trade temporary performance loss for durable capacity gain, with recovery and stop rules preventing overload.▸ Mechanisms (10)
- After-Action Gain Harvest — Turns a finished stress episode into retained capacity by debriefing it, recording what actually improved, and setting the dose that keeps the gain from fading.
- Consented Challenge Contract — Makes a hard challenge legitimate and bounded by negotiating, up front, what capacity it builds, what limits protect the person, and who fairly bears the burden.
- Deload or Recovery Cycle — Schedules planned reductions in load so the adaptation from prior stress can consolidate before the next build phase, and gates the re-ramp on that recovery.
- Desirable Difficulty Task Design — Builds the right kind of difficulty into a task itself so immediate performance drops but the durable learning the task is meant to produce rises.
- Fatigue and Maladaptation Dashboard — Watches strain, fatigue, and error signals against each person's own baseline to catch stress turning into damage before it shows up as injury or collapse.
- Graduated Exposure Ladder — Climbs a ranked ladder of feared situations one rung at a time, advancing only after each rung stops provoking distress, until the fear no longer controls behavior.
- Hormetic Microdose Protocol — Delivers repeated sub-damage doses of a stressor so the system overcompensates and builds tolerance it would never develop at rest.
- Pre/Post Capacity Assessment — Measures capacity before and after a conditioning block — including a delayed transfer test — so real durable gains are separated from momentary performance.
- Progressive Overload Protocol — Raises challenge in small, planned increments while protecting recovery, so capacity adapts upward without tipping into injury or collapse.
- Spaced Retrieval and Interleaving Plan — Distributes retrieval practice over expanding intervals and interleaves topics so recall stays effortful and therefore durable, then holds it with periodic review.
- Proxy–Target Divergence Detection and Recalibration: Keep proxies honest by continuously testing whether they still track their intended target, then downgrade, recalibrate, supplement, or retire them when the relationship decouples.▸ Mechanisms (10)
- Drift and Change-Point Detection — Watches the proxy's own signal stream for abrupt breaks and gradual drift, flagging when its statistical behavior changes even before anyone measures the target.
- Holdout Ground-Truth Audit — Withholds a random sample from proxy-driven action, measures the true target on it directly, and compares — a periodic reality check the proxy cannot influence.
- Incentive Impact Review — Maps the rewards, sanctions, and optimization pressure acting on a proxy to anticipate where actors will game the measure and hollow out its link to the target.
- Metric-Gaming Red Team
- Proxy Retirement Decision Record — Documents, with rationale and a named owner, the decision to downgrade, recalibrate, replace, or retire a proxy — and what claims must change as a result.
- Proxy–Target Correlation Refresh — Periodically re-estimates the statistical association between proxy and freshly measured target, updating the recorded link assumption instead of trusting the original validation forever.
- Reference-Standard Recalibration Review — Checks whether the reference standard used to judge the proxy has itself aged, and re-anchors or replaces it against a fresh, traceable yardstick.
- Sentinel Outcome Dashboard — A standing, owner-facing display that lines up the proxy against downstream outcome and harm signals so silent decoupling becomes visible at a glance.
- Shadow Target Measurement — Runs a slower, higher-fidelity measurement of the true target continuously in parallel with the proxy on live cases, without acting on it, to catch the two drifting apart.
- Triangulated Proxy Panel — Combines several independent proxies of the same target and treats their disagreement as the divergence signal, with no single ground truth required.
- Realized-Possible Outcome Gap Mapping: Compare what a process actually produced with what it could credibly have produced, then treat the gap as the main diagnostic object.▸ Mechanisms (9)
- Best-Demonstrated-Practice Comparator — Anchors the possible-outcome envelope on the best result actually demonstrated by a comparable unit somewhere, so the ceiling is an existence proof rather than a model.
- Closability Scoring Rubric — Scores each portion of a decomposed gap on how closable it is — recoverable latent capacity versus irreducible limit — using a shared, explicit rubric instead of intuition.
- Counterfactual Ceiling Probe — Estimates the theoretical ceiling by asking what the outcome would have been if identified losses were counterfactually removed, and carries the answer with an uncertainty band.
- Feasible-Frontier Mapping — Derives the possible-outcome envelope from an explicit constraint model — what the system could reach given its real limits — rather than from any single achieved result.
- Gap-Closure Experiment Backlog — Turns closable gap portions into a prioritized queue of experiments, each ranked by the expected gap it would close against its cost, so effort flows to the highest-return tests first.
- Loss-Channel Decomposition — Breaks a single measured realized-possible gap into named loss channels that sum back to the whole, so a lump deficit becomes an itemized account of where the outcome leaked.
- Post-Closure Gap Remeasurement — Re-runs the gap measurement after an intervention lands, updating both the realized outcome and its uncertainty band to confirm how much gap actually closed versus what was predicted.
- Realized-Possible Gap Table — Lays each realized outcome beside its credible possible value in one row-per-outcome ledger, turning the gap between them into an explicit, comparable quantity.
- Theoretical-Ceiling vs Feasible-Target Review — Adjudicates between the theoretical ceiling and a feasible target, deciding which portion of the gap to pursue and formally recording the ceiling-to-target band as intentionally left open.
- Rebound-Aware Efficiency Governance: Pair efficiency improvements with absolute resource targets, rebound modeling, demand guardrails, and adaptive monitoring so cheaper service does not erase or reverse the intended savings.▸ Mechanisms (20)
- Absolute Resource-Budget Protocol — Converts a per-unit efficiency gain into a binding ceiling on total resource use, with a stated rebound tolerance, so a smaller unit cannot quietly become a larger system.
- Cap-and-Trade — Holds total resource use under a hard aggregate cap while letting priced, tradable rights allocate the scarce total — so an efficiency gain frees allowances to trade rather than expanding the pie.
- Comparative LCA Model — Models the full physical resource burden — embodied, operating, replacement, end-of-life — of an efficient option against its counterfactual, per unit of service, so a smaller operating footprint isn't bought with a bigger hidden one.
- Control Group Comparison — Compares treated units against otherwise-similar untreated ones to recover what total use would have been without the efficiency program — separating the real saving from the rebound and from what would have happened anyway.
- Cost–Benefit Assessment Protocol — Weighs a proposed distortion repair on full welfare terms — surplus recovered, who gains and loses, and how robust the case is — instead of accepting 'it costs less' as proof it is better.
- Demand Response Pricing — Varies price continuously by time, load, or scarcity so responsive demand moves off the peaks efficiency would let it pile onto — reshaping when the resource is used rather than what it costs on average.
- Direct and Indirect Rebound Audit — Traces where an efficiency gain's freed capacity and freed money actually went — same-service demand, cross-category spending, and induced supply — to see how much of the intended saving rebounded.
- Efficiency-Dividend Lockbox — A standing fund that ring-fences a defined share of efficiency savings for resource retirement or public benefit, so the dividend cannot be silently reinvested into more throughput.
- Elasticity Experiment — Deliberately tests several lever magnitudes, messages, or friction levels on small slices before scaling, to measure how strongly demand rebounds — the elasticity every price and guardrail is tuned against.
- Embodied-Resource Payback Test — Checks whether the resource embodied in replacing or upgrading equipment is actually repaid by the in-use savings within the equipment's life — after real-world rebound is counted.
- Essential-Access Rebound Review — Sorts post-efficiency demand growth into need-closing use that must be protected and low-value use that controls may target, so rebound controls don't cut off the under-served.
- Full-Cost Accounting — Pulls the upstream, downstream, social, and environmental costs an efficiency decision leaves off-ledger back onto it — so the choice is judged on its full resource burden, not just the metered operating bill.
- Price Incentive Adjustment — Applies a standing, deliberate change to price — a fee, tax, rebate, or subsidy set where demand will respond — to re-raise the effective cost an efficiency gain quietly lowered.
- Quota System — Rations the scarce total into bounded, per-holder use limits — the choice when an absolute target must hold even under strong or uncertain rebound and no price or market can be trusted to protect it.
- Rebound Scenario Stress Test — Runs the efficiency intervention through a spread of rebound scenarios — from negligible to full backfire — before scaling, to see whether the intended saving survives the bad cases.
- Rebound-Leakage Boundary Review — Re-runs the efficiency outcome at successively wider category, supply-chain, geographic, and time boundaries to expose rebound that was merely exported or delayed past the original accounting line.
- Rebound-Triggered Policy Recalibration — A standing monitor-and-escalate loop that fires predefined corrective actions, in order, once observed rebound or total use pushes past the allowed band.
- Resource Monitoring Dashboard — Puts unit efficiency, service demand, total resource use, rebound fraction, and budget status on one live view — so the gap between per-unit gains and the stubborn total is impossible to miss.
- Service-Output Normalization Dashboard — Puts resource use, service quantity, service quality, utilization, and access on one normalized basis so an efficiency gain can be told apart from simply delivering more service.
- Usage-Based Pricing — Ties at least part of what is paid to actual metered use, so an efficiency gain that lowers unit cost never makes marginal consumption feel free — defeating the flat-rate overuse that erases the saving.
- Reference Tracking Bandwidth Alignment: Make the demanded trajectory trackable by matching reference update speed to the loop bandwidth that can actually observe, decide, act, and settle.▸ Mechanisms (10)
- Actuator Saturation Alarm — Fires when tracking error stops responding to effort because the actuator or capacity has hit its ceiling — reattributing the lag from willingness to bandwidth.
- Feedforward Prepositioning Plan — Stages capacity, stock, or configuration ahead of forecast reference movement so the loop begins each change already closer to the new target.
- Hysteresis or Deadband Window — Holds the loop still inside a band of insignificance so it stops chasing noise and rapid reversals it could never usefully track.
- Lead-Time Change Notice — Commits the reference-setter to announce a change a fixed lead time before it binds, converting a surprise into preparation.
- Model-Predictive Tracking Window — Optimizes each correction over a short rolling forecast of where the reference is heading, so the loop acts on the coming target, not just the present error.
- Priority-Band Triage Rule — Allocates scarce tracking bandwidth by priority band, keeping critical references inside the envelope while lower bands queue, degrade, or wait.
- Reference Slew-Rate Limit — Caps the rate at which the setpoint may move so the loop always has time to settle between updates.
- Staged Setpoint Ramp — Breaks one large reference jump into a sequence of intermediate targets, each reached and validated before the next is issued.
- Trackable Envelope Chart — Puts reference speed, loop response time, saturation margin, and error persistence in one view so mismatch is visible at a glance.
- Untrackable Demand Exception Record — Logs each time demanded reference motion breached the trackable envelope — when, why, and which fallback fired — so unmet demand is accounted, not hidden.
- Refinement Timing Guardrail: Delay costly local refinement until the global structure, real bottlenecks, and reversibility conditions are known enough to spend optimization effort well.▸ Mechanisms (9)
- Architecture Skeleton or Walking Skeleton — Stands up a thin end-to-end version of the whole system first — every layer wired, nothing polished — so its real integration structure is visible before any local part is refined.
- Decision Record with Deferred Refinement — Writes down, for a single decision, which refinement is being deliberately postponed, what lock-in that avoids, and under what exception it could still proceed early.
- Local–Global Metric Trace — Instruments a local metric and the whole-system outcome it is supposed to serve on the same chart, so a polished local number can't be mistaken for real value.
- Optimization Backlog with Trigger Conditions — Keeps deferred optimizations in a visible list, each tagged with the measurable condition that should fire it — so good ideas are neither forgotten nor done too early.
- Pre-Optimization Review Ritual — A recurring, short team meeting where any proposed optimization must be argued aloud before work starts — turning 'should we polish this now?' into a collective, evidence-checked decision.
- Refinement Readiness Checklist — A fixed list of pass/fail criteria every proposed refinement must satisfy before it is allowed to proceed — the gate rendered as an explicit, repeatable checklist.
- Representative Workload Profiling — Runs the system under a load that mirrors real usage and measures where time and resources actually go — so refinement aims at the true bottleneck, not the suspected one.
- Reversibility Tag or Feature Flag — Wraps an early refinement behind a switch that can turn it off or back it out cleanly, so the change stays removable while the surrounding system is still uncertain.
- Timeboxed Optimization Spike — Spends a fixed, small budget of time on an optimization purely to learn whether it would pay — with a hard stop and no commitment to keep the code.
- Reflexive Forecast Impact Governance: Treat a forecast that people can react to as an intervention, then govern its disclosure, response channels, and success criteria so belief in the forecast does not accidentally invalidate or misread it.▸ Mechanisms (12)
- Avoided-Loss Counterfactual Review — Judges a forecast that appears to have 'failed' by estimating the loss it prevented, so a warning that averts its own prediction is credited as a success rather than a false alarm.
- Capacity Window Assignment — Pre-assigns actors to specific time or capacity windows instead of letting them all self-select from the forecast, so a published projection of scarcity or slack doesn't trigger a synchronized stampede that invalidates it.
- Forecast Impact Audit — Examines, after release, how a forecast actually moved behavior — comparing the reaction that occurred against the reaction that was modeled, and testing whether anyone gamed it — to tell a self-defeating forecast apart from a merely wrong one.
- Forecast Release Decision Log — A dated, append-only record of each forecast released — the exact claim, who could see it, and the disclosure boundary applied — so the decision to publish a reactive forecast can be reviewed against what was known at the time, not what happened after.
- Forecast Update Cadence — Sets the rhythm and trigger for re-issuing a forecast as people react to the last one, so the forecast tracks the world it is actively reshaping instead of chasing — or amplifying — its own feedback.
- Forecast-as-Intervention Label — A standing tag attached to a forecast that declares it can change the outcome it predicts, telling readers to treat it as guidance to act on — and stating why it is being disclosed at all.
- Post-Release Behavior Dashboard — Watches, in near-real time, how audiences actually respond once a forecast is published, so the reaction becomes an observed signal rather than an assumption.
- Public False-Alarm Explainer — A prepared public explanation for when a warning looks like a false alarm precisely because acting on it averted the harm it predicted — issued to protect the credibility of the next warning.
- Reaction Channel Premortem — Before release, imagines the forecast is already public and works backward through every channel by which audiences could react, to surface the reactions that would distort or defeat it.
- Response Smoothing Instruction — Ships the forecast with guidance on how to respond so the collective reaction spreads out instead of spiking all at once and defeating the forecast.
- Staged Disclosure Protocol — Releases a reflexive forecast in controlled phases — to whom, in what order, at what detail — so those who must prepare can act before the reaction that broad release would trigger.
- Strategic Gaming Stress Test — Red-teams a forecast before release by asking how self-interested actors could game it once published, then specifies the commitment or incentive anchors that remove the payoff for gaming.
- Reflexive Self-Monitoring: Enable a system or actor to observe its own behavior and use that observation to adjust future behavior.▸ Mechanisms (9)
- Habit Tracker — Records recurring personal behavior so patterns, streaks, lapses, triggers, and adjustment opportunities become visible.
- Metacognitive Prompt — Asks the actor to notice its own thinking, uncertainty, attention, assumptions, or strategy while acting or learning.
- Organizational Review — Periodically examines an organization's own routines, metrics, norms, commitments, and outcomes to revise how it operates.
- Peer Feedback Session — Adds other observers to help the actor see behavior that self-observation alone may miss.
- Personal Dashboard — Aggregates selected self-observation signals for an individual, operator, learner, or role holder.
- Postmortem Review — Uses a failure, incident, near miss, or major outcome as evidence for revising future behavior and safeguards.
- Reflective Journal — Preserves episodes, interpretations, emotions, strategies, and follow-up commitments for later pattern recognition.
- Self-Assessment Tool — Helps an actor compare its own performance, process, or state against criteria before external judgment or final outcome.
- Team Retrospective — Creates a recurring space for a team to inspect its own work process, coordination patterns, and improvement commitments.
- Reinforcement Loop Design: Shape cues, responses, and consequences so desired behaviors become easier to learn and maintain.▸ Mechanisms (10)
- Behavior Data Dashboard — Displays behavior frequency, quality, latency, decay, and outcome correlation so the loop can be tuned.
- Behavioral Prompting — Places prompts, reminders, cue cards, notifications, defaults, or environmental signals at the moment a target response should occur.
- Consequence Design Review — Reviews proposed rewards, penalties, feedback, recognition, and natural consequences for alignment, proportionality, timing, fairness, and side effects.
- Habit Loop Mapping — Charts the existing cue → routine → reward loop so the association driving a behavior is visible before anything is changed.
- Immediate Feedback Interface — Gives rapid information about whether the target response occurred, how well it was performed, or what adjustment is needed.
- Perverse Incentive Red Team — Stress-tests the loop by asking how a rational, overloaded, fearful, or opportunistic actor might satisfy the reinforcement while violating the intent.
- Reinforcement Schedule Design — Chooses continuous, fixed, variable, intermittent, tapering, or event-triggered reinforcement patterns for a particular behavior and context.
- Reward or Recognition System — Provides meaningful acknowledgment, points, access, status, compensation, privileges, or praise linked to the target response or outcome.
- Safety Reinforcement Protocol — Makes safe actions, near-miss reporting, stop-work decisions, or checklist adherence visible and positively reinforced.
- Training Feedback Cycle — Repeatedly exposes learners to practice, performance feedback, correction, and another attempt until the desired skill or response becomes stable.
- Relation Rewiring: Change the relationships among entities to alter information flow, incentives, dependencies, responsibility, or influence patterns.▸ Mechanisms (8)
- Communication Channel Redesign — Changes who can communicate with whom, through which channel, at what cadence, and with what escalation or visibility rules.
- Dependency Injection or Adapter Substitution — Implements relation rewiring in software or systems by changing how a component obtains collaborators, dependencies, or interface pathways.
- Network Intervention Pilot — Tests a limited relation change before full rollout, using local monitoring to detect unwanted bottlenecks, exclusions, or dependency transfers.
- Organizational Redesign — Implements relation rewiring by changing reporting lines, decision rights, team interfaces, ownership boundaries, or coordination forums.
- Partnership Restructuring — Changes relationships among organizations, vendors, institutions, or jurisdictions so obligations, dependency, risk, or influence are redistributed.
- Routing Table or Rule Update — Changes configured relations among requests, users, cases, queues, services, or decision paths without necessarily changing the underlying entities.
- Stakeholder Realignment Workshop — Uses a structured meeting or workshop to identify problematic relationships, negotiate new interaction patterns, and assign transition responsibilities.
- Workflow Rerouting — Implements the archetype by changing the path that work, cases, requests, approvals, or information follow among actors or systems.
- Reputational Signal Governance: Turn past behavior into a governed standing signal that helps others decide trust, access, scrutiny, cooperation, or priority while preserving evidence quality, context, correction, decay, and anti-abuse safeguards.▸ Mechanisms (13)
- Appeal and Correction Workflow — Gives a subject a governed path to contest and fix reputational information that is false, irrelevant, malicious, or stale.
- Attested Credential Registry — Anchors reputation to independently verified credentials and attestations, so trust does not have to rest on informal history alone.
- Complaint and Resolution Record — Records not just the complaint but the response, repair, and closure, so a grievance is read together with how it was handled.
- Contribution Ledger — Keeps an append-only, per-subject record of contributions, no-shows, and repairs across repeated rounds, so standing rests on a whole conduct history rather than the last impression.
- Decay-Weighted Score Update — Discounts old evidence on a schedule so standing tracks who a subject is now, not who they were years ago.
- Moderation Record with Reentry — Logs rule violations and their repair while defining the conditions under which standing is restored.
- Peer Reference or Vouching — Lets credible counterparties endorse, warn about, or contextualize a subject from direct first-hand experience.
- Rating and Review System — Collects ratings and reviews from counterparties after each interaction and publishes them as an at-a-glance standing signal.
- Reputation Portability Protocol — Lets a subject carry reputation evidence or attestations from one context to another under consent, with scope and validity limits attached.
- Reputation Score or Standing Index — Aggregates a subject's weighted traces into one score, band, or standing index used to sort trust, access, ranking, or scrutiny.
- Sybil, Collusion, and Brigading Detection — Detects fake accounts, coordinated rings, paid reviews, and retaliatory brigading that manufacture or attack reputation.
- Trust-Tier Badging — Bins subjects into a few coarse trust tiers shown as a badge, and attaches concrete treatment to each tier.
- Verified Transaction History — Presents a subject's completed transactions, fulfilled commitments, and defect or dispute outcomes as verified facts of record — evidence, not opinion.
- Revealed-Use Path Alignment: When people repeatedly cut their own path through a designed system, treat the trace as evidence and redesign the official path only after interpreting the cause, safety, legitimacy, and equity of the deviation.▸ Mechanisms (12)
- Before/After Trace Monitoring — Measure the intensity of the old workaround trace before and after a path change to test whether the redesign absorbed the deviation — or merely moved it.
- Clickstream Deviation Scan — Mine product telemetry at population scale for the loops, exits, repeated searches, and shortcut clicks that mark where users deviate from the intended flow.
- Desire Path Walkthrough — Traverse the designed route and the worn-in one side by side, on site, to make the official path explicit and mark exactly where lived use departs from it.
- Friction Mapping Session — Lay the official path and the workaround side by side and score each step for effort, delay, uncertainty, and social and cognitive cost, so the cost gap that drives the deviation becomes visible and rankable.
- Frontline Go-Along Interview — Walk the real route beside the person who uses it and have them narrate each deviation as they make it, recovering the reason, the who, and the who's-missing that logs cannot show.
- Informal Route Legalization Patch — Make a safe, already-vetted workaround official by rewriting the rule, SOP, permission, or documentation to match it — and naming who now owns the sanctioned path.
- Route Closure with Alternative — Blocks a revealed path that has been judged genuinely harmful while standing up a legitimate route that serves the same underlying need — so the need isn't punished along with the path.
- Safety and Accessibility Review — Tests a candidate accommodation against the non-negotiables — safety, accessibility, dignity, privacy, environment — before anyone decides to pave, reroute, or block the revealed path.
- Temporary Paving Pilot — Stands up a cheap, reversible version of the revealed path — temporary signage, paint, or a workflow patch — to test whether formalizing it actually improves outcomes before committing to a permanent build.
- Trace Decay Review — After a redesign, checks two things at once — that the old desire path is actually fading, and that no worse path has popped up somewhere else.
- Use-Trace Heatmap — Aggregates many individual traces into a single visual field so the places where actual behavior concentrates — and diverges from the intended path — jump out at a glance.
- Workaround Inventory — A structured catalog of the informal routes, side systems, and unofficial handoffs a system has accumulated — each entry logged with its context and a first-pass reading of why it exists.
- Scope Creep Containment: Control incremental expansion of a work boundary by judging every addition against the original charter, capacity, tradeoffs, and explicit subtract-or-recharter rules.▸ Mechanisms (10)
- Change Control Board — A standing cross-functional body that adjudicates every proposed scope change against the charter, owns the cumulative trajectory, and publishes each disposition so no addition slips in unowned.
- Deferred Scope Parking Lot — A visible holding register where good-but-not-now requests are parked with owner and revisit date, so deferral is an honored decision rather than a lost promise or a silent yes.
- Impact Assessment Checkpoint — A required analysis step that, before any change is decided, traces its full downstream cost — capacity, dependencies, hidden follow-on work — and measures how far it moves scope from the original charter.
- Plus/Minus Scope Review — A recurring review that refuses to let any addition in without naming, in the same session, the cut, deferral, or buffer draw that pays for it — making scope changes symmetric instead of additive-only.
- Rebaseline Workshop — A facilitated session that, when accumulated drift has made the old plan a fiction, deliberately establishes a new authorized baseline and archives the prior trajectory — so scope moves by explicit reset, not silent erosion.
- Requirements Traceability Matrix — Threads every requirement through to the design, code, and verification that satisfy it, so any requirement with no downstream link — or no passing test — is a visible coverage hole.
- Scope Change Request Template — A standard intake form that makes a scope change unmentionable until its requester has stated fit, value, cost, owner, and what it displaces — turning casual asks into structured, logged records with the admission questions built in.
- Scope Drift Dashboard — A continuously-updated view that plots how far the current perimeter has moved from the original charter and how much reserve remains, so cumulative drift is a visible trend rather than a late surprise.
- Scope Freeze Protocol — A declared, time-boxed window during which no scope additions are accepted at all, with any emergency exception carrying a built-in expiry so the freeze thaws cleanly instead of leaking into permanent new scope.
- Scope-Cut Review
- Second-System Complexity Restraint: Keep the successor system launchable by remembering which first-system constraints made focus possible, triaging deferred ambitions, preserving the proven core, and admitting new complexity only through staged value-and-cost gates.▸ Mechanisms (10)
- Architecture Decision Record with Future-Option Cost — Records each architectural choice together with the priced cost of the future option it keeps open — so 'build it flexible now' has to pay a visible tax.
- Complexity Budget Review — A recurring review that totals the successor's cumulative complexity against a fixed cap and flags when the sum — not any single item — starts to threaten launchability.
- Constraint-Release Inventory — Catalogs each of the first system's constraints alongside the pain it caused, the useful function it secretly performed, and the replacement discipline needed before it can be safely released.
- Feature Admission Rubric — Scores each proposed addition on value, evidence, complexity, support, migration, and tier-fit, so admission to the successor is a decision the item earns rather than a default it inherits.
- Parity-Then-Expansion Gate — A hard precondition that forbids any net-new expansion from entering the successor until it has demonstrably matched the predecessor's validated core.
- Postlaunch Ambition-Thaw Review — After the successor stabilizes, deliberately reopens the parked-ambition and deferred-debt lists to decide which frozen items are now ready to thaw into the next cycle.
- Rewrite Scope Firewall — A structural barrier that forces parity work, debt repair, architecture change, and new features into separate approval channels so none can smuggle the others in.
- Second-System Premortem — A structured foresight exercise that imagines the successor has already failed by overreach — too general, too late, too fragile — and works backward to the decisions that caused it.
- Staged Release Ladder — Structures the successor into ordered tiers — launch, stabilize, expand, later — and routes each deferred ambition into a named rung with an owner and a review trigger.
- Successor Charter — The founding document that fixes what the successor must preserve, what it may improve this cycle, its protected invariants and escape path, and who holds the authority to change any of it.
- Selective Pathway Suppression: Slow, pause, or stop a specific active transformation by applying a selective counter-agent at its enabling mechanism while preserving protected functions and a monitored release path.▸ Mechanisms (15)
- Circuit Breaker Pause — Trips an automatic, temporary halt on one runaway activity the instant a cascade metric crosses a preset threshold, then releases on its own once conditions cool.
- Competitive Occupancy Inhibition — Occupies the target pathway's own control point with a rival that engages the site but does nothing, so the real activator can no longer bind it at the former rate — a surmountable brake set by dose.
- Counter-Signal Injection — Cancels a pathway's drive by injecting an equal-and-opposite signal alongside it, leaving the original source in place and other signals untouched.
- Decoy Binding or Sink — Plants a sacrificial look-alike that soaks up a pathway's activator before it can reach the real mechanism, starving that one pathway while others keep their supply.
- Feature-Flag Disablement — Disables one specific software behavior or integration behind a runtime switch — without shutting down the rest of the service — and records who flipped what, so it can be reversed in seconds.
- Feedback-Gain Reduction — Turns down the loop gain of a self-reinforcing pathway so it stops amplifying itself, without cutting the loop or blocking its inputs.
- Goal-Shielding Protocol — Suppresses competing goals, cues, and requests for the duration of a focal task, then lifts the suppression the moment the task completes or times out.
- Inhibitor Titration and Taper — Ramps inhibition up in small steps until the target sits in its objective band, then steps it back down gradually so the pathway doesn't rebound on release.
- Lateral Suppression Network — Lets each active unit inhibit its neighbours in proportion to its own strength, so a clear winner and sharp contrast emerge from competition rather than from an external brake.
- Noncompetitive or Allosteric Inhibition — Caps a mechanism's output by binding a separate control site and changing its state, so piling on more input can't overcome the block.
- Parallel Feedforward Brake — Fires a calibrated inhibitory path from the same signal that triggers the response, bounding the response in advance instead of correcting it after it overshoots.
- Permission or Access Revocation — Withdraws the specific authorization an actor needs for the target action while leaving its other capabilities intact — the block sits at the grant, not the mechanism.
- Rate Limit or Throttle — Caps how fast a given actor can hit the network so abuse, overload, or attack degrades gracefully instead of taking the shared system down — a blunt, reversible safety valve.
- Time-Bounded Veto or Hold — Lets an independent authority pause a transition for a fixed window that lapses by default, so continuing the hold — not lifting it — is what must be justified.
- Washout and Rechallenge — Removes the inhibitor to see whether the target recovers, then cautiously reapplies it, so the off-then-on toggle proves the inhibitor was doing the work.
- Self-Endorsed Norm Uptake: Help people adopt an external norm as a self-endorsed internal standard by making the norm legitimate, meaningful, practiced, feedback-rich, and contestable rather than merely enforced.▸ Mechanisms (12)
- Autonomy-Supportive Framing — Presents a norm as something a reasoning person can endorse — with the choice, the rationale, and a real way to object left intact — rather than as obedience demanded by authority.
- Commitment Rehearsal — Turns a general endorsement into a concrete, pre-rehearsed if-then response and a stated commitment, so the norm is retrievable in the exact pressured moment it is needed.
- Dissonance-Safe Reappraisal — Gives people a way to face the clash between a long-held habit and a newly adopted standard without sliding into shame, denial, or defensive rationalization.
- Guided Practice with Feedback — Has people apply the norm in realistic but low-stakes scenarios, get specific feedback, repair the error, and repeat — so the norm becomes a practiced skill rather than a memorized rule.
- Narrative Identification Prompt — Uses stories of role, craft, mission, or consequence — and the symbols that carry them — to help a person recognize the norm as part of the kind of person they are trying to become.
- Norm Legitimacy Review — Periodically re-examines the norm itself — is it still justified, explainable, contestable, and free of coercion — so people are asked to internalize only standards that deserve it.
- Onboarding Norm Translation — Inducts newcomers into a norm by conveying its purpose, worked examples, and the judgment it calls for — not just the rule text — so it arrives as something to understand rather than merely obey.
- Peer Sensemaking Circle — A recurring peer forum where equals talk through real, ambiguous cases together — normalizing the standard while surfacing exactly where it is genuinely contested.
- Reflective Values Dialogue — A guided dialogue that connects the norm to the person's own purposes and values — moving it from 'they require this' to 'this is a standard I have reason to hold.'
- Repair or Reentry Reflection — After a breach or drift, a structured reflection that turns the violation into understood harm and renewed commitment — restoring standing without permanent shame.
- Role Modeling with Debrief — The actor watches a credible exemplar enact the norm under real pressure, then debriefs the judgment behind the action — so tacit judgment, not just the rule, is transmitted.
- Self-Explanation of Norm — The actor must reconstruct the norm in their own words — with their own examples and limits — so understanding is generated internally rather than recited.
- Self-Fulfilling Prophecy Interruption: Break feedback loops where expectations cause behaviors that make the expected outcome come true.▸ Mechanisms (13)
- Balanced Opportunity Assignment — Distributes challenge, mentoring, and visibility by rule rather than by gut expectation, so people predicted to fail are not quietly denied the chances that would let them succeed.
- Blind Review — Withholds identity, reputation, and prior scores at the point of evaluation so a judgment forms before the expectation can steer it.
- Counter-Stereotype Evidence — Feeds credible, case-specific disconfirming evidence into a judgment so a stereotype cannot monopolize the reading of ambiguous behavior.
- Expectation Audit — Traces where an expectation, label, or score enters a process and maps the behavior channels through which it may be quietly manufacturing its own confirmation.
- Expectation Calibration Review — Compares what was predicted against what actually happened while controlling for the treatment the prediction itself caused, separating warranted forecasts from prophecies.
- Feedback-Loop Redesign — Rebuilds the timing, content, audience, and consequences of feedback so it fuels improvement instead of ratifying a predicted deficit.
- Growth-Mindset Framing — Frames expectations around improvable capability, strategy, and next steps rather than fixed traits, redirecting a negative prophecy toward effort and support.
- Interaction Script Revision — Rewrites the recurring lines, prompts, and moves of everyday interactions so low expectations stop riding into behavior through ordinary conversational habit.
- Label-Neutral Reporting — Constrains what a record or handoff may say, replacing fixed-trait labels with observed behavior and evidence so downstream readers are not pre-steered.
- Neutral Treatment Protocol — Standardizes the baseline treatment everyone receives — opportunity, information, respect, review, follow-up — so a label cannot buy better or worse handling through discretion.
- Outcome Monitoring Review — Tracks over time whether an interruption actually changed outcomes and treatment — and whether the loop simply moved to a subtler channel — so optimism does not replace one untested story with another.
- Prediction Impact Audit — Checks whether a risk score, forecast, or warning label is changing how a system treats its subjects in ways that help bring about the very outcome it predicts.
- Teacher / Manager Expectation Check — Prompts an authority figure to compare their own expectations against how they actually distribute attention, challenge, and feedback — and to change the interaction where the two diverge.
- Sense-Act Loop Coupling: Design sensing and action as one loop: each movement changes what can be known, and each new observation reshapes the next move.▸ Mechanisms (7)
- Action-Observation Log — Records each action, the observation it produced, its interpretation, and the next action, preserving the action–perception coupling as a durable, shared, reconstructable trace.
- Active Probe Protocol — Pre-commits a single bounded probe to one specific uncertainty — naming what it should reveal, how far it may go, and which next action each possible result triggers — so exploration stays informative, reversible, and safe.
- Interactive Task Walkthrough — Puts a real, often first-time user in front of a live surface with a genuine task and watches what they actually perceive and do, making the gap between intended and enacted use observable.
- Look-Move-Look Cycle — Interleaves small physical advances with fresh reads of the scene at a cadence never faster than you can re-perceive, so each move is chosen from what the last one exposed.
- Micro-Experiment Sequence — Chains many small, cheap tests into a branching series, carrying each result forward so every next experiment is chosen from what the previous ones revealed.
- Mobile or Embodied Sensor Array — Mounts sensing on a movable, aimable body or mount that can be repositioned, advanced, or reconfigured to bring occluded state into view — making observability a controllable output of motion.
- Perceptual Calibration Drill — Retrains an actor's own perception through repeated, feedback-corrected reps that direct attention to a specific diagnostic cue, so the signal that matters is noticed and read correctly at the moment of performance.
- Source–Sink Viability Management: Manage asymmetric support networks by protecting sources, diagnosing sink dependency, and deciding when to sustain, restore, transform, or exit sinks.▸ Mechanisms (13)
- Connectivity or Corridor Plan — Designs and protects the actual pathways along which a source's surplus can reach a sink, and deliberately keeps more than one route open, so rescue can happen without leaving the sink hostage to a single link.
- Cross-Subsidy Budget — Makes the transfer from source to sink an explicit line item — how much surplus each source can spare after protecting itself, where it goes, and whether the resulting subsidy is fair — so support is a decision, not a leak.
- Dispersal or Transfer Tracer — Tags and follows the individuals or units that actually move between patches, turning assumed support flows into a measured map of who really feeds whom and what each patch's true net balance is.
- Metapopulation Model — Runs a network of coupled patches forward from their per-patch birth–death and dispersal rates to forecast whether the whole persists — and which patches are true sources versus occupied-but-doomed sinks.
- Minimum Support Schedule — Sets the smallest reliable support a sink needs to stay just above its viability threshold, delivered on a fixed cadence and adjusted by rule as conditions change — sparing the source without letting the sink slip under.
- Rescue-Effect Audit — Periodically tests whether a sink's apparent health is genuine local recovery or merely a rescue effect — persistence borrowed from a source — by asking what it would do if the support were removed.
- Restoration Priority Matrix — Ranks dependent sinks by how recoverable they are against how much they are worth keeping, sorting each into restore, convert, sustain, or exit — so scarce surplus goes where it can actually change a unit's fate.
- Role Reclassification Review — A standing review that watches for role-change triggers and, on a set cadence, formally re-labels any unit whose source or sink status has shifted — so the classification the whole system trusts never silently goes stale.
- Sink Dependency Dashboard — Tracks each sink's dependency in real time — how much support it draws, how close it sits to its viability threshold, and which flows it relies on — so hidden fragility and lock-in surface before an interruption exposes them.
- Source Depletion Dashboard — Continuously watches each source's health — how much exportable surplus is left, whether its viability guardrails are being breached, and how it holds up under stress — so stewardship never quietly slides into extraction.
- Source–Sink Patch Map — Lays out every unit as a labelled patch — source, sink, neutral, or contested — coloured by measured net balance, so the asymmetric structure of who is quietly carrying whom becomes visible at a glance.
- Support Flow Agreement — Turns an informal support flow into an explicit compact — stating why the support exists, until when it is promised, and on what fair terms — so a subsidy is a governed decision rather than an accreted habit.
- Support Taper Plan — A staged glide-path for reducing or ending support, paced to the sink's response and bounded by a do-no-harm guardrail, so withdrawal is a controlled landing rather than a cliff.
- Stock–Flow Accumulation Control: Manage buildup or depletion by treating the stock as the integral of net flow, not as another flow rate.▸ Mechanisms (7)
- Accumulation Threshold Alert — Watches an accumulating stock against preset bands and fires a warning the moment the level crosses a floor or ceiling.
- Clearance–Turnover Tuning — Tunes how fast a stock is drained and cycled — its clearance and turnover rates — to hold residence time and throughput where they belong.
- Delay-Compensated Control — Controls a stock whose response lags the lever, acting on where the level is headed rather than where it is now.
- Hidden Accumulation Probe — Hunts for stock that has quietly displaced across a boundary or piled up off the books, explaining a level that the visible flows cannot.
- Net-Flow Lever Adjustment — Steers a stock into its target band by choosing which inflow or outflow lever to move, and by how much, given the current net flow.
- Stock-Level Buffering — Holds a deliberate reserve so a stock can absorb swings in inflow or outflow without breaching its limits.
- Stock–Flow Balance Reconciliation — Closes the books on a stock by reconciling its measured level change against the net of every inflow and outflow, and flags the unexplained residual.
- Sustainable Load Envelope Governance: Keep recurring demand inside a sustainable load envelope so current operation does not cannibalize the capacity needed for future operation.▸ Mechanisms (12)
- Capacity Drawdown Ledger — Records every deliberate over-envelope drawdown as dated capacity debt — with an owner, an expiry, and a repayment plan — so borrowed capacity is repaid before it silently becomes the new normal.
- Capacity Envelope Review Board — A standing body that convenes on cadence to weigh substrate evidence, exceptions, and breaches, and to decide whether the load envelope holds, tightens, or may be raised — so the limit is revised by accountable deliberation, not by operational drift.
- Carrying Capacity Assessment — Estimates the recurring load a system can carry indefinitely — deriving it from how fast the substrate renews, how it degrades under load, and the uncertainty around both — rather than from what the system has managed once.
- Demand Admission Gate — Decides at the point of entry whether each new unit of demand is admitted, queued, redirected, or staged — so the envelope is protected by controlling what gets in, before load is ever taken on.
- Ecosystem or Asset Monitoring Transect — Repeatedly samples the same fixed route or points across a system to read the actual condition of the load-bearing substrate — turning ground-truth about depletion into evidence that can override optimistic output numbers.
- Load Shedding Trigger — Fires a pre-defined, staged reduction of service, extraction, or commitments the moment a depletion band is crossed — cutting load already being carried, in a set order, before a breach turns into substrate damage.
- Recovery Window or Rest Period — Reserves protected time — a fallow, a closed season, a mandated rest — when load is deliberately withheld so the substrate can renew, buying capacity back before it is spent down.
- Regenerative Budget — Meters allowable load against what the stock regenerates each period — spending the yield and preserving the principal — so today's draw never eats the capacity that funds tomorrow's.
- Safe Operating Envelope Chart — Draws the sustainable envelope as a few named zones — green, warning, restriction, emergency, restoration — so operators and stakeholders see at a glance where load sits and what that zone demands.
- Substrate Depletion Dashboard — Puts the substrate's condition — stock level and depletion rate — on one screen beside throughput and sustained demand, so the hidden cost of today's output is visible next to the output.
- Sustainable Yield Quota — Caps total take for a period at what the substrate can renew — the sustainable yield — and allocates that cap into shares, so the sum of everyone's draw cannot outrun renewal.
- Utilization Ceiling and Headroom Rule — Fixes the normal operating point below maximum capacity and reserves the gap as standing headroom, so the substrate can absorb variance and recover instead of running flat out toward collapse.
- Symbiotic Alignment: Design a relationship so each party's success reinforces the other's success rather than extracting value one-sidedly.▸ Mechanisms (8)
- Cooperative Supply Contract — Structures buyer-supplier relations around reliability, fair risk sharing, capability investment, and long-term mutual capacity.
- Ecological Pairing Plan — Pairs species, habitats, or land-use practices so each supports the conditions under which the other can thrive.
- Mentorship Exchange Program — Creates reciprocal learning and contribution flows where mentor and learner both gain capability, perspective, or social capital.
- Mutualistic Service-Level Agreement — Extends ordinary service commitments with reciprocal support, responsiveness, repair duties, and shared improvement responsibilities.
- Partnership Operating Agreement — Turns the relationship design into explicit roles, contributions, shared goals, review cadence, escalation paths, and revision rules.
- Platform Ecosystem Incentive Scheme — Allocates access, visibility, fees, rewards, data, or support so platform growth also strengthens participants and complements.
- Public–Private Partnership Agreement — Coordinates public mission, private capacity, risk allocation, accountability, and shared benefit in a continuing institutional relationship.
- Shared Success Dashboard — Displays joint viability indicators and imbalance signals so parties can see whether the relationship is reinforcing or extractive.
- System Archetype Diagnosis: Match a recurring feedback pattern to a known system archetype so the likely failure mode and intervention family become visible.▸ Mechanisms (10)
- Archetype Fit Checklist — Tests a proposed system-archetype match against its evidence and its strongest rival before the label is allowed to guide action.
- Causal Loop Diagram — Draws the pressure behind a hazard, the feedback loops that regenerate it, and the delays between them, so a control can be aimed at the loop rather than the symptom it displaces.
- Escalation Archetype Mapping — Maps a runaway tit-for-tat between two parties as the Escalation archetype — two balancing loops coupled through relative position — so the rivalry can be diagnosed instead of fought.
- Fixes That Fail Diagnosis — Diagnoses a problem that keeps relapsing as Fixes That Fail — a quick fix whose delayed side effect quietly recreates the very symptom it relieved.
- Leverage Point Matrix — Ranks candidate places to intervene in the diagnosed loop by how much structural change each buys, so effort goes to high-leverage sites instead of the obvious low-leverage ones.
- Limits to Growth Diagnosis — Diagnoses stalled growth as Limits to Growth — a reinforcing engine running into a balancing constraint — and locates the binding limit that caps it.
- Pattern Diagnosis Workshop — Convenes the people who each see one arc of a recurring problem to build a shared loop map and narrow to a provisional archetype together.
- Shifting the Burden Diagnosis — Diagnoses a deepening reliance on a symptomatic quick fix as Shifting the Burden — where the easy relief crowds out and atrophies the fundamental solution.
- System Archetype Template — A reusable pattern card — typical symptoms, loop skeleton, and intervention hints for one named archetype — used as the reference a live map is matched against.
- Tragedy of the Commons Diagnosis — Diagnoses the degradation of a shared resource as Tragedy of the Commons — where individually rational use, summed across users, destroys the pool everyone depends on.
- Tempo-Matched Response Governance: Make the response clock fit the environment clock so correct decisions arrive while they are still useful and not before the target is ready.▸ Mechanisms (12)
- Decision Latency Scorecard — Breaks a decision loop into sensing, analysis, approval, handoff, execution, and feedback stages and times each one, so the slowest stage stops hiding inside a single 'we're too slow'.
- Environmental Time-Constant Estimate — Measures how fast the environment itself changes — its characteristic time constant — so every internal clock has a real yardstick to be matched against.
- Event-Triggered Escalation Rule — Pre-wires the condition that flips a decision onto a faster authority track the instant an environmental event crosses a set tempo threshold — so no meeting is needed to decide to hurry.
- Freshness Timer or Timestamp Badge — Stamps every piece of evidence, forecast, approval, and decision with its age and time-to-expiry, so staleness is visible at a glance instead of assumed away.
- Hold-and-Revalidate Protocol — When an action's underpinning evidence has aged past its validity window, this protocol halts it in place and refuses to release it until the assumptions are re-checked against current reality.
- Lead-Time Decomposition Map — Splits total response time into its segments — prepare, authorize, move, implement, propagate, take effect — so the stage that actually delays the outcome becomes visible and addressable.
- Preapproved Response Playbook — Decides in advance, and in calm, which responses are pre-authorized within which bounds — so that when the trigger fires the team executes a standing play instead of starting a deliberation.
- Queue-Jump Authority — Grants a named authority the standing right to pull a time-critical item out of the ordinary queue — under pre-set conditions and with every jump logged — so a fast threat isn't paced by a slow line.
- Readiness Gate — Holds an otherwise-ready action at the door until the environment, recipient, or market can actually receive it — turning 'we're finished' into 'released only when it will land.'
- Rolling Forecast Resynchronization — Keeps the timing assumptions live — re-estimating the environment's clock and resetting the response cadence each time new evidence moves the window — so decisions stay matched to a moving target.
- Slow-Release or Phased Absorption Plan — Meters an action out in absorbable increments instead of all at once, throttling to the receiver's uptake and sequencing along its lead times, so infrastructure or recipients take it up without overload or premature failure.
- Takt or Cadence Board — Puts both clocks on one board — the rhythm the work is running at and the rhythm the environment demands — so tempo mismatches and their bottlenecks are seen at a glance before they bite.
- Theory-Responsive Case Sampling Design: Select the next case because it can sharpen, challenge, extend, or saturate the emerging account—not because it statistically represents a population.▸ Mechanisms (10)
- Boundary Case Probe — Selects a case at the model's suspected edge to find out where the account stops applying.
- Case Selection Audit Trail — Preserves the versioned, time-ordered record of the sampling path — memos, access constraints, and each case's model effect — so the sequence can be reconstructed and defended.
- Constant Comparison Matrix — Compares each new case against prior cases and the current categories, forcing every difference into a model revision.
- Grounded Theory Sampling Memo — Records the current category, the open gap, and the reason for the next case before it is collected.
- Maximum Variation Case Round — Samples deliberately across the widest range of cases to see which findings survive maximum difference.
- Negative Case Sampling Pass — Actively hunts for a case that could disconfirm or puncture the current account rather than confirm it.
- Rival Explanation Discriminator — Chooses the one case whose outcome would separate two still-live rival explanations.
- Saturation Review Memo — Documents whether newly sampled cases have stopped changing the model, and convenes the decision to stop.
- Theoretical Gap Matrix — Maps the model's open gaps against candidate cases to rank which case would teach the most next.
- Transferability Claim Check — Audits the final claims against what the sampled cases can actually support, trimming overreach.
- Titrated Intervention: Adjust intervention intensity gradually based on observed response instead of applying full force immediately.▸ Mechanisms (8)
- Alert Threshold Tuning — Retunes the level at which alerts fire so responders catch real incidents without drowning in noise.
- Behavior Intervention Scaling — Increases or decreases prompts, coaching, incentives, reminders, or consequences based on observed behavior change and burden.
- Clinical Titration Protocol — Implements titrated intervention through professionally governed starting levels, adjustment increments, monitoring intervals, contraindications, and stop conditions.
- Gradual Rollout Intensity — Adjusts the scope, strictness, traffic share, or feature exposure of a rollout as real-world response becomes visible.
- Incremental Staffing Adjustment — Changes staffing levels, coverage, or support capacity in increments while monitoring service quality, backlog, cost, and overload.
- Phased Policy Intensity — Introduces enforcement, eligibility rules, incentives, or restrictions in adjustable stages rather than imposing the strongest version immediately.
- Progressive Training Load — Uses stepwise changes in training volume, intensity, or complexity while observing adaptation, fatigue, and performance response.
- Spend or Resource Ramp — Increases budget, capacity, or resource allocation stepwise while measuring marginal response, waste, and saturation.
- User Context Validation: Validate a solution against actual user behavior, needs, constraints, and context of use.▸ Mechanisms (10)
- Accessibility Review — Checks the solution against inclusion standards and the full range of sensory, cognitive, physical, and linguistic abilities, so no user is excluded by an assumption the design never examined.
- Analytics Behavior Review — Reads the whole population's behavioral traces — abandonment, errors, retention, search — to test a design assumption at scale and to check whether narrower evidence actually generalizes.
- Contextual Inquiry — Studies users in the actual setting where the work happens — watching and asking at the same time — so the situated constraints and workarounds that never surface in a lab become visible.
- Diary Study — Has users log their own experience in the moment, repeatedly over days or weeks, so recurring friction and delayed consequences that no single session can reach come into view.
- Field Observation — Watches users act in the real setting where the solution must work, surfacing the tacit routines, workarounds, and situated constraints they could never report from a conference room.
- Journey Map — Lays a user's end-to-end path out as a single picture — touchpoints, handoffs, delays, and emotional lows — so scattered findings become a prioritized map of where the design fails.
- Participatory Design Session — Brings affected users into the design room as co-authors, so the people who will live with the solution shape the revision instead of only supplying evidence for it.
- Service Pilot — Runs the whole solution as a small, real, bounded service so end-to-end fit, support needs, and outcomes can be seen — and its findings drive revision before full rollout.
- Usability Test — Puts users in front of the solution and asks them to attempt representative tasks, making friction, errors, and comprehension gaps visible where interaction actually breaks.
- User Interview — Surfaces users' own goals, constraints, and felt needs in guided conversation, so the design's beliefs about who the user is and what they lack can be tested against their own account.
- Variation–Selection–Retention Engine Design: Shape adaptive change by making the variation supply, selection pressure, reproduction or retention channel, and diversity safeguards explicit.▸ Mechanisms (12)
- Adverse Adaptation Red Team — A chartered, safety-bounded exercise in which defenders imagine how an adaptive adversary would evolve to slip past the current barrier set — and whether the nominally independent layers would fall to the same move.
- Champion–Challenger Rotation — Keeps a reigning champion variant in the live role while challengers run alongside it, and promotes a challenger only when it beats the champion by a preset margin over enough exposure — so winners propagate on proven, not apparent, improvement.
- Environmental Shift Retest — When the environment moves, re-runs the selection test on the variants that already won — checking whether they are still the fittest, and whether the fitness proxy still tracks reality — so the loop stops rewarding champions selected for a world that no longer exists.
- Escape Variant Watchlist — A governed, evidence-graded register of known and plausible escape variants — what each is, how strong the evidence is, who owns it, when it is next reviewed, and its response status — so uncertain classes are tracked over time without being treated as confirmed threats.
- Fitness Proxy Audit — Audits what your barrier and its metrics actually reward for surviving — exposing proxies that let an escape variant look 'handled' precisely because it has become harder to see.
- Generation Cadence Review — Checks whether the selection loop is turning at the right tempo — fast enough to adapt, slow enough that each generation is judged on signal rather than noise — and re-sizes the generation unit, coupled to the variation supply, when it is not.
- Multi-Pressure Tradeoff Matrix — Lays out the several selection pressures acting at once against the traits they reward, making visible where optimizing for one quietly degrades another — so the loop chooses its fitness function instead of backing into one.
- Retention / Pruning Protocol — Governs which retained variants earn continued storage and which are culled, keeping the surviving library small and current without ever pruning below the diversity reserve the loop needs to keep adapting.
- Selection Loop Map — Makes an implicit selection loop explicit by charting its stations — the population of variants, how winners reproduce, and where selection actually bites — so the whole engine can be seen and steered.
- Selection Pressure Sandbox — A contained copy of the selection loop for applying a candidate pressure to a variant population and watching what it actually breeds — before that pressure is turned loose on the live system.
- Variance Floor Trigger — A tripwire that fires when a population's diversity falls toward a floor, forcing fresh variation back in before selection grinds the pool down to a single fragile winner.
- Variant Lineage Log — A running record of every variant's ancestry and fate — losers included — so the engine can trace which forebear a trait, or a failure, descends from.
- Whole-System Alignment: Align local parts and incentives with the behavior of the whole system so local optimization does not undermine global viability.▸ Mechanisms (8)
- Balanced Scorecard — Tracks multiple performance dimensions to reduce single-metric tunnel vision in organizations.
- Cross-Silo Governance Forum — Gives interdependent units a standing body with authority to adjudicate cross-boundary tradeoffs and rewrite shared rules.
- Ecological Management Plan — Aligns land uses and stakeholders around ecosystem viability across long horizons and cross-boundary effects.
- Integrated Planning Process — Reconciles separate budgets, schedules, and dependencies into one end-to-end plan owned across the parts.
- Patient Care Team Conference — Convenes a patient's specialists to re-plan care around the whole-person outcome no single discipline owns.
- Shared OKRs or Cross-Functional Goals — Binds interdependent teams to one common objective while each keeps ownership of how it hits its own key results.
- System Health Review — Puts local scorecards next to whole-system outcomes on a cadence to catch local wins that quietly harm the whole.
- Systems Engineering Review — Checks at design gates that component and interface choices add up to the performance the whole system must deliver.
Also a related prime in 447 archetypes
- Absorptive Capacity Building: Build the ability to recognize, translate, assimilate, and apply useful external knowledge.
- Accountable Gatekeeping Design: Design choke-point selection so passage decisions use explicit criteria, bounded discretion, traceable reasons, review paths, and distribution audits rather than opaque gatekeeper preference.
- Activation Decay Measurement: Treat priming as a fading state: measure its useful lifetime, set an action or refresh window, and stop relying on it after it expires.
- Activation Energy Cost-Benefit Analysis: Before paying the start-up burden to cross a threshold, compare the full activation cost with the expected durable benefit, uncertainty, and opportunity cost of alternatives.
- Active Goal Shielding: Protect the current goal by reducing access to competing goals, preserving only explicit exceptions, and releasing suppression once the goal window ends.
- Active Knowledge Construction: Have learners build usable understanding by connecting new experience to prior knowledge, surfacing misconceptions, and revising their own mental models.
- Acute Stabilization Command: Activate a temporary, bounded command regime that stabilizes an acute disruption before full diagnosis, then exits into recovery and learning.
- Adaptive Mutation Rate Management: Treat deliberately introduced variation as a tunable control variable: increase it when the system needs exploration and reduce it when the system needs stability, safety, or convergence.
- Adaptive Opponent Rehearsal: Rehearse a plan against an adaptive opponent before commitment so hidden assumptions surface as the opponent moves, counters, exploits, and changes the state of play.
- Adaptive Precision-Weighted Signal Fusion: Combine imperfect signals by how reliable they are now, not by treating every input as equal or permanently trustworthy.
Notes¶
Feedback is the foundational mechanism of cybernetics and control theory, introduced by Wiener and developed by Ashby, Bateson, Forrester, and Powers. The concept pervades engineering (thermostats, PID controllers, servo mechanisms), biology (homeostasis, endocrine regulation), economics (price signals, demand adjustment), ecology (predator-prey dynamics), organizations (review cycles, quality feedback), and social dynamics (reputation, norm enforcement). The Structural Tensions section reflects the practical challenges of implementing feedback-controlled systems: sign ambiguity, gain-delay interaction, reference drift, loop coupling, sensor error, and disturbance classification. These tensions cannot be "solved" but must be actively managed through careful loop design, parameter tuning, and structural analysis.
References¶
[1] Wiener, N. (1948). Cybernetics: Or Control and Communication in the Animal and the Machine. Cambridge, MA: MIT Press. Founding text establishing feedback as the foundational concept of control + communication in engineered and biological systems, including feedback-induced oscillation/hunting. Supports markers 001 (Wiener introduced feedback as foundational) and 005 (the oscillation/overshoot/runaway failure modes shared with thermostat control). registry ↩a ↩b
[2] Nyquist, H. (1932). "Regeneration Theory". Bell System Technical Journal, 11(1), 126-147. Provides the graphical stability criterion for feedback amplifiers in the complex plane, assessing closed-loop stability from open-loop frequency response (gain and phase). Supports markers 002 (Nyquist stability criterion / Bode analysis) and 010 (joint gain-delay/phase-margin determination of stability). registry ↩a ↩b
[3] Black, H. S. (1934). "Stabilized Feed-Back Amplifiers". Bell System Technical Journal, 13(1), 1-18. Invention and theory of the negative-feedback amplifier: feedback reduces distortion and stabilizes gain against component and temperature variation, at the cost of reduced gain unless open-loop gain is high. Supports marker 003. registry ↩
[4] Beer, S. (1966). Decision and Control: The Meaning of Operational Research and Management Cybernetics. London: John Wiley & Sons. Management-cybernetics treatment of feedback and control applied to organizations and operational decision-making. Supports marker 004 (feedback at organizational scale - the weekly customer-complaint review loop). registry ↩
[5] Ashby, W. R. (1956). An Introduction to Cybernetics. London: Chapman & Hall. States and proves the Law of Requisite Variety: a regulator's response repertoire must match the disturbance variety it faces, otherwise regulation fails - the formal feedback-regulation framework that transfers across substrates. Supports marker 006 (Ashby's feedback framework applies unchanged). registry ↩
[6] Forrester, J. W. (1961). Industrial Dynamics. Cambridge, MA: MIT Press. Origin of the demand-amplification ('bullwhip') phenomenon: small downstream demand fluctuations are amplified into large upstream order swings as a direct consequence of loop gain and delay mis-tuning. Supports marker 007 (supply-chain feedback loops with delays produce the bullwhip effect). registry ↩
[7] Maruyama, M. (1963). "The Second Cybernetics: Deviation-Amplifying Mutual Causal Processes". American Scientist, 51(2), 164-179. Draws the distinction between deviation-counteracting (negative, mutual-negative-feedback) and deviation-amplifying (positive, mutual-positive-feedback) loops, naming the positive-feedback pathways behind bubbles, vicious circles, and morphogenesis. Supports markers 008 and 009. registry ↩a ↩b
[8] Conant, R. C., & Ashby, W. R. (1970). "Every Good Regulator of a System Must Be a Model of That System". International Journal of Systems Science, 1(2), 89-97. Proves the good-regulator theorem: any maximally simple, maximally successful regulator must be isomorphic to (model) the system it regulates - the theoretical basis for the claim that a loop is only as trustworthy as the reference/model it controls toward. Supports marker 011 (setpoint vs drift: loop behavior is only as good as its reference). registry ↩
[9] Powers, W. T. (1973). Behavior: The Control of Perception. Chicago: Aldine. Introduces perceptual control theory, modeling organisms as controlling perceptions toward internally-generated reference signals. Supports marker 012 (organisms controlling for internally-specified reference values; feedback control cannot guarantee correct purpose if the reference is wrong). registry ↩
[10] Sterman, J. D. (2000). Business Dynamics: Systems Thinking and Modeling for a Complex World. Boston: Irwin/McGraw-Hill. Canonical system-dynamics text on how multiple feedback loops interact to produce surprising aggregate behavior, and how a loop well-tuned for one disturbance class can be poorly tuned for others. Supports markers 013 (loop isolation vs interaction) and 015 (feedback coupling vs external/novel disturbance). registry ↩a ↩b
[11] Bateson, G. (1972). Steps to an Ecology of Mind: Collected Essays in Anthropology, Psychiatry, Evolution, and Epistemology. San Francisco: Chandler Publishing. Explores how ecological and social feedback loops interact to produce surprising behaviors (schismogenesis, double bind). Supports marker 014 (ecological and social feedback loops often interact to produce surprising behaviors). registry ↩
[12] von Bertalanffy, L. (1968). General System Theory: Foundations, Development, Applications. New York: George Braziller. General systems theory across biological and social organisms; feedback regulation and homeostasis. Bibliography-only entry (not cited in body). registry
[13] Meadows, D. H. (2008). Thinking in Systems: A Primer (D. Wright, Ed.). White River Junction, VT: Chelsea Green Publishing. The discipline's canonical introduction, codifying stocks, flows, delays, and reinforcing/balancing feedback loops as the working vocabulary of systems thinking. Bibliography-only entry (not cited in body). registry
[14] von Foerster, H. (1979). "Cybernetics of Cybernetics." In K. W. Back (Ed.), Social Processes and Social Dynamics (pp. 5-8). New York: John Wiley & Sons. Second-order cybernetics framework distinguishing the cybernetics of observed systems from the cybernetics of observing (self-observing, reflexive) systems. Bibliography-only entry (not cited in body); no authoritative DOI/publisher page located, left link-less. registry
[15] Kauffman, S. A. (1993). The Origins of Order: Self-Organization and Selection in Evolution. New York: Oxford University Press. Develops autocatalytic-set theory as a formal model of collective self-production in chemical reaction networks. Bibliography-only entry (not cited in body). registry