Source changed 2026-10-03 16:02:47 UTC · snapshot created 2026-10-03 16:03:51 UTC · last check 2026-10-03 16:40:20 UTC
C.3.2:3 - Forces
Force
Tension
Readable use vs reusable declaration
One case should stay ordinary, while repeated classification needs a stable criterion and assumptions.
Admissibility vs uncertainty
Candidate or slice mismatch means no judgment; missing knowledge for an admissible request means unknown.
Criterion condition vs evidentiary use
The direct condition named by the criterion can be physical, relational, epistemic, institutional, or publication-dependent; use as evidence alone creates none of them.
False vs unknown
Known criterion failure differs from unavailable support or dependency.
Intent vs extension
A declaration can stay fixed while candidate state or selected slice changes the true-candidate set.
Set use vs ontology
A query may need a set without creating a collection holon, direct relation occurrence, or U.EntitySet.
Scope vs evaluation input
Claims may be scoped; the kind is not. The context slice is an explicit input.