Derivation follows the clock#

This page is generated from the code and must not be edited by hand.

Not available in this version. No file is counted as made from one written more than a minute after it, when both carry a trustworthy time.

derivation_follows_the_clock version 1

Kind of rule: Limits every conclusion keeps to (constraint). Limits what any conclusion may say, by naming what cannot be true together.
What it limits: derives
Reasoning: defeasible. A conclusion is usually right, and is retracted when a rule it names concludes against it.
What it reads: one file at a time

Is it available in this version?#

Not available in this version. Its test is declared and not written yet, so it refuses nothing.

It names no rule whose conclusion would defeat it.

Parameter	Shipped value	May be	What it does
`minimum_clock_tier`	`"document"`	one of `instrument`, `document`, `name`	The weakest clock rung either endpoint may carry before the refusal applies. The ladder orders by copy-robustness rather than by accuracy, because a filesystem clock can be exact to the nanosecond and still record when somebody moved a folder.
`tolerance_seconds`	`60`	seconds, from 0 to 86400	How far a source may postdate its output before the pair is refused. A pipeline holding its input open while writing, a filesystem with one-second resolution and a document stamped before its last page was rendered all produce small real inversions.