Known gaps

These findings describe the configuration as of 2026-10-28.

Configuration defects

• Notification Rule → Audience (Membership Name) and Message → Recipients (Membership Name) are invalid lookups with no target field (Work Item “Fix invalid lookup and formula configurations across bases”).
• Channel has a blank row with no name, type or status.
• The rule Reading due today says schedule:daily 09:00 America/Chicago in Trigger; scheduled rows are created at about 12:00 UTC, which is 09:00 in Brasília.
• The Slack DM channel’s description says the bot opens the conversation by the member’s Company Email; the Daily Digest resolves recipients through Identity Binding and Tool Account in Tooling and Access.
• Channel Type’s description lists five choices and omits Direct Message, the type of the only channel in use.
• Message → About Keys says the keys point to readings in “the Operation base”; they are Recurrence Configuration ids in KPIs & OKRs. The Context Base option Operation is ambiguous with the retired Operations base.
• Message → Context Base’s description maps a Sales purpose to CRM, but Purpose has no Sales option.
• Channel Binding → Subject Type’s description says the sync and the automations read the type and link pair; no automation reads Channel Binding.
• Rollups that count Sent rows (Messages Sent, Last Sent) include dry runs.

Not built yet

• No intake, check or queue views; one Grid view per table.
• Channel Binding is empty and unused; Notification Rule documents a flow rather than driving it.
• No retry for Failed deliveries; a design awaits approval (Work Items “Approve the Daily Digest retry proposal” and “Implement Daily Digest retry with shared sender and idempotency”).
• Recurring Daily Digest failures for unresolved recipients (Work Item “Fix the Daily Digest DM failures (user_not_found)”).
• Email Logging is inactive (Work Item “Activate the Email Logging workflow (Gmail to Message and Interaction)”).
• Message Status Received and Purpose Sales are missing; Sales lets a binding route e-mail context to CRM and Received marks inbound e-mail (Work Item “Add Received (Message Status) and Sales (Channel Binding Purpose) options”).
• No Tool Account mirror and no Channel → Tool Account link; a mailbox is a Tool Account and the person behind it comes from its Identity Binding, never from the address (Work Item “Mirror Tool Account into Communication and link it from Channel”).
• No synced Message views for CRM or other bases; each consuming base is meant to read Message through its own synced view (Work Item “Sync Message to consumer bases and link Relationship Messages”).
• Follow-up stays in each base, not here: CRM follows up through Interaction and Task, billing through its own collection records; the rule is adopted but not yet applied (Work Item “Keep follow-up in each base, not in Communication”).
• E-mail and campaign sequences are deferred (Work Item “Build connected e-mail and campaign sequences”).

Documentation boundaries

Confirm flow behavior in n8n and in the newest Message rows. Check the sync configuration of the nine mirrors (source view, field mapping, refresh) in the Airtable sync settings, and the filters of the mirror Grid views, before relying on them. Base permissions have not been reviewed.