Structural MovesDocumentation Index
Fetch the complete documentation index at: https://docs.svrnos.com/llms.txt
Use this file to discover all available pages before exploring further.
Definition
A rule exists. A responsible party encounters a case the rule was designed for. The rule is never invoked at decision time. The rule remains intact on paper. The connection between the case and the rule is never made operational. Five sub-types: awareness gap (party doesn’t know the rule applies), pattern-matching failure (party fails to recognize the case as fitting the rule), workflow gap (rule exists outside the path the case travels through), discretion structure (rule explicitly delegates activation to judgment that doesn’t fire), cross-handoff drop (rule is held by one party; case passes through a different party who doesn’t invoke it).Distinct from
- GER-404 — Rule exists but is never invoked at decision time → this code. No rule exists in the active ruleset for this harm category → GER-404.
- GER-420 — Rule exists and is held by a responsible party but never activated → this code. Rule stated in policy but no enforcement mechanism in production → GER-420.
Tags
mass-casualty · violence