nw-cross-cutting-context-residency

Context Residency

Composition: Load with nw-cross-cutting-invariants; no forced sequence; return to its routing table for other concerns.

context:pay-on-demand-not-every-session — resident context is paid every session (STANDING)

Whoever needs it loads it; whoever does not need it must not pay for it in every session. Context injected at session start is a per-session tax on every reader, including the readers who will never touch that subject. Detail belongs where it is needed, at the moment it is needed — not resident.

Three residency classes; classify before you inject anything:

• MUST-BE-RESIDENT — if it is absent from context, it does not happen. The load-bearing case is a trigger: an instruction to arm, to check, to refuse. Nobody goes looking for what they do not know exists, so a trigger cannot be made reachable-on-demand — its absence is silent. Same for a safety warning whose omission causes harm before anyone would think to consult it.
• MAP-ONLY — the reader must know THAT a thing exists and roughly WHEN to reach for it. Not how it works. A name plus a one-line "reach for this when…" is the whole resident cost.
• REFERENCEABLE — pure detail, needed only by whoever is doing that specific thing.

Density is a second axis, independent of residency. Normative content cannot be GENERATED from code, but it can be COMPRESSED: doctrine is usually rules — subject · condition · action — written as narrative. A table says the same thing in a fraction of the bytes and reads better. Do not confuse "not derivable" with "not compressible"; measuring the first tells you nothing about the second.

The failure this clause prevents: a projection that ADDS instead of REPLACING. Retiring a duplicate is a saving; generating a new view beside a surviving hand-written one is a new divergence surface AND a bigger payload.

context:resident-doctrine-can-be-compensation-debt — resident prose that patches bad guidance is debt (STANDING)