Limitations and Guard Interpretation

Reference for the limits of automated checking, the meaning of guard outputs, and where researcher judgment is still required.

Licklider reduces the risk of common statistical and reporting mistakes, but it does not remove the need for researcher judgment.

This section explains where the boundary is.

Child pages

Known Limitations

Describes what the product cannot detect reliably from data and metadata alone.

Interpreting Guards and Heuristics

Explains how to read confirmations, warnings, heuristics, and export blocks.

Nullable Fields and Edge Cases

Explains why missing structure, ambiguous inputs, and edge-case data should be read conservatively even when the workflow can proceed.

Start here

  1. Start with Known Limitations to understand the main blind spots.
  2. Continue to Interpreting Guards and Heuristics to interpret warnings correctly.
  3. Use Nullable Fields and Edge Cases when data structure ambiguity is part of the problem.