Cross-Field Rule Unchecked

What goes wrong

Each field is checked against its own allowed range, but the rule linking it to a sibling field (start before end, minimum below maximum, no duplicates) is never checked. Two individually valid values combine into a pair that breaks the rule the bounds exist for.

Example

A date-range form accepts 'from' and 'to' as valid dates each, and lets 'from' be later than 'to', producing an empty window.

Not to be confused with

Every value is in range on its own, unlike Storage range escapes input validation; and there is no race on a single check (Parallel Admission Bypass) — the missing piece is the rule relating two fields.

Discovered by

@sks24git GitHub

Field notes · 6

@sks24git2026-10-21

A balance-chain rule said 'compare with the neighbouring statement' but never said the neighbour must be adjacent. One missing month and a correct file is rejected as a balance error instead of a coverage gap.

Define 'neighbour' by contiguity, not order. Gaps belong to the coverage check.
Copy every gate clause into the binding spec. Prose in a design doc is not a test target.

@sks24git2026-10-14

Two reviewers are each told the other owns every category outside their own list, but the setup check validates each list alone. Give them lists with a gap and both skip that category, each trusting the other.

Validate a split as a whole, not each half. Two valid halves can still leave a hole.
Derive "the other side owns it" from the other side. A complement of your own list is a guess.

@sks24git2026-09-10beat 2 review rounds

The first ladder edit sharing nothing with the old one stamped every new deadline with now. The required set then went empty for anyone near the date, and empty was deliberately deny.

"Empty means deny" hides three states. Separate nothing-required, not-warned and unreadable before refusing.
A rule the operator cannot undo by retrying is a trap.

@sks24git2026-09-10beat 1 review round

Adding a milestone to a warning ladder jammed deletion for every cohort already past due. New rows are only ever scheduled in the future, while the gate demanded a full count under the current ladder.

A gate keyed on today's config re-judges history that cannot be recreated. Judge what was recorded, not what the config now asks for.
A config edit must not strand rows.

@sks24git2026-09-05beat 2 review rounds

A locked re-check of a two-field rule had no "does this write touch the pair" guard, and a resting pair could already break the rule. Every unrelated write on that row then fails with a message blaming a concurrent edit.

Judge only the fields a write moves. A resting violation is not this write's fault.
Reconcile derived bounds before publishing them. A floor above the ceiling is a knob nobody can set.

@sks24git2026-09-05

A daily job looked exactly one interval ahead for "ends soon" notices, so every deadline was seen by one run only. Skip that run once and the whole day's cohort gets its first notice as the freeze itself.

Let two runs see every deadline. A window equal to the tick turns one missed tick into silent loss.
Never bake a schedule number into copy. "24 hours" lies the day the window moves.