Annotation · not proposed UI Spec iii 3.1 · what a source row is. Each table row reads a source registry record: provider identity, what the source feeds, the current snapshot and its revision, and whether attribution is required. Factor rows carry their source and snapshot revision, so every published number on the tenant side traces back to exactly one row here: computed figure, to factor row and edition, to source snapshot, to this record. The expanded DESNZ row shows the pattern for the Required flag: the stored attribution line lives in the row detail; each Required row opens the same way. Clicking a row inserts its detail inline below it, pushing later rows down; no overlay.

Annotation · not proposed UI Spec iii 6.5 · the subscription reference is metadata, not a licence engine. Licence status is not enforced by the product (PM ruling D-iii-1): no expiry check exists anywhere in code, and computation, imports, and reads behave identically the day before and the day after 24 Aug 2027. Renewal follow-up is Evercomm staff work owned by Platform operations; this table is the reminder surface, not a gate. The beneficiary counter is display-only (PM ruling D-iii-2): counted per customer company whose computed figures actually used SEFR values in a run. Nothing refuses at any count; an 11th benefiting company would make it read "11 of 10" and change nothing else. Both are deliberate scope decisions, recorded so a reviewer does not mistake the absence of enforcement for an unfinished feature.

Annotation · not proposed UI Spec iii 7.6 · placement and access. The factor library follows the Companies pattern: a system_admin operator surface, cross-tenant, outside tenant navigation. A non-system_admin caller who reaches these routes receives the platform's byte-identical unknown-route 404, so the surface is undiscoverable rather than merely forbidden. The "Internal operations" sidebar group with the Factor Library item and its three sub-items (Sources, Editions, Browser, always visible, active per page) is a menu placement proposal; the hatched block stands in for whatever operator navigation already exists.

Annotation · question for the PM Two questions this page does not settle. First: should the SEFR expiry date raise an operator-side reminder (an email or console notice some weeks ahead), or does Platform operations track renewals outside the product entirely? Ruling D-iii-1 only settles that the product does not refuse; it does not say whether it reminds. Second: the beneficiary counter is operator-only as drawn. Whether a benefiting company should ever see that its figures used SEFR values is a tenant-surface question left to the lineage view, not decided here.