Reading diagrams / Topic 33 of 42
Checked endings: ticks, red, green and ?
The rule
An author can write claims about a route's paths, such as not writes docs on the path where the document is someone else's. Yichus checks each claim on the path it names and marks the ending with one count per verdict: ✓ 1 is a claim that holds, ✗ 1 one that fails, and ? 1 not known one Yichus cannot decide. On a route with claims, an ending marked no claim has nothing claimed about it. A struck ring label beside a stub, such as “write · docs”, is the write that claim says does not happen, checked.
The colour of a cap or a dot comes only from checks. A red cap means a claim fails on that path, or a check such as the access check reports a problem there. The list under the tree, why each coloured leaf is coloured, gives the reason by number. A red or green dot beside an entry's name at the top says one of its paths is red or green.
So a cap can be red and ticked at once: the tick is the author's claim holding, and the red is another check failing on the same path. In policy-docs, every path that reads docs is red with the note no AccessRule declared for resource “docs”. An access rule names a table and who may touch it, such as only its owner, or only after a named check. The access check found none for docs, so it reports every path that touches that table.
When an earlier version is compared, the line at the top says so: “compared with shared-docs-base · 1 fixed · 0 still failing”. A green cap is a path that failed in that version and holds now, with the old ending drawn faded beside it, marked base. With nothing compared, there is no such line, and the tree cannot say what was fixed.
A hollow, dashed cap marked ? not known is a path where Yichus could not follow the code, or where the access check gave up on an operation, and its note says why. It is neither yes nor no, so no red on a tree with a hollow cap does not mean nothing fails. Its rings may be missing too: a write inside code Yichus could not open is not drawn.
A tick checks the claim as written. No red anywhere means no claim the author wrote fails and no check Yichus runs reports a problem; it does not mean the route is right. Whether the claims are the ones that matter, or whether the italic words describe the code, is for you and the author to judge.
- ✓ at an ending confirms the claim on that path; ✗ rules it out; ? not known on a hollow cap, or no claim, can't tell.
- A red cap: an author's claim or a check Yichus runs fails on that path, and the numbered note says what.
- A green cap: fixed since the compared version. With nothing compared: can't tell.
shared-docs /docs/edit, compared with shared-docs-base, the version before a fix.
Loading the shared-docs tree.
sequence-probe /save.
Loading the sequence-probe tree.
policy-docs /docs/write again.
Loading the policy-docs tree.
How to read this: what each mark in these pictures means
Loading the worked examples and practice.