Knowledge requests — its own ring in the side nav

Its own count and inbox item; beside go-live, never part of it

22 Oct 2026 · branch feat/knowledge-requests-p1b-ring · captured against propflow-stage · at ae6c9dfe154

Data note. Every name and balance below comes from propflow-stage, which is anonymized by construction (ADR-0097/0110 — phones in the impossible +1000 NPA, emails @example.test). The identical capture against prod would carry real tenants' names and balances and is not safe to attach anywhere, which is why the generator refuses to run against one.

1 · Not live: Knowledge requests and go-live, each with its own ring

The side nav's bottom slot draws the Knowledge requests row with its own ring above the go-live row, as in the approved mock. Its percent is Knowledge requests' own count (the same read the page's bar paints from); go-live's ring is unchanged.

Asserted in the captured DOM — Knowledge requests · answered · complete · Packages. Both pinned rows and the page's count loaded.

Not live: Knowledge requests and go-live, each with its own ring
Sections 2–2 and notes

2 · Phone width

The page at phone width; the rail is behind the menu button there.

Asserted in the captured DOM — answered

Phone width

What is not in the picture

The live-company state (Knowledge requests ring only) and the all-answered state (nothing pinned) are pinned by inbox-items.test.ts; the TEST company is not live and has unanswered topics. No answer was saved.

PropFlow Docs