core/unreachable-defensive-guard

Flag defensive guards against states internal code cannot produce — they hide bugs and add noise.

Read it in the terminal

The same facts, from the checkout you are already in — no browser, and no network.

$ npx redlinegate explain core/unreachable-defensive-guard

Where this came from

You are most likely here from a review comment. A finding names its rule and, when your repository has told Redline where the standard is published, its address:

Redline/HIGH [core/unreachable-defensive-guard]: …
  → …/r/core/unreachable-defensive-guard

That second line is written by redline init --docs-url and is empty until an organisation sets one — there is no default, because a link to somebody else's copy of the standard is worse than no link. See Onboard a repository.

In context

This is a core rule: it applies in every profile, and every stack extends it rather than overriding it. The core standard lists it beside everything else a reviewer is asked to consider.

Other HIGH rules in this stack

• core/missing-boundary-error-handlingError handling belongs at real system boundaries: user input, network calls, storage, native modules, message consumers. Flag missing handling there.
• core/silent-async-failureAsync operations that can reject must not fail silently: no empty catch, no floating promises, no error logged then treated as success.
• core/argument-mutationFlag mutation of function arguments or shared objects.
• core/async-race-conditionFlag race conditions in async work: missing cancellation/abort when the owner unmounts, the request is superseded, or the context is cancelled.
• core/untracked-todoFlag `TODO`/`FIXME`/placeholder code without a ticket reference.
• core/naive-clockFlag time handling that assumes local timezone or a naive clock in new code.