Notifications
Regulatory Digest posts to your firm's feed channel, and every post it makes also appears as an item in Feed. All of it is internal. Nothing the agent produces is ever visible to an advisor, an LP, or any outside party.
What A Run Produces
A run does not post one combined card. It posts one card per area that had new material, under its own name, so a quiet area stays silent instead of padding a card with nothing.
| Card | Covers |
|---|---|
| Compliance Watch | Rule changes, regulator guidance, enforcement precedent, court decisions |
| Filings Watch | Competitor and peer filings, product and offering intelligence |
| Platform Watch | Platform and distribution-channel context |
| Market Pulse | Economic data and market intelligence |
| Research Pulse | Investment research and trade press |
A run posts as few as one of these and as many as five. An area with nothing new in the window produces no card at all.
What One Card Contains
Each card is short by design: a marker, a bolded headline, one or two sentences explaining why it matters, and a trailer. In Slack it reads roughly like this:
馃毃 *FINRA AWC: forward-return language fined $200K*: Direct precedent on
outreach phrasing; projection language in current collateral is worth a
compliance read.
_Daily update 路 April 30, 2026 路 12 documents_
The parts:
- The marker changes with the card's materiality, so a material item is visually distinct from routine background at a glance.
- The headline is the lead item for that area in this run: the most material thing the agent saw.
- The reason is one or two sentences on why it matters to distribution or compliance, not a summary of the filing.
- The trailer names the cadence, the date, and how many documents the run took in for that area.
When an area had more than one material item, the card adds a line naming up to two more: Also material: X, Y. When the lead item is the only notable thing but more arrived, it adds Plus 11 additional documents in this run. instead.
A card names the lead item and counts the rest. It is not a complete list of every filing in the window, and the headlines do not carry links to the underlying filing. Open the source's own public record when you need to read the filing itself.
The "What We Have On File" Sidebar
When the lead item matches something in your own uploaded compliance and playbook documents, the card appends a short sidebar showing what your firm has already written on the subject, with each cited document linked to its entry in the operator console. This is the one kind of link a card carries, and it points at your own material, not at the regulator's.
When a material item matches nothing on file, the card says so instead:
*Action:* legal flagged this and the firm has no documented position on file.
That line is the most actionable thing the digest produces. It means something changed that your firm has no written position on.
Materiality Labels
Every item is classified into one of three levels, and the bar for the top one is deliberately conservative.
| Label | What it means |
|---|---|
| Material | Changes a rule, opens or closes a regulatory gate, or sets an enforcement precedent that would alter how your firm distributes, markets, files, or reports |
| Notable | Useful context that does not shift action: industry trend data, peer fund filings, macro releases, research findings |
| Routine | Noise: monthly statistical releases, minor amendments, calendar items |
Material items arrive in your app feed at a higher severity than the rest. Over-flagging trains a team to ignore the digest, so when the classifier is unsure it downgrades.
Routine items do not normally reach a card. The one exception: if an area produced nothing above routine in the window, its card leads with the highest-volume routine item rather than staying silent, so you can still see that the area was read.
When Nothing Posts
A run that finds nothing new posts nothing. There is no empty-digest note, no "run complete" confirmation, and no card saying the window was quiet. Silence means either a quiet window or a run that did not happen, and the cards themselves do not distinguish the two.
If you need to confirm a run happened, the archive in the operator console is the place that answers it. See Troubleshooting.
Action Required
Read the material headline, if there is one. Decide what belongs in your compliance log, what warrants a wholesaler ping, and what deserves a closer read against the regulator's own record. Notable and routine items are background; no action is expected by default.
Cards carry no buttons. Regulatory Digest produces no outbound artifacts, so there is nothing on a card to approve, send, or draft.
Regulatory Digest does not send direct messages and does not post real-time alerts between runs. Everything arrives on one of the four scheduled cadences.