Claim-Evidence Boundary

A claim-evidence boundary states exactly what a result proves and what it does not prove. It is useful for papers, Korean synthesis posts, project notes, and concept pages.

The minimal form is:

If any part is missing, the claim should be narrowed or marked to verify.

Boundary Fields

FieldQuestion
ClaimWhat exact statement is being made?
TaskWhat input and output space does the evidence test?
DataWhich population, benchmark, preprocessing, and split define the examples?
ProtocolHow were model selection, threshold choice, early stopping, and final testing separated?
MetricWhat number supports the claim, and what does it average over?
BaselineWhat comparison makes the result meaningful?
UncertaintyIs the effect larger than seed variation, confidence interval, or measurement noise?
ScopeWhere should the claim be expected to hold?

Narrowing Rule

Write the broad version first, then narrow it until every word is supported.

Broad ClaimNarrower Claim
This model generalizes to proteins.This model improves metric on a protein-family split for benchmark .
This method improves docking.This method improves pose plausibility under the reported pocket and ligand-preparation protocol.
This architecture is better.This architecture improves metric under matched data, objective, and training budget.
This objective learns better representations.This objective improves downstream metric under the stated frozen or fine-tuned protocol.
This benchmark proves real-world performance.This benchmark supports the specific population, split, and allowed-information boundary it defines.

Formula View

An empirical claim usually estimates a target quantity:

but reports a finite estimate:

  • : target quantity the claim wants to support.
  • : measured estimate.
  • : evaluation unit, such as example, query, molecule, complex, pose, target, or task.
  • : intended population or deployment distribution.
  • : benchmark or test-set distribution actually sampled.
  • : metric contribution for one unit.

The claim is only as broad as the match between and .

Molecular Modeling Checks

Claim TypeBoundary To State
Molecule propertymolecule standardization, label source, scaffold or time split, metric
Protein predictionsequence identity or family split, residue indexing, structure source, metric
Protein-ligand complexligand scaffold, protein family, complex-pair split, pocket definition, coordinate source
Docking posereceptor preparation, ligand state, pose RMSD rule, geometry checks, known-pocket assumption
Virtual screeningactive/decoy construction, enrichment metric, property bias, target context
Generative moleculevalidity, uniqueness, novelty, diversity, constraint satisfaction, filtering rule

Use In Posts

For Korean synthesis posts, include only the boundary needed for the reader:

  • What claim is being discussed?
  • What evidence supports it?
  • What split or benchmark limits the claim?
  • Which wiki note holds the detailed metric, formula, or paper evidence?

Long evidence tables belong in Evidence table or paper notes. The post should keep the boundary readable.

Red Flags

  • A random split is used to claim new-scaffold or new-protein generalization.
  • A metric is reported without model-selection or threshold-selection details.
  • A benchmark score is treated as deployment performance without population matching.
  • A molecular result ignores standardization, assay context, or leakage.
  • A small score difference is interpreted without uncertainty or paired comparison.
  • A qualitative example is used to imply a broad quantitative claim.