Get ThruLine

Five chains · one demo record

Specimens

Each one is an agent’s claim, checked against what ran. A specimen is a case study where the customer is the record.

Where these come from

Recorded on ThruLine’s checkout-web demo record. No customer data.

[swap in a corpus chain before launch]

demo · checkout-web

In a chain

holds lit thread proof stops here, once not reached, never faded

5 specimens

  1. Specimen 01

    Ran, checked nothing

    “Ran, checked nothing. This is not a pass.” A run that exits 0, the code for success, having checked nothing.

    Read the chain
    ① Said ② Rests on ③ Ran on ④ Since ⑤ Re-checked ⑥ So
    1
    ▪
    3
    4
    5
    Not proven

    Proof stops at ② Rests on

    [n] skipped, 0 ran · exit 0

    Outcome: Ran, checked nothing (not a pass)

  2. Specimen 02

    The run was one version older

    The tests passed on 9f2ad3e — one version (one commit) before the one you are approving.

    Read the chain
    ① Said ② Rests on ③ Ran on ④ Since ⑤ Re-checked ⑥ So
    1
    2
    3
    4
    5
    Not proven

    Proof stops at ③ Ran on

    version 9f2ad3e · 1 version older · approving e71c5b0

  3. Specimen 03

    A file changed after the run

    checkout/api.py changed at step 56 (16:04), after the run and after the claim.

    Read the chain
    ① Said ② Rests on ③ Ran on ④ Since ⑤ Re-checked ⑥ So
    1
    2
    3
    5
    Not proven

    Proof stops at ④ Since

    Needs a re-check· version e71c5b0

    checkout/api.py changed · step 56 · after the run

    The code is now e71c5b0, and nothing on it has run with that file in scope.

  4. Specimen 04

    The count that counted the passes

    “Failed · 3 of 4” when 3 passed and 1 failed: a count must say which way it counts. Caught in ThruLine’s own prototype screen during design review, and fixed.

    Read the chain
    ① Said ② Rests on ③ Ran on ④ Since ⑤ Re-checked ⑥ So
    1
    ✕
    3
    4
    5
    Not proven

    Proof stops at the count, not the chain

    Failed · 3 of 41 failed, 3 passed (4 tests)

    The record: 3 passed, 1 failed. The fixed count says which way it counts — failures first.

  5. Specimen 05

    A step with no result yet

    Step 60 started a check and has no result yet. A step with no result never counts as proof.

    Read the chain
    ① Said ② Rests on ③ Ran on ④ Since ⑤ Re-checked ⑥ So
    1
    2
    3
    ⋯
    Not proven

    Proof stops at ⑤ Re-checked

    Needs a re-check· version e71c5b0 No result yet· step 60

    The check step 60 started has no result, so it never counts as a link in the chain.

The six questions

How to read a chain

Every chain asks the same six questions of one claim, in order. The thread stays lit while the record backs the claim. The stop mark shows where proof runs out.

See the chain on the product page What “Not proven” means Where the record lives
  1. ① Said

    What did the agent claim?

    Every chain starts here.

  2. ② Rests on

    What is that claim based on?

    Stops here: 01, 04

  3. ③ Ran on

    Which version did that actually run on?

    Stops here: 02

  4. ④ Since

    Did anything it depends on change after it?

    Stops here: 03

  5. ⑤ Re-checked

    Has anything checked it since?

    Stops here: 05

  6. ⑥ So

    So what do we actually know?

    All five here end in Not proven.