List a partner's activity

Lists everything that happened to a sourcing partner, newest first.

Cursor-paginated, newest first, across seven sources: status changes, terms revisions, documents received and verified, payout-account changes, loans attributed and detached, invoices raised and payments recorded.

Derived, never logged. Every entry comes from the record that already exists; there is no activity table. A feed table would be a second copy of every event in the API, and the copy is what drifts: a row claiming a document was verified, beside a document that says it was not. Deriving costs a wider query and buys the guarantee that the feed cannot disagree with the thing it describes.

type is an enum and arrives lower-case: status_changed · terms_revised · document_received · document_verified · bank_account_changed · loan_attributed · loan_detached · invoice_raised · payment_recorded. New types will be added over time; treat an unrecognised one as displayable rather than an error, and render summary, which is written for an operator to read verbatim.

reference_id is the opaque id of the thing the event happened to, so a row can link straight to it; it is null for events with no addressable subject. reason is populated only where the write demanded one: status changes, payout-account changes and attribution corrections.

actor is null where the underlying row carries no user, rather than being filled in with a plausible name. A seeded or system-written record has no person behind it, and naming one in an audit feed would be a lie in exactly the place someone goes looking for accountability.