Where is the debt stored now, and what local repair reduces it?

locality_dimensions:
  layer_locality: "repair must match U-layer of failure/debt"
  node_locality: "repair must reach the affected node, not only the governing node"
  time_locality: "repair must address recurrence and delayed effects"
  boundary_locality: "repair must address damaged interfaces and consent edges"
  memory_locality: "repair must update records, precedent, training, or recurrence patterns"
  capacity_locality: "repair must restore usable slack where capacity was depleted"

state_vector_relevance:
  H: "debt must be reduced where it is stored"
  Au: "traceability identifies repair location"
  BΣ: "boundary damage requires boundary-local repair"
  R: "repair capacity must be available at the affected node/layer"
  K: "slack must be restored where constraint caused collapse"
  µᵢ: "meaning must be repaired where contradiction persists"

affected node receives usable repair
origin and storage layer are identified
debt location is mapped before closure
recurrence pathway is altered
repair burden is not exported elsewhere

public reputation is repaired but harmed nodes remain burdened
policy is updated but capacity remains absent
classification changes but execution does not
payment occurs without boundary correction
punishment occurs without recurrence reduction

relationship:
  origin_layer_repair: "repair where failure began"
  repair_locality: "repair wherever the resulting debt is stored"

failure_risks:
  - Hidden Debt Export
  - Quiet Minimization
  - Symbolic Repair
  - Scapegoat Collapse
  - Procedural Theater
  - Repair Burden Transfer

machine_summary:
  id: GL-060
  term: Repair Locality
  definition: "The rule that repair must occur where debt, damage, boundary failure, or recurrence is actually stored."
  locality_types:
    - layer
    - node
    - time
    - boundary
    - memory
    - capacity
  prevents:
    - coherence_laundering
    - symbolic_repair
    - hidden_debt_export
    - recurrence_preservation