Skip to content
  1. Wiki
  2. Verification and evidence
  3. Evidence (not "should be fixed")

Evidence (not "should be fixed")

In pstack, "done" needs real proof: real output, values actually saved, a screen actually clicked through.

An analogy

Like inspecting a house. "The plumbing's fine" doesn't count; you turn on the lights, run the taps and check the meter.

In pstack

This principle means "show that it works"; its name is prove it works. Proof comes from something that really ran, and "it compiled" doesn't count. For a command-line change, run the real command. For a screen change, click through it in the app. For speed, compare before-and-after numbers.

In your first prompt, say "what counts as done" and "what proof you want". That's the most useful thing you can do. When it can't check something, a good reply says "inconclusive". A confident reply with no proof can't be trusted.

Common misconceptions

  • "All the tests pass, so it's proven": tests only check the cases their author thought of. pstack wants to see how the real app behaves.
  • "Its explanation makes sense, so it's probably fine": a result you can check beats any explanation. You can verify a result; an explanation you can only believe or not.

Try it: Full guide step 6: Verify and ship

Related: Verification skill, The 24 principles, Formal verification

An unofficial beginner's guide to pstack, not its official docs. pstack is made by poteto; the official repo is the source of truth for commands and behavior. The original guide source is on GitHub.

Hosted by airali. Adapted from Xiaoxiaodong's MIT-licensed guide.