Molecule

Claim

The line of evidence. 131 instances across 24 screens, and after the row it is the most repeated thing in the product.

Three zones in one order: what kind of claim this is, the claim, and where it came from. Design principle 2 is built out of these: the tag lets her skip, the sentence lets her judge, and the source lets her check.

It was not in the register. Step 2 built the register from a browser census of controls, and this is a container. Found at step 5 by scanning every class that owns a rule block in kit.css against the register: twenty one came back and thirteen were components. docs/inventory.md section 13 has all of them.

Anatomy

dark, shipped

identityToken replay from a new ASN, 3 of 3 sessions.Entra sign in

not foundNo second signal on this tenant in the same window.tenant baseline

light, the pair

identityToken replay from a new ASN, 3 of 3 sessions.Entra sign in

not foundNo second signal on this tenant in the same window.tenant baseline

Behaviour at width

Below 1280, the system's one point (Width), the line wraps and the source takes margin-left:auto. That is the whole of it. Until then the source parked at the top right and the sentence wrapped underneath it, so a two line claim read as two columns; the source takes a line of its own now. The three zones, their order, and the tag sitting inside .txt rather than beside it are the same at every width.

Variants

AxisValueUsesThe rule
absencebase113Clerk found something
.claim--absence18Clerk found nothing, and that is the fourth voice rule rendered: say what is true about the machine, including what it did not find. The whole line dims together, tag, sentence and source, because the absence is the claim rather than a weaker version of one
severityno values–Prohibited. A claim is not a case. The severity ramp belongs to the row, and painting one line of evidence would tell the analyst which part of the argument to believe

When to use it

In the evidence block of a case, once per thing Clerk found or looked for. It is the unit the analyst reads down until she either believes the verdict or does not.

Where she meets it. Dozens of times a shift, on the one surface the whole product exists for. Six hours a day is why the tag exists at all: it is what lets her read the fourth claim without reading the third.

Rule and anti-rule

Do

identityToken replay from a new ASN, 3 of 3 sessions.Entra sign in

Kind, claim, source. The count names its scope and the source opens where it came from.

Do not

Suspicious sign in activity detected.

Never without a source and never as a summary. A claim with nowhere to check it is an assertion, and this product exists because the analyst arrives distrusting the machine.

At 360 the claim wraps and the source takes its own line pushed right. Before that it parked at the top right and a two line claim read as two columns.

States

It has none, and it is not interactive.

dark, shipped

identityToken replay from a new ASN, 3 of 3 sessions.Entra sign in

not foundNo second signal on this tenant in the same window.tenant baseline

light, the pair

identityToken replay from a new ASN, 3 of 3 sessions.Entra sign in

not foundNo second signal on this tenant in the same window.tenant baseline

What it reads, and where it stands

RoleSurfaceWhere on the componentDarkLight
--text-secondaryink 4.5:1the whole line when it is an absence
--line-separatorline, exemptthe hairline between claims

Copy this

<p class="claim"><span class="txt"><span class="tag">identity</span>Token replay.</span><a class="src" href="...">Entra sign in</a></p>

Where it stands