Cybersecurity law, instrument by instrument

What this page claims, and what it does not

The stages are LexLint's own vocabulary. Four of the five boxes are the binding classes the /law/<jurisdiction> docket already draws (In force, Enacted but not yet in force, Proposed, and Repealed, withdrawn or blocked), so a square here and a square there mean the same thing. A struck-down instrument is spent on both readings.

Enjoined has its own box. Inside "Repealed, withdrawn or blocked" it would sit beside a mark that is a false description of a law a court has paused, and it would pool away a count that reads as a signal: how contested a jurisdictional hook is. The certainty ladder files enjoined as present law and the docket draws it spent; splitting it out here makes that disagreement the reader's choice instead of our silent one. It is off by default, which follows the docket.

One date column, and where a bare date would mislead it says what kind of date it is. "In force from" is commencement: the earlier of a published commencement event and the instrument's own effective date, the same choice lifecycle_band() makes and for the same reason, neither source is reliably the commencement, and the earlier one cannot make a law look newer than it is. A bracket qualifies the date where a bare one would mislead ([future] for a start date still ahead, [proposed] for a bill with no commencement to show, [enjoined], [struck down], [repealed], [superseded] or [withdrawn] for a spent instrument). Nothing is inferred from our own review date: a row with neither a date nor a status to explain the gap says "not recorded" instead.

The map is the table. Its fill is the count of instruments at the stages you chose, binned on the same RAMP_BINS edges /law/map uses, and it redraws on every change. Point at, click, or tab to a place for what applies there, every stage it holds shown even when your filter is excluding it.

Three ways of showing nothing, and they are different claims. A place washed pale holds cybersecurity law your filter is excluding, so widening the filter brings it back. A hatched place is one we track and hold no cybersecurity law for at all: that is a statement about our research, not about the law. A white place has no jurisdiction record for this topic at all. Only the first of the three moves when you change the filter; the other two are facts about us and hold still.

Nothing here needs the script. The default resultset is in the HTML: counts, tally, map fills and the hidden rows are all rendered at build. The script recomputes them when a box changes and does nothing else, which is what lets this page ship under script-src 'self' and be read whole by a crawler.