core practice · system design prompt

Design exercise: Evidence-backed Verification

Claims, source provenance, executable checks, screenshots, diffs, test outputs, and acceptance criteria. Implement designOutline() returning non-empty values for: acceptanceCriteria, evidence, inferenceBoundary. Each value must name a concrete mechanism or decision.

The mechanism

Verification turns an agent claim into inspectable evidence. Match each acceptance criterion to a source, command, artifact, or observed state and keep inference separate.

Study Evidence-backed Verification

Expected evidence

A design outline with acceptanceCriteria, evidence, inferenceBoundary plus an explicit failure mode or trade-off.

Try this drill in the practice workspace →

Hints when you need them
  • Name the failure mode before selecting the mechanism.

Check the sources

Browse all practice briefs