Molecule

Tombstone

Where something used to be. 7 instances across 7 screens, inside a block.

The evidence snapshot that fell out of the 90 day retention window, the case that was superseded, the source that no longer resolves. Geo and compliance require an append-only log carrying the evidence as it stood, and this is what the interface does on the day that record can no longer be produced: it says so in the place the record was, rather than rendering nothing.

A slot has no variant matrix. Six molecules turned out to be slots at step 2, measured in a browser: 71 distinct sets of child zones and one computed form each.

Anatomy

dark, shipped

The snapshot is gone. It fell out of the 90 day window on 12 August, and the ruling above still stands.

light, the pair

The snapshot is gone. It fell out of the 90 day window on 12 August, and the ruling above still stands.

Variants

One, and it arrived at stage 09 by being counted rather than by being drawn. tomb--all, one instance, on the entry screen for a case beyond retention, where what is gone is not one field but the whole record. Its own file said "step 9 decides whether one use earns a name", and step 9 decided: it keeps the name, because the alternative reading is a tombstone with everything missing, and that is a different sentence rather than a fuller one. It is the only variant in the system standing on a single instance, and it is named here so that the count is visible rather than the exception invisible.

And otherwise none.

Axis a reader looks forValuesWhy the cell is empty
severity–Prohibited, and this is the whole component. A red box would say the record failed. The record did exactly what the retention policy says it does
kind–It is a slot: 5 sets of child zones across 7 instances
action–No control. There is nothing to retry: what is gone is gone, and offering to fetch it would be the interface lying about its own storage

When to use it

In the place a piece of evidence would have been rendered, when it can no longer be produced. It is never used for something that failed to load.

Where she meets it. Months later, defending a decision. This is the component that has to be honest when nobody is watching, and the sentence has to say which record and when it went, because those are the two facts an auditor will ask for.

Rule and anti-rule

Do

The snapshot is gone. It fell out of the 90 day window on 12 August, and the ruling above still stands.

What is gone, when it went, and what is still true. The last clause is the one that matters: a missing snapshot does not undo a ruling.

Do not

Snapshot unavailable

Never as an error. Retention working is not a failure, and painting it in the severity ramp spends a colour that belongs to cases on a policy behaving correctly.

States

It has none, and it is not interactive.

dark, shipped

The snapshot is gone. It fell out of the 90 day window on 12 August, and the ruling above still stands.

light, the pair

The snapshot is gone. It fell out of the 90 day window on 12 August, and the ruling above still stands.

The dashed border is drawn with an INK role and not a line role, and the exception is deliberate. --text-secondary is declared ink; used as a border it paints a line. The alternatives are --line-control at 3.98, which would make the tomb louder than the evidence beside it, or --line-separator at 1.18, which would make a dashed box invisible. It is not a control boundary, so 1.4.11 does not reach it. The surface rule is bent knowingly rather than by accident, and step 9 rules on whether it earns a line role of its own.

What it reads, and where it stands

RoleSurfaceWhere on the componentDarkLight
--text-primaryink 4.5:1what is gone
--text-secondaryink 4.5:1the sentence, and the dashed border

Copy this

<p class="tomb"><b>The snapshot is gone.</b> It fell out of the 90 day window on 12 August.</p>

Where it stands