0. Plain Statement

If feedback demands response while slack is near zero, the loop consumes the system rather than regulating it.

Plain-language version:

Feedback is not automatically helpful. If a system has no spare capacity to receive, process, respond, repair, or integrate feedback, then more feedback becomes more load.

1. Formal Definition

The Feedback Without Slack Becomes Extraction Law states that feedback must be absorbable to regulate a system coherently.

Feedback is supposed to help a system learn, adapt, correct, repair, and reduce recurrence. But feedback is not free. It consumes attention, interpretation capacity, emotional capacity, time, energy, auditability, coordination, repair capacity, and response bandwidth.

When slack is available, feedback can regulate.

When slack is near zero, feedback can extract.

Feedback becomes extraction when the demand to receive, interpret, answer, justify, report, respond, explain, correct, document, or repair exceeds the receiving system’s capacity. In that state, the feedback loop no longer stabilizes the system. It consumes the very capacity required for restoration.

Feedback must therefore be absorbable.

Otherwise it increases hidden debt.

2. Canonical Form

σ≈0 + feedback demand↑ ⇒ extraction / H↑

Expanded canonical form:

feedback regulates only when the receiving system has enough slack, bandwidth, restoration capacity, and boundary integrity to absorb and act on it

Failure expression:

unabsorbable feedback ⇒ response burden↑ + R_eff↓ + H↑

Source rule:

Feedback must be absorbable.
Otherwise it increases hidden debt.

Related variables:

O, H, ε, ι, Au, R, R_eff, BΣ, K, µᵢ, Φ, σ, 𝓑, 𝓓, Γ, Π, Θ, Ψ, Τ, FI

Where:

3. Core Mechanism

The Feedback Without Slack Becomes Extraction Law unfolds when feedback is valid or visible but not absorbable.

Coherent feedback pathway

feedback arrives
→ receiving system has slack
→ feedback is classified and prioritized
→ response burden is bounded
→ restoration capacity engages
→ feedback routes into repair
→ hidden debt decreases
→ recurrence weakens

Extractive feedback pathway

feedback arrives
→ slack is near zero
→ system must respond anyway
→ attention, time, energy, and repair capacity are consumed
→ response burden rises
→ restoration capacity falls
→ hidden debt accumulates
→ recurrence persists or worsens

The core mechanism is:

feedback that exceeds absorbability becomes load

A feedback loop can become extractive even if the feedback is well-intended, accurate, necessary, or morally justified. The question is whether the receiving system has the capacity to process and repair from it.

4. When This Law Applies

This law applies whenever feedback, reporting, review, complaint, audit, correction, appeal, monitoring, supervision, performance evaluation, survey, check-in, intake, incident report, governance process, training loop, model evaluation, or repair demand requires a response from a low-slack system.

It is especially important when:

• feedback volume rises;
• the receiving node is depleted;
• response is mandatory;
• appeal or complaint systems demand extensive effort from harmed nodes;
• audit burden falls on the damaged party;
• reporting requirements exceed capacity;
• AI governance queues overwhelm staff;
• security alerts exceed analyst bandwidth;
• institutions demand documentation from overloaded people;
• medical systems require high coherence from exhausted patients;
• teams receive more review feedback than they can integrate;
• feedback is repeated but restoration capacity is absent;
• accountability requests become unmanaged workload;
• “participation” becomes unpaid labor;
• feedback is used to signal care without funding repair.

The law applies strongly when:

feedback demand > receiving system slack + bandwidth + restoration capacity

or when:

feedback collection increases while repair capacity does not

Typical domains:

5. When This Law Does Not Apply

This law should not be used to avoid feedback, accountability, audit, complaint pathways, or correction.

Feedback remains necessary. The law requires systems to make feedback absorbable, not to suppress it.

This law does not justify:

• ignoring complaints;
• silencing harmed nodes;
• avoiding audit;
• rejecting accountability;
• deleting feedback;
• reducing transparency;
• refusing correction;
• claiming low capacity as permanent immunity.

Feedback can be coherent under low slack when:

• feedback is prioritized;
• response burden is reduced;
• support is added;
• repair capacity is increased;
• feedback is routed to responsible nodes;
• affected nodes are not forced to carry the full burden;
• response is staged;
• urgency is limited to true emergencies;
• feedback collection is paired with restoration capacity.

False-positive cases:

Important distinction:

The problem is not feedback. The problem is unabsorbable feedback that demands response without supplying capacity.

6. Diagnostic Signature

Canonical diagnostic:

σ≈0 + feedback demand↑ ⇒ extraction / H↑

Warning signature:

feedback volume↑
response obligation↑
σ↓
𝓑↓
R_eff↓
recurrence unchanged
H↑
⇒ feedback extraction

Common indicators:

Additional diagnostics:

7. Failure Pattern

If ignored, this law produces feedback fatigue, response overload, and hidden debt.

General failure pathway:

feedback need appears
→ system lacks slack
→ feedback demand increases anyway
→ response burden consumes capacity
→ repair capacity falls
→ visible responsiveness may rise
→ hidden debt accumulates
→ recurrence persists
→ system becomes less able to receive future feedback

Common failure modes:

• Feedback Extraction — feedback consumes more capacity than it restores.
• Zero-Slack Feedback Burden — low-slack system is required to respond.
• Silent Extraction — feedback work is invisible but drains the node.
• Response Overload — system becomes unable to process feedback coherently.
• Compression Collapse — feedback demand accelerates compression.
• Restoration Capacity Exhaustion — repair capacity is consumed by response burden.
• Feedback Fatigue — repeated unabsorbable feedback degrades participation.
• Pseudo-Responsiveness — visible feedback handling improves while repair does not.
• Audit Burden Inversion — harmed or depleted nodes must prove what the system should audit.
• Victim Pathway Overload — damaged nodes face pathways requiring capacities harm already reduced.
• Hidden Debt Accumulation — unresolved feedback burden becomes future cost.
• Burnout Basin — chronic feedback overload becomes normalized.

Compact failure signature:

feedback demand↑ + σ≈0 + R_eff↓ ⇒ extraction loop

8. Restoration Implications

Restoration requires reducing feedback burden, adding capacity, and routing feedback into repair rather than response theater.

The first restoration question is not:

How do we get more feedback?

The first restoration question is:

Can this system absorb the feedback it already receives?

Restoration priorities:

1. Measure feedback demand.
2. Measure receiving slack and bandwidth.
3. Measure restoration capacity.
4. Separate valid feedback from response burden.
5. Prioritize feedback by risk and repair value.
6. Add capacity before demanding response.
7. Reduce unnecessary reporting or performance loops.
8. Shift burden away from harmed or depleted nodes.
9. Route feedback into origin-layer repair.
10. Time-validate recurrence reduction and ring-down improvement.

Relevant restoration arcs:

Minimal restoration sequence:

measure feedback demand
→ measure σ / 𝓑 / R_eff
→ reduce or prioritize feedback load
→ add capacity
→ shift burden to responsible nodes
→ route feedback into repair
→ validate H↓, recurrence↓, and 𝓓↑

Temporal validation requirement:

σ↑
𝓑 sufficient
R_eff↑
response burden↓
feedback absorbability↑
H↓
recurrence↓
𝓓↑
affected-node burden↓
O stable or rising

9. Design Rule

Do not demand feedback response from systems without the slack to absorb and act on it.

Operational design requirements:

• Measure feedback demand before increasing it.
• Protect slack for response and repair.
• Add capacity when feedback volume rises.
• Reduce feedback burden on harmed or depleted nodes.
• Prioritize feedback by consequence and repair value.
• Pair feedback collection with restoration capacity.
• Make feedback easier to submit and process.
• Avoid demanding repeated proof from the same node.
• Track response burden as system load.
• Validate that feedback reduces recurrence.

Avoid:

• collecting feedback without capacity to act;
• demanding documentation from damaged nodes;
• treating participation as free labor;
• requiring exhausted systems to explain their exhaustion;
• making appeals harder than the original harm;
• measuring responsiveness by volume handled;
• treating feedback fatigue as apathy;
• increasing audits without support;
• creating accountability pathways that only extract testimony;
• treating “we heard you” as repair.

10. Cross-Scale Expressions

11. Examples

Example A — Security Alert Fatigue

Scenario:

A SOC receives more alerts than analysts can meaningfully process. More alerts do not improve security; they drain attention and increase missed incidents.

Law expression:

alert feedback demand↑ + σ_security≈0 ⇒ extraction / H_security↑

Interpretation:

Security feedback must be triaged, prioritized, and made absorbable.

Example B — AI Appeals Backlog

Scenario:

An AI platform offers appeals, but appeal volume exceeds review capacity. Users must repeatedly explain harm while the system cannot repair policy or classification.

Law expression:

appeal feedback demand > R_governance ⇒ H_user + H_platform↑

Interpretation:

Appeals without restoration capacity become extraction from users.

Example C — Institutional Complaint Burden

Scenario:

A harmed person must repeatedly document harm, retell events, gather proof, meet deadlines, and navigate forms while already depleted.

Law expression:

pathway demand > damaged-node capacity ⇒ feedback extraction

Interpretation:

The complaint pathway may become a second harm.

Example D — Team Code Review Overload

Scenario:

A team receives so many review comments, tickets, and process feedback loops that no one has capacity to integrate them.

Law expression:

feedback volume↑ + integration slack↓ ⇒ H_technical↑

Interpretation:

Feedback improves quality only when it can be absorbed.

Example E — Medical Reporting Burden

Scenario:

A patient with low energy is asked to track many symptoms, fill repeated forms, coordinate appointments, and explain complex history without support.

Law expression:

feedback demand > bio/social capacity ⇒ restoration burden inversion

Interpretation:

The care system extracts feedback from the person whose capacity is already damaged.

Example F — Governance Consultation Theater

Scenario:

A community is asked to provide repeated feedback, but no capacity is allocated to process or implement it.

Law expression:

participation demand↑ without R_governance↑ ⇒ legitimacy debt↑

Interpretation:

Feedback collection becomes legitimacy extraction when it cannot change outcomes.

12. Relationship to Nearby Laws

Aliases folded into this law:

• Feedback Without Slack Becomes Extraction Law
• Feedback Absorbability Law
• Zero-Slack Feedback Extraction Law
• Feedback Burden Law
• Unabsorbable Feedback Law

Deduplication note:

This law should remain the root feedback-absorbability law. LAW-048 handles feedback integrity; LAW-049 handles whether the system has the slack and restoration capacity to absorb feedback without extracting from itself or affected nodes.

13. Operator Mapping

Coherent operator sequence:

Ψ(feedback) → Γ(priority / absorbability) → Σ(scope / bandwidth) → Π(response limits) → ℛ(repair capacity) → Τ(validate H↓ and recurrence↓)

Inverted operator sequence:

feedback demand↑ → σ≈0 → Π(response obligation) → R_eff↓ → H↑ → Ξ / ι↑ → feedback fatigue / recurrence↑

14. Machine-Readable Summary

id: "LAW-049"
name: "Feedback Without Slack Becomes Extraction Law"
type: "law"
status: "draft"
family:
  - "Cybernetic and Meta-Theory Laws"
summary: "If feedback demands response while slack is near zero, the loop consumes the system rather than regulating it."
canonical_statement: "If feedback demands response while slack is near zero, the loop consumes the system rather than regulating it."
canonical_form: "σ≈0 + feedback demand↑ ⇒ extraction / H↑"
failure_form: "unabsorbable feedback ⇒ response burden↑ + R_eff↓ + H↑"
source_rule: "Feedback must be absorbable. Otherwise it increases hidden debt."
variables:
  primary:
    - "σ"
    - "K"
    - "feedback demand"
    - "𝓑"
    - "R"
    - "R_eff"
    - "FI"
    - "BΣ"
  secondary:
    - "O"
    - "H"
    - "ε"
    - "ι"
    - "Au"
    - "µᵢ"
    - "Φ"
    - "Γ"
    - "Π"
    - "Θ"
    - "Ψ"
    - "Τ"
    - "𝓓"
diagnostics:
  - "Slack"
  - "Feedback Absorbability"
  - "Bandwidth"
  - "Restoration Capacity"
  - "Response Burden"
  - "Feedback Integrity"
  - "Compression"
  - "Hidden Debt"
  - "Inversion Index"
  - "Recurrence"
  - "Ring-Down"
  - "Affected-Node Capacity"
failure_modes:
  - "Feedback Extraction"
  - "Zero-Slack Feedback Burden"
  - "Silent Extraction"
  - "Response Overload"
  - "Compression Collapse"
  - "Restoration Capacity Exhaustion"
  - "Feedback Fatigue"
  - "Pseudo-Responsiveness"
  - "Audit Burden Inversion"
  - "Victim Pathway Overload"
  - "Hidden Debt Accumulation"
  - "Burnout Basin"
restoration_arcs:
  - "Slack Regeneration"
  - "Restoration Capacity Rebuild"
  - "Controlled Decoupling"
  - "Boundary Reconstitution"
  - "Auditability Restoration"
  - "Temporal Validation"
  - "Recurrence Reduction"
  - "Origin-Layer Repair"
  - "Basin Supersession"
related_laws:
  - "LAW-017"
  - "LAW-020"
  - "LAW-021"
  - "LAW-022"
  - "LAW-023"
  - "LAW-025"
  - "LAW-026"
  - "LAW-030"
  - "LAW-040"
  - "LAW-041"
  - "LAW-045"
  - "LAW-048"
  - "LAW-050"
  - "LAW-051"
  - "LAW-066"
  - "LAW-073"
  - "LAW-075"
  - "LAW-104"
  - "LAW-108"
  - "LAW-115"
  - "LAW-124"
related_invariants:
  - "INV-001"
  - "INV-077"
operator_sequence:
  coherent:
    - "Ψ feedback"
    - "Γ priority / absorbability"
    - "Σ scope / bandwidth"
    - "Π response limits"
    - "ℛ repair capacity"
    - "Τ validate H↓ and recurrence↓"
  inverted:
    - "feedback demand↑"
    - "σ≈0"
    - "Π response obligation"
    - "R_eff↓"
    - "H↑"
    - "Ξ / ι↑"
    - "feedback fatigue / recurrence↑"
aliases:
  - "Feedback Without Slack Becomes Extraction Law"
  - "Feedback Absorbability Law"
  - "Zero-Slack Feedback Extraction Law"
  - "Feedback Burden Law"
  - "Unabsorbable Feedback Law"
deduplication_note: "Root feedback-absorbability law. LAW-048 handles feedback integrity; LAW-049 handles whether the system has the slack and restoration capacity to absorb feedback without extracting from itself or affected nodes."
source: "content/archive/laws/technical.md"

15. Compact Card Version

LAW-049 — Feedback Without Slack Becomes Extraction Law

If feedback demands response while slack is near zero, the loop consumes the system rather than regulating it.

Plain meaning:

Feedback is not automatically helpful. If a system has no spare capacity to receive, process, respond, repair, or integrate feedback, then more feedback becomes more load.

Canonical form:

σ≈0 + feedback demand↑ ⇒ extraction / H↑

Failure form:

unabsorbable feedback ⇒ response burden↑ + R_eff↓ + H↑

Source rule:

Feedback must be absorbable.
Otherwise it increases hidden debt.

Primary variables:

σ, K, feedback demand, 𝓑, R, R_eff, FI, BΣ, O, H, ι, Au, µᵢ, Γ, Π, Θ, Ψ, Τ, 𝓓

Diagnostic signature:

Feedback volume and response obligation rise while slack, bandwidth, restoration capacity, ring-down, and affected-node capacity fall. Hidden debt and recurrence do not decrease.

Failure risk:

Feedback extraction, zero-slack feedback burden, silent extraction, response overload, compression collapse, restoration capacity exhaustion, feedback fatigue, pseudo-responsiveness, audit burden inversion, victim pathway overload.

Restoration priority:

Measure feedback demand against slack, bandwidth, and restoration capacity; reduce and prioritize feedback load; add capacity; shift burden away from depleted or harmed nodes; route feedback into repair; and validate hidden debt, recurrence, and ring-down improvement.