Re-read and Delete

What counsel used to face

A document that had been read badly offered a lawyer a diagnosis job. Was the text extracted wrong? Was it classified wrong? Were the sections cut in the wrong places? Each had its own button, in its own place, under its own name — and picking the right one required knowing how our pipeline is built. That is our knowledge, not theirs. A failed row in the register even carried a third name for the same act: “Retry”.

What shipped

Two species of verb, and why the divider matters

The bulk bar keeps its four organize actions (founder-ratified 2026-07-14). Tagging a document, linking it to a proceeding, marking it filed, downloading it — these describe a document; they never change what it is. Re-read and Delete do. The rule drawn between them in the toolbar is that distinction made visible. Reclassify (declared side, home) stays for the same reason: it is counsel telling us a fact only counsel knows, not counsel diagnosing our pipeline.

Re-read: honest, not optimistic

The re-read endpoint is asynchronous by contract — it answers 202 with a queued ticket, and the segmentation pass runs later on the registrar rail. So there is nothing to be optimistic about: nothing has changed yet. The row therefore says exactly what is true — “Re-read queued” — instead of spinning on a completion it will never be told about. The document’s JOURNEY, on the Insights lens, is where the machine’s actual progress is told.

Delete: soft, guarded, and typed

Delete is a soft delete and always was, upstream: the row’s availability axis is tombstoned and the WORM bytes are retained (ADR-126 / FN-RETENTION). The register stops showing it, anything citing it can still render an honest tombstone, and an administrator can restore it. Nothing a lawyer can click destroys evidence. The confirm dialog says so in as many words — that reassurance is the copy’s whole job.

Three guards, in order

1. Counsel only. Without matters:write both verbs still show — disabled, with the reason. A lawyer must never wonder whether Delete is missing or merely unavailable.
2. Legal hold outranks counsel. A document on hold cannot be deleted by anyone; that is the entire point of a hold. Re-read stays available — reading a document again cannot destroy it, so a hold has no business blocking it.
3. Type to confirm. A click-through “Are you sure?” stops nothing: the muscle memory that opened the menu also dismisses the dialog. Typing the phrase forces the eye back onto the object.

Bulk is not a bypass

Selecting twelve documents and pressing Delete runs the row guard twelve times. A document under legal hold survives the bulk exactly as it survives its own row menu, and the skip is reported — “2 documents skipped — under legal hold” — rather than silently swallowed. Partial success is stated as partial success.

The flow

The seam we are honest about

The re-read endpoint that exists today is segmentation-only: it re-cuts the document’s sections against its current extraction run. It does not yet decide depth — it will not re-extract a degraded scan, reclassify, or re-brief. The founder’s ruling requires one door that diagnoses which stages to run.

So this Story ships the vocabulary against the door that exists, and the unified repair door is filed as a pramaan-functions child ticket (pramaan-docs ADR-031). When it lands, the UI changes by exactly one line: the endpoint the Re-read verb calls. Counsel never sees the difference — which is the point of hiding the ladder behind one verb in the first place.

What to look at