Story-3301 — the P5 progress UI: the living index on the matter screen

pramaan-functions Story-3300 files the living index: a draft the moment the knife commits a bundle's members, one row upgraded per card, a final PDF into the family. This is the app half — counsel watching that index fill in on the Record, with Kabir's name on it.

What ships

• src/lib/documents/register/bundle-index.ts — livingIndexes(), a pure projection from the register corpus to one LivingIndex per carved bundle.
• src/components/documents/register/living-index-strip.tsx — the strip, mounted above the register in live-matter-documents-page.tsx.
• Copy under DocumentsRegister.livingIndex in both messages/en.json and messages/hi.json. The registrar's name comes from AgentsCast.kabir.name — counsel reads Kabir; logs and dashboards keep saying Blake (agents/_shared/personas.py: two namespaces, disagreeing by design).

Where each tick comes from — real work, never a timer

Completeness comes from the declared family, never from one page of rows

The Record renders one page of documents (limit=50 on the record bootstrap). A paperbook carved into more members than that has its later annexures absent from the corpus entirely — so a final decided from rows.length would call the index complete while the backend family is still draft. Telling counsel a legal index is finished while annexures are pending is the exact class of credible-looking-but-wrong status this epic exists to kill (app#788 P1).

So the denominator is familyMemberCount — carve's declared member set, read off the frozen BundleFamily already on the bundle row, durable and in the payload the page already has (no extra fetch, no poll). The strip shows that real denominator ("12 of 62 read") and names how many members are off the page. A family whose declared count is missing stays draft forever rather than guessing. bundle-index.test.ts → completeness comes from the DECLARED family reds if the predicate goes back to rows.length.

Refresh is the test (D22)

The strip reads the same server-rendered corpus the register renders — the Record page's existing recordBootstrap round-trip. No new endpoint, no poll, no second fetch. Reload the browser mid-journey and the projection re-derives an identical index; bundle-index.test.ts asserts exactly that, including corpus-order independence.

It cannot run ahead of the work. Three ways it errs, all in the same safe direction: a card that applied REFUSED (the broker's unread, which the app contract does not carry) reads pending; members off the current page keep the index draft; and a missing declared count keeps it draft forever. It can under-report a finished bundle; it cannot over-report an unfinished one.

Firm scoping

The corpus is one firm-scoped read (backend RLS + the Clerk org scope on the query client). The projection groups members by a parentDocumentId that resolves inside that corpus, fetches nothing, and resolves no id of its own — so a member whose parent is not visible produces no index and never stitches itself into a family that is. Asserted in bundle-index.test.ts → firm scoping (RLS).

Not derivable from today's app contract — named, not faked

• DocumentListItem carries no family_manifest, so the broker's own state/rows_read/generation and the filed index PDF's identity are not readable here. The projection re-derives state from the member rows instead; when functions exposes the manifest, reading it is a one-liner and the "open the index" link becomes possible.
• Segmentation has no row-level signal (a carved member is minted indexed and the segment pass writes only documents.document_sections). The strip therefore shows carve → per-member cards → final index, and says nothing about segmentation rather than inventing a tick for it.
• The live half is not wired, and cannot be from this repo. clerk_worker/bundle/progress.py pushes run.progress to the run's connection_id; an ambient Blake carve run has no browser connection, so every push logs step_drop.progress_no_connection. Per the acceptance, live frames are additive and never the source of truth — the durable half is the whole of the truth, and it ships complete.

Verify

Storybook: Documents/Register/LivingIndexStrip — DraftAtCarve, FillingIn, Final, LargerThanOnePage, TwoBundles, Empty.
Staging: open a matter holding a carved bundle → the strip lists its members with Kabir reading them; reload mid-journey → identical progress; when the last card lands the strip flips to Final.